You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by Yujin Kim <ne...@gmail.com> on 2005/09/01 22:29:11 UTC
Re: issue with maven repo on ibiblio
Is it possible to distribute the pluto driver and tools (war files) to
maven as well?
this will be useful so people can just download the maven script and
build pluto with a single maven goal.
thanks
On 8/31/05, David H. DeWolf <dd...@apache.org> wrote:
>
>
> Carsten Ziegeler wrote:
> > 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.
>
> AFAIK we never had a seperate jar for the portal in the maven repo. It
> was recently added manually. See this thread:
>
> http://mail-archives.apache.org/mod_mbox/portals-pluto-dev/200508.mbox/%3C42F95568.6090007@apache.org%3E
> >
> >
> >>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.
>
>
> This change was recomended by the maven people! Jeremy submitted a
> patch for it and it seemed reasonable to me.
>
> >
> > Carsten
>
>
Re: issue with maven repo on ibiblio
Posted by "David H. DeWolf" <dd...@apache.org>.
Hmm, i thought these were allready there. let me look into this.
David
Yujin Kim wrote:
> Is it possible to distribute the pluto driver and tools (war files) to
> maven as well?
> this will be useful so people can just download the maven script and
> build pluto with a single maven goal.
>
> thanks
>
> On 8/31/05, David H. DeWolf <dd...@apache.org> wrote:
>
>>
>>Carsten Ziegeler wrote:
>>
>>>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.
>>
>>AFAIK we never had a seperate jar for the portal in the maven repo. It
>>was recently added manually. See this thread:
>>
>>http://mail-archives.apache.org/mod_mbox/portals-pluto-dev/200508.mbox/%3C42F95568.6090007@apache.org%3E
>>
>>>
>>>>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.
>>
>>
>>This change was recomended by the maven people! Jeremy submitted a
>>patch for it and it seemed reasonable to me.
>>
>>
>>>Carsten
>>
>>
>