Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml
Hi, Is it the same like "installing" the snapshot artifacts in the local ~/.m2 cache ? I am looking at some of the stuff which is lying on my hard drive : /Users/antoine/.m2/repository/org/apache/commons/commons-openpgp/1.0-SNAPSHOT antoine-levy-lamberts-macbook:1.0-SNAPSHOT antoine$ ls commons-openpgp-1.0-SNAPSHOT.jarmaven-metadata-local.xml commons-openpgp-1.0-SNAPSHOT.pom Regards, Antoine Stefan Bodewig wrote: On 2010-03-16, Bill Barker wrote: I was thinking of adding a localRepository="name" to the builder that allows projects to share a local repo when they can't be trusted to use the central repo. These would be cleaned when Gump finishes (or maybe on startup). Sounds like a good idea. It would probably solve the castor-xml case as well when castor-xml can share the local repository with castor-core. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml
On 2010-03-19, Antoine Levy Lambert wrote: >> On 2010-03-16, Bill Barker wrote: >>> I was thinking of adding a localRepository="name" to the >>> builder that allows projects to share a local repo when they can't be >>> trusted to use the central repo. These would be cleaned when Gump >>> finishes (or maybe on startup). > Is it the same like "installing" the snapshot artifacts in the local > ~/.m2 cache ? Yes, I think so. Only that we'd be using a directory other than ~/.m2 that would get purged after the Gump run has finished. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml
-- From: "Stefan Bodewig" Sent: Friday, March 19, 2010 6:39 AM To: Subject: Re: svn commit: r920715 - /gump/metadata/project/excalibur.xml On 2010-03-19, Antoine Levy Lambert wrote: On 2010-03-16, Bill Barker wrote: I was thinking of adding a localRepository="name" to the builder that allows projects to share a local repo when they can't be trusted to use the central repo. These would be cleaned when Gump finishes (or maybe on startup). Is it the same like "installing" the snapshot artifacts in the local ~/.m2 cache ? Yes, I think so. Only that we'd be using a directory other than ~/.m2 that would get purged after the Gump run has finished. Yes, that is the idea. It lets a group of projects that depend on each other's snapshot artifacts to "install" them in a local cache where they can then be found by M2, since M2 doesn't like to get snapshot artifacts from any of the remote repos that are currently mirrored. This would also be helpful for M2 projects that define their own remote repo in the POM, that isn't mirrored, since they can't be trusted to use the common local cache (because if they have a dependency on an Ant-built project, and are the first to request it, it will get the versioned jar from their remote repo, and then other M2 projects will use that jar instead of the Gump-built jar). This would have made setting up portals-pluto-trunk much easier, instead of the sordid hack I used to convince Gump to make it the last project to build. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
