[Building Sakai] Getting rid of 3.0.0-milestone01 binaries

[N. Matthijs]

+1 for all of the reasons that Anthony gives.

Nicolaas

> +1 Binaries removal (i.e.., artifact removal from the Maven2 repo only)
>
> The 3.0.0 milestone01 code misrepresents the Sakai 3 technology stack.
> It's confused deployers on more than one occasion.  Plus, we can remove
> the binaries without any harm since we are not losing history.  The code
> can still be retrieved from SVN.
>
> Cheers,
>
> Anthony
>
>
>
> On Jul 26, 2010, at 9:35 AM, Jean-Francois Leveque wrote:
>
>> Why bother and not remove the binaries right away if they're not
>> supported with Sakai 2 (based on unsupported Sakai 2.5) or Sakai 3?
>>
>> J-F
>>
>> Noah Botimer a écrit :
>>> Maybe they can be moved into a group ID like org.sakaiproject.preview?
>>>
>>> Thanks,
>>> -Noah
>>>
>>> On Jul 26, 2010, at 7:28 AM, David Horwitz wrote:
>>>
>>>> Hi All,
>>>>
>>>> When analyzing dependencies with maven tools (like the dependency
>>>> plugin) we get screwy results because  of the 3.0.0-milestone01
>>>> binaries
>>>> in the repo. Can we get rid of these?
>>>>
>>>> D
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"