[jira] Created: (XFIRE-1147) unresolved repository url in xfire-all 1.2.6 pom.xml

Discussion:

Alexander Stanik (JIRA)

2009-12-03 10:44:55 UTC

unresolved repository url in xfire-all 1.2.6 pom.xml
----------------------------------------------------

Key: XFIRE-1147
URL: http://jira.codehaus.org/browse/XFIRE-1147
Project: XFire
Issue Type: Bug
Affects Versions: 1.2.6
Reporter: Alexander Stanik
Assignee: Dan Diephouse
Priority: Blocker

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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Alexander Stanik (JIRA)

2009-12-03 10:44:55 UTC

Permalink

Havard Bjastad (JIRA)

2009-12-08 19:28:55 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201792#action_201792 ]

Havard Bjastad commented on XFIRE-1147:
---------------------------------------

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

Post by Alexander Stanik (JIRA)
unresolved repository url in xfire-all 1.2.6 pom.xml
----------------------------------------------------
Key: XFIRE-1147
URL: http://jira.codehaus.org/browse/XFIRE-1147
Project: XFire
Issue Type: Bug
Affects Versions: 1.2.6
Reporter: Alexander Stanik
Assignee: Dan Diephouse
Priority: Blocker
I have a dependency in my maven project to xfire-all version 1.2.6
Project ID: null:xfire-all:jar:1.2.6
null:xfire-all:jar:1.2.6 for project null:xfire-all:jar:1.2.6
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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Havard Bjastad (JIRA)

2009-12-08 19:28:55 UTC

Permalink

Viggo Navarsete (JIRA)

2009-12-08 20:14:55 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201797#action_201797 ]

Viggo Navarsete commented on XFIRE-1147:
----------------------------------------

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

Viggo Navarsete (JIRA)

2009-12-08 20:14:55 UTC

Permalink

Aaron Hamid (JIRA)

2010-01-19 18:52:55 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207520#action_207520 ]

Aaron Hamid commented on XFIRE-1147:
------------------------------------

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

Aaron Hamid (JIRA)

2010-01-19 18:52:55 UTC

Permalink

Bogdan MINCIU (JIRA)

2010-06-20 14:22:13 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225907#action_225907 ]

Bogdan MINCIU commented on XFIRE-1147:
--------------------------------------

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. Hope it helps you too.

Regards,
Bogdan.

Bogdan MINCIU (JIRA)

2010-06-20 14:22:13 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225907#action_225907 ]

Bogdan MINCIU commented on XFIRE-1147:
--------------------------------------

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. Hope it helps you too.

Regards,
Bogdan.

Bogdan MINCIU (JIRA)

2010-06-20 15:41:13 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225907#action_225907 ]

Bogdan MINCIU edited comment on XFIRE-1147 at 6/20/10 10:40 AM:
----------------------------------------------------------------

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.

was (Author: bogdan.minciu):
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. Hope it helps you too.

Regards,
Bogdan.

Bogdan MINCIU (JIRA)

2010-06-20 15:41:13 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225907#action_225907 ]

Bogdan MINCIU edited comment on XFIRE-1147 at 6/20/10 10:40 AM:
----------------------------------------------------------------

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.

was (Author: bogdan.minciu):
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. Hope it helps you too.

Regards,
Bogdan.

Dave Garcia (JIRA)

2010-08-09 17:29:33 UTC

Permalink

[ http://jira.codehaus.org/browse/XFIRE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231499#action_231499 ]

Dave Garcia commented on XFIRE-1147:
------------------------------------

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

Dave Garcia (JIRA)

2010-08-09 17:29:33 UTC

Permalink