XFire

unresolved repository url in xfire-all 1.2.6 pom.xml

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Blocker Blocker
  • Resolution: Unresolved
  • Affects Version/s: 1.2.6
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

I have a dependency in my maven project to xfire-all version 1.2.6

wenn i run "mvn compile", the build aborts with the message:

Project ID: null:xfire-all:jar:1.2.6

Reason: Cannot find parent: org.codehaus.xfire:xfire-parent for project:
null:xfire-all:jar:1.2.6 for project null:xfire-all:jar:1.2.6

I think the problem is the repository url in:
http://repository.codehaus.org/org/codehaus/xfire/xfire-all/1.2.6/xfire-all-1.2.6.pom

Because the repository https://maven-repository.dev.java.net/nonav/repository not exist
and Maven try to download the xfire-parent form this repository.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Havard Bjastad added a comment -

This problem affects older versions, too, we're experiencing it with 1.2.2
Should be easy to fix for the maintainers - please fix!

Show
Havard Bjastad added a comment - This problem affects older versions, too, we're experiencing it with 1.2.2 Should be easy to fix for the maintainers - please fix!
Hide
Permalink
Viggo Navarsete added a comment -

This issue also relates to the following issue (which couldn't be reproduced): http://jira.codehaus.org/browse/XFIRE-837

Show
Viggo Navarsete added a comment - This issue also relates to the following issue (which couldn't be reproduced): http://jira.codehaus.org/browse/XFIRE-837
Hide
Permalink
Aaron Hamid added a comment -

this is biting us too...what is the workaround...can the artifact/pom be obtained elsewhere?

Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.codehaus.xfire:xfire-parent for project: null:xfire-all:jar:1.2.6 for project null:xfire-all:jar:1.2.6

Show
Aaron Hamid added a comment - this is biting us too...what is the workaround...can the artifact/pom be obtained elsewhere? Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.codehaus.xfire:xfire-parent for project: null:xfire-all:jar:1.2.6 for project null:xfire-all:jar:1.2.6
Hide
Permalink
Bogdan MINCIU added a comment - - edited

The xfire-parent-1.2.6.pom file inside my local maven repo contains this:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://download.java.net/maven/1/org.codehaus.xfire/poms/xfire-parent-1.2.6.pom">here</a>.</p>
<hr>
<address>Apache Server at maven-repository.dev.java.net Port 443</address>
</body></html>

So, as a workaround I manually downloaded this file: http://repository.codehaus.org/org/codehaus/xfire/xfire-parent/1.2.6/xfire-parent-1.2.6.pom and copied over the file in my local repo. This solved the problem for the moment. Hope it helps you too.

You may also experience the same problem with jar files (xfire-aegis, xfire-annotations, xfire-core, etc.).

Regards,
Bogdan.

Show
Bogdan MINCIU added a comment - - edited The xfire-parent-1.2.6.pom file inside my local maven repo contains this: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="http://download.java.net/maven/1/org.codehaus.xfire/poms/xfire-parent-1.2.6.pom">here</a>.</p> <hr> <address>Apache Server at maven-repository.dev.java.net Port 443</address> </body></html> So, as a workaround I manually downloaded this file: http://repository.codehaus.org/org/codehaus/xfire/xfire-parent/1.2.6/xfire-parent-1.2.6.pom and copied over the file in my local repo. This solved the problem for the moment. Hope it helps you too. You may also experience the same problem with jar files (xfire-aegis, xfire-annotations, xfire-core, etc.). Regards, Bogdan.
Hide
Permalink
Dave Garcia added a comment -

Hi guys,

I found a (dirty) trick that could help. Using mirrors when maven is fetching from inexistent repository and it fails, it will try with to re-fetch using the mirror url.

Adding the following info inside settings.xml (or creating if not existed) on your .m2 dir should work

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">

<mirrors>
<mirror>
<id>ibiblio.org</id>
<name>ibiblio Mirror of http://repo1.maven.org/maven2/</name>
<url>http://repo1.maven.org/maven2/</url>
<mirrorOf>java.net</mirrorOf>
</mirror>
</mirrors>
</settings>

Best regards

Dave

Show
Dave Garcia added a comment - Hi guys, I found a (dirty) trick that could help. Using mirrors when maven is fetching from inexistent repository and it fails, it will try with to re-fetch using the mirror url. Adding the following info inside settings.xml (or creating if not existed) on your .m2 dir should work <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <mirrors> <mirror> <id>ibiblio.org</id> <name>ibiblio Mirror of http://repo1.maven.org/maven2/</name> <url>http://repo1.maven.org/maven2/</url> <mirrorOf>java.net</mirrorOf> </mirror> </mirrors> </settings> Best regards Dave

People

Vote (4)
Watch (1)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.