http://repo1.maven.org/maven/cargo/jars/cargo-core-uberjar-0.7.jar works for me.
Syncing plugins now. - Brett Vincent Massol wrote: > >> -----Original Message----- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: lundi 16 janvier 2006 18:20 >> To: Maven Developers List >> Subject: Re: Syncing repository-staging/maven to ibiblio? >> >> As I said in my previous mail, yes, its turned off. The only thing that >> will harm is plugins. Artifacts in the "m1" repo are served out of m2 >> anyway, so there is no point including them in the m1 repo, but plugins >> are not converted. > > That's what I thought too but all cargo m1 users cannot use it! The reason > is that our m1 cargo plugin depends on cargo jars and it uses "cargo" as the > groupId for those dependencies but the URL rewriting rule is using > "org.codehaus.cargo" as the groupId. I've fixed this for the next release of > Cargo but in the meantime the cargo m1 plugin 0.7 is unusable if we don't > sync the cargo artifacts. > >> Is it only a plugin that is the issue? I will sync it across manually if >> you give me the artifact ID until the next solution is in place. > > Thanks. There are actually 3 jars, located in > /home/projects/maven/repository-staging/to-ibiblio/maven/cargo: > > groupid = cargo > artifactId = cargo-maven-plugin > type = plugin > version = 0.7 > > groupid = cargo > artifactId = cargo-core-uberjar > type = jar > version = 0.7 > > groupid = cargo > artifactId = cargo-ant > type = jar > version = 0.7 > > Thanks! > -Vincent > >> Vincent Massol wrote: >>> Hi (Brett), >>> >>> Yesterday I've copied the cargo artifacts to >>> repository-staging/to-ibiblio/maven (this was required because our m1 >> plugin >>> uses the "cargo" groupid). >>> >>> However the sync has not happened and I can't the new 0.7 artifacts on >>> ibiblio (http://www.ibiblio.org/maven/cargo/jars/). >>> >>> Is the sync turned off? If so how can I get those artifacts to show up >> on >>> ibiblio? >>> >>> 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] > > > --------------------------------------------------------------------- > 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]
