Yes, this specific pom is corrupt and is not a valid xml document (missing entity declaration). You can either take the good version from codehaus (by placing it above repo1 in the remote repo list) or remove the offending character and deploy it to one of the local repositories.
On Thursday, January 7, 2010, David Binder <[email protected]> wrote: > hey I found why it was screwed > <developer> > <name>Trygve Laugstøl</name> > <id>trygvis</id> > <email>[email protected]</email> > <roles> > <role>Developer</role> > </roles> > </developer> > > second line is the problem, at sometime, somehow the pom is parsed and > ø is not recognized as a character. > > > > 2010/1/6 David Binder <[email protected]> > > the artifact is not in codehaus repository (who said weird ?) > > I manages to get some log I didn't see cause of the small console I used, it > logs the remote download of proxied artifacts may be this can be of some help > > 2010-01-06 23:08:27,562 [btpool0-7] [INFO ] (o.a.r.HttpRepo :156) - > nexus-indexer: Retrieving > 'http://repository.sonatype.org/content/groups/public/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom'... > 2010-01-06 23:08:27,968 [btpool0-7] [INFO ] (o.a.r.HttpRepo :156) - > nexus-indexer: Retrieving > 'http://repository.sonatype.org/content/groups/public/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom.sha1'... > 2010-01-06 23:08:27,984 [btpool0-7] [INFO ] (o.a.r.HttpRepo :173) - > nexus-indexer: Retrieved > 'http://repository.sonatype.org/content/groups/public/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom.sha1' > with return code: 200. > 2010-01-06 23:08:28,265 [btpool0-7] [INFO ] (o.a.r.HttpRepo :156) - > nexus-indexer: Retrieving > 'http://repository.sonatype.org/content/groups/public/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom.md5'... > 2010-01-06 23:08:28,281 [btpool0-7] [INFO ] (o.a.r.HttpRepo :173) - > nexus-indexer: Retrieved > 'http://repository.sonatype.org/content/groups/public/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom.md5' > with return code: 200. > 2010-01-06 23:08:28,296 [btpool0-7] [WARN ] > (o.a.c.x.EntityResolvingContentHandler:121) - Received the following error > during xml parsing: 'The entity "oslash"was referenced, but not declared.'. > 2010-01-06 23:08:28,312 [btpool0-7] [INFO ] (o.a.r.HttpRepo :173) - > nexus-indexer: Retrieved > 'http://repository.sonatype.org/content/groups/public/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom' > with return code: 200. > 2010-01-06 23:08:28,328 [btpool0-7] [WARN ] (o.a.j.JcrServiceImpl:38) - > Ignoring bad XML stream while importing > '/repositories/plugins-releases/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom/artifactory:xml': > Invalid byte 1 of 1-byte UTF-8 sequence.. > 2010-01-06 23:08:28,328 [btpool0-7] [WARN ] (o.a.r.j.StoringRepoMixin:451) - > IO error while trying to save resource > plugins-releases:org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom'': Invalid > byte 1 of 1-byte UTF-8 sequence. > > 2010/1/6 Frederic Simon <[email protected]> > > > Hi,The valid plexus pom file may come from codehaus remote repo and not > repo1. That's why artifactory/repo successfully downloaded it. If you had the > codehaus remote repo to the list of repositories in the virtuals > ( plugins-releases <http://localhost:8081/artifactory/plugins-releases/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom>, libs-snapshots, libs <http://localhost:8081/artifactory/libs-snapshots/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom>-releases <http://localhost:8081/artifactory/plugins-releases/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom>, plugins-snapshots <http://localhost:8081/artifactory/libs-snapshots/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom>) > or more easily the virtual remote-repos, and make sure it is place before > repo1, it may solve your problem. > > > > On Wed, Jan 6, 2010 at 9:44 PM, David Binder < > -- Yoav Landman Artifactory Creator Co-founder and Product Development Lead JFrog Ltd. http://www.jfrog.org/ ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
