-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yep I'm subscribed to pluto-dev, though I'm by no means a pluto guru ;-) I'll change the pluto dependencies in the repository asap. And thank you for testing the new maven repository!
Regards. Diego. Elliot Metsger wrote: > Hey Diego, I don't know if you're on pluto-dev but here's a copy of the > convo I had there wrt the Maven repo. I had to modify the <groupId> of > the Pluto dependencies in the various subcomponents. Also, the > pluto-portal jar was missing from Ibiblio - Carsten is/has put it up to > be mirrored so it should be there soon if it isn't already. > > Elliot > > -------- Original Message -------- > Subject: Re: issue with maven repo on ibiblio > Date: Tue, 30 Aug 2005 10:38:17 +0200 > From: Carsten Ziegeler <[EMAIL PROTECTED]> > Reply-To: [email protected], [email protected] > To: [email protected] > References: <[EMAIL PROTECTED]> > > Elliot Metsger wrote: > >> Hey all, >> >> I'm having a little difficulty with the structure of the maven >> repository for pluto on Ibiblio (my sincere apologies if these issues >> were already hashed out for the rc4 cut): >> http://www.ibiblio.org/maven/org.apache.pluto/jars/. >> >> 1. Is the pluto-portal-1.0.1-rc4.jar missing from the iBiblio Maven >> repo? I see pluto-1.0.1-rc4.jar, pluto-deploy-1.0.1-rc4.jar, and >> pluto-descriptors-1.0.1-rc4.jar but not pluto-portal-1.0.1-rc4.jar. >> > It is missing - I downloaded our release, but we don't have a > pluto-portal-1.0.1-rc4.jar in there anymore. I think we should fix this > for the final release. I'll create the jar today and put it up on ibiblio. > >> So this causes some difficulty with projects like WSRP4J, where if you >> already have rc4 installed in a local repo, the WSRP4J project.xml >> files work fine - the dependencies are resolved. BUT, if you don't >> have rc4 already installed in a local repo, the dependancies can't be >> resolved (by IBiblio's repo) without editing WSRP4J's project.xml file >> and changing the groupid from: >> <dependency> >> <artifactId>pluto</artifactId> >> <groupId>pluto</groupId> >> <version>1.0.1-rc4</version> >> </dependency> >> to: >> <dependency> >> <artifactId>pluto</artifactId> >> <groupId>org.apache.pluto</groupId> >> <version>1.0.1-rc4</version> >> </dependency> >> >> Changing the groupId to "org.apache.pluto" allows WSRP4J to resolve >> the dependencies and retrieve them from IBiblio. But then you get >> stuck, unable to retrieve pluto-portal-1.0.1-rc4.jar. >> > For some reason, plut changed the group id to "org.apache.pluto", so I > think org.apache.pluto is the correct group id and wsrp4j should use > that one. I think in general, projects should use really unique > identifiers for the repository. > > Carsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDFJU7gyzZYflJelERAv6kAKCPBFRr0ualp02QfZvqeEcek7S29QCfSwTg 5SBFRGE2QQ9sjw9Q8SqSfTM= =mMN1 -----END PGP SIGNATURE-----
