[Building Sakai] [cle-release-team] Add/updating jars on the maven repository

[Steve Swinsburg]

Forget setting up Jenkins for 2.8 (lets leave that for 2.9+). So for those that need snapshots done for 2.8, just ping me. I have all of the setup and permissions that we need and its a simple 
mvn clean install deploy 
(ignoring source and javadocs)

cheers,
Steve


On 12/07/2012, at 7:48 AM, Matthew Jones wrote:

> Generally, for 2.8, the snapshots aren't being refreshed for most of the projects in the snapshots repository anymore, though they are for 2.9 and trunk. This was because prior to 2.9, all artifacts were deployed using SCP to source.sakaiproject.org to a flat file system (no repository manager) and generally some manual intervention was needed. None of these old projects were setup on the build server.
> 
> Also, prior to 2.9 the dependency resolution order (especially for indies) wasn't entirely correct, so it would occasionally download snapshot artifacts when you wanted to use the ones you built instead. This was because we left out relativePath for parents and had some of the module ordering wrong.
> 
> Those build changes weren't ever pushed back to 2.8, as all most build resources, aside from Steve getting 2.8.2 out, are focused on 2.9+.
> 
> For example, the snapshots that are present for msgcntr haven't been updated since 2010! So it would probably be bad if you relied on them in your build, and we should probably just wipe this repository anyway  http://source.sakaiproject.org/maven2-snapshots/org/sakaiproject/msgcntr/msgcntr/2.8-SNAPSHOT/
> 
> A few projects *are* still pushing snapshots, (kernel/master/purepoms/search) and it's not super hard to have snapshots for 2.8 be sent to the old repo (as they are for 2.9/trunk and the credentials are still correct), it just was never really configured that way automatically and would require a few hours of manual work on Jenkins to get them all in there regularly. and make sure it was all working correctly.
> 
> You could set up a local repository manager like Nexus and deploy them there if you wanted to avoid rebuilding them, I did that at Michigan for some projects, it's pretty easy.  
> 
> I'd be more concerned about breaking local builds if new snapshots started appearing in the repos, but otherwise I agree with Steve that it's doable.
> 
> -Matthew
> 
> On Wed, Jul 11, 2012 at 1:02 PM, Brian Baillargeon <bbailla2 at uwo.ca> wrote:
> Last week I created a patch and Bryan Holladay updated
> https://source.sakaiproject.org/svn/msgcntr/branches/msgcntr-2.8.x/
> We'd like to pull down a compiled jar with Maven rather than keeping it
> in our svn .externals file and building it locally. Is it bad practice
> to put up a jar whose version ends with '-SNAPSHOT'? Is there a process
> to add/update jars in the maven repository?
> 
> Thanks,
> Brian
> _______________________________________________
> 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/sakai-dev/attachments/20120712/5136153f/attachment.html