[cle-release-team] [Building Sakai] Removal of indies and project versions

[Steve Swinsburg]

This has been the case for some time, trunk has been the same as trunk all, but it will be good to finally simplify this.

Cheers,
S

Sent from my iPad

On 13/09/2013, at 21:58, Neal Caidin <neal.caidin at apereo.org> wrote:

> YES!
> 
> The team wants to get rid of TRUNK-ALL because it is redundant.
> 
> Cheers,
> Neal
> 
> 
> 
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Sep 13, 2013, at 7:52 AM, Mark Breuker <mbreuker at loi.nl> wrote:
> 
>> Hi Aaron,
>> 
>> Does this mean that the main code line can now be checked out from TRUNK again instead of TRUNK-ALL?
>> 
>> Cheers,
>> 
>> Mark
>> Mark Breuker
>> Product Owner
>> Tel.: +31 71 5451 203
>> Leidse Onderwijsinstellingen bv
>> Leidsedreef 2
>> 2352 BA Leiderdorp
>> www.loi.nl________________________________________
>> Van: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] namens Aaron Zeckoski [azeckoski at unicon.net]
>> Verzonden: donderdag 12 september 2013 21:45
>> Aan: Sakai-Dev Developers; cle-release-team at collab.sakaiproject.org
>> Onderwerp: [Building Sakai] Removal of indies and project versions
>> 
>> This is a "heads up" (warning) for all developers and contrib tool authors.
>> 
>> With the completion of https://jira.sakaiproject.org/browse/SAK-23907
>> we will have removed all indies (projects which were versioned
>> separately from the main Sakai version and downloaded as a binary
>> instead of built during regular builds) and all indie project versions
>> (e.g. sakai.jsf.version) from the corporate POM (a.k.a. master). This
>> change includes the kernel. This has been committed to trunk as of
>> today and should be working for all core projects.
>> 
>> Any contrib tools which referenced older versions manually (e.g.
>> 1.4.0-SNAPSHOT for kernel) or used the project versions will fail to
>> build against trunk after today. All non-core code should use the
>> Sakai master pom as parent and should not reference versions directly
>> but should instead exclude the version for all Sakai dependencies and
>> all maven dependency management to handle the versioning.
>> 
>> Look at the projects in the core for examples of the right way to do this.
>> 
>> Let me know if you have any questions.
>> -AZ
>> 
>> 
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>> _______________________________________________
>> 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"
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130913/55652100/attachment-0001.html