Hi Sitapati,

I have faced this issue before. Upgrading to Maven 3 and cleaning up my
existing ~/.m2 repository worked for me.

Regards,
Anuj

On Wed, May 30, 2012 at 5:18 PM, Sitapati das / Joshua J Wulf <
[email protected]> wrote:

> Thanks for the quick reply Fabian.
>
> [jwulf@radhe apache-stanbol-0.9.0-incubating]$ rpm -q maven
> maven-3.0.3-7.fc15.noarch
>
> Looks like that was maven 3.....
>
> On Wed, May 30, 2012 at 12:21 PM, Fabian Christ <
> [email protected]> wrote:
>
> > Hi,
> >
> > the problem is not directly related to Stanbol but to the Jersey
> > packages on Maven central. Someone moved (I don't know why people are
> > doing such things) the Jersey 1.7 artifacts on the Maven central
> > server after our 0.9.0-incubating release. The server responds with a
> > "Moved permanently" and points to the new location. The problem is
> > that Maven 2 seems not to handle this correctly which results in the
> > null values here
> >
> > Reason: Cannot find parent: com.sun.jersey:jersey-project for project:
> > null:jersey-server:bundle:null for project null:jersey-server:bundle:null
> >
> > Can you please try it with Maven 3?
> >
> > Best,
> >  - Fabian
> >
> > 2012/5/30 Sitapati das / Joshua J Wulf <[email protected]>:
> > > I downloaded 0.9.0-incubating + dependencies zips, unzipped them in the
> > > same place, then ran
> > >
> > >
> > > mvn clean install.
> > >
> > > I get the following error:
> > >
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Error building POM (may not be this project's POM).
> > >
> > >
> > > Project ID: null:jersey-server:bundle:null
> > >
> > > Reason: Cannot find parent: com.sun.jersey:jersey-project for project:
> > > null:jersey-server:bundle:null for project
> null:jersey-server:bundle:null
> > >
> > >
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] For more information, run Maven with the -e switch
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Total time: 52 seconds
> > > [INFO] Finished at: Wed May 30 11:17:07 EEST 2012
> > > [INFO] Final Memory: 120M/247M
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > >
> > >
> > > I tried mvn clean, then mvn clean install again. Same error.
> > >
> > > With stack trace on:
> > >
> > > Caused by:
> > org.apache.maven.artifact.resolver.ArtifactResolutionException:
> > > Unable to get dependency information: Unable to read the metadata file
> > for
> > > artifact 'com.sun.jersey:jersey-server:jar': Cannot find parent:
> > > com.sun.jersey:jersey-project for project:
> null:jersey-server:bundle:null
> > > for project null:jersey-server:bundle:null
> > >  com.sun.jersey:jersey-server:jar:1.7
> > >
> > > from the specified remote repositories:
> > >  apache.snapshots (http://repository.apache.org/snapshots),
> > >  central (http://repo1.maven.org/maven2),
> > >  __jpp_pom_repo__ (file:///usr/share/maven-poms),
> > >  __jpp_repo2__ (file:///usr/share/maven/repository),
> > >  __jpp_repo__ (file:///usr/share/maven2/repository)
> > >
> > > Path to dependency:
> > > 1)
> > >
> >
> org.apache.stanbol:org.apache.stanbol.commons.web.base:bundle:0.9.0-incubating
> > >
> > > Any pointers?
> > >
> > > thanks!
> >
> >
> >
> > --
> > Fabian
> > http://twitter.com/fctwitt
> >
>

Reply via email to