Thanks, so I should use both http://www.ibiblio.org/maven and http://dist.codehaus.org/ as repository when I compile? How do I accomplish that? I've seen that the parameter -Drepo.url can be used to specify a different repository, but it doesn't seem to support a list of several urls.
/Magnus > -----Ursprungligt meddelande----- > Från: Vincent Massol [mailto:[EMAIL PROTECTED] > Skickat: den 21 februari 2005 11:39 > Till: 'Cactus Developers List' > Ämne: RE: adding dependency to cargo > > > Hi Magnus, > > I've made the Cargo 0.5 snapshot jar (containing your > modifications for > run-as - CARGO-109) available on: > > http://dist.codehaus.org/cargo/jars/cargo-0.5-SNAPSHOT.jar > > Thanks > -Vincent > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: lundi 21 février 2005 09:52 > > To: 'Cactus Developers List' > > Cc: '[EMAIL PROTECTED]' > > Subject: RE: adding dependency to cargo > > > > Hi Magnus, > > > > > -----Original Message----- > > > From: Magnus Grimsell [mailto:[EMAIL PROTECTED] > > > Sent: lundi 21 février 2005 09:22 > > > To: cactus-dev@jakarta.apache.org > > > Subject: adding dependency to cargo > > > > > > Hi, > > > > > > I am refactoring cactus to use cargo. I've made some > necessary changes > > to > > > the cargo code and > > > I would now like to start using them from cactus. The > changes to cargo > > is > > > not yet commited. > > > How do I do this? > > > > Very cool! For now the best way is to create a JIRA issue > for Cargo and to > > attach your patches to it. JIRA for Cargo is available on > > http://jira.codehaus.org. I'll apply them (if I get them > before the 24th > > morning, date at which I'm on holiday for 10 days and > without internet > > access... ;-)). Otherwise someone else will apply them. > > > > > I'm rather new to maven and the idea of downloading all > > > dependencies from > > > a remote repository. What is the main reason for this? > Why not bundle > > all > > > the dependencies? > > > > For the same reasons DLL, shared libraries, etc exist: to share them > > between projects. If each Maven project bundles all its jar > in its SCM > > they you'll find yourself with hundreds of copies of the > same libraries on > > your disk. > > > > Having a repository a la CPAN is also extremely useful. > > > > > > > > I suppose it's possible to add a dependecy to the latest > dev version of > > a > > > library, right? So when > > > I commit my cargo patch, when will it be available for > download at the > > > repository? > > > > Yes, you're right. We had a continuous integration build done by > > DamageControl (DC) some time back but DC had some bib > problems and it's > > been stopped. It should be back online in about 1 month I'd > say. So for > > now we have no more continuous builds. But: > > > > 1/ building from sources is very simple: SVN-checkout > Cargo, install Maven > > and type "maven" at the top level of your cargo sources. > The result will > > be in distribution/target/maven > > > > 2/ I can do a build whenever you wish and make the > generated jar available > > in the remote repository so that it's available to Cactus > users of 1.8dev. > > > > Thanks > > -Vincent > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
