XFire

CLONE -Maven 2 build usuable because of broken java.net repository

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

I'm using the xfire-all bundle in the global Maven repository :

http://mirrors.ibiblio.org/pub/mirrors/maven2/org/codehaus/xfire/xfire-all/1.2.4/

However, inside its pom, this bundle links to the java.net Maven repository :

<url>https://maven-repository.dev.java.net/nonav/repository</url>

Which makes Maven 2 try to download some dependencies from this java.net repository :

[INFO] Error building POM (may not be this project's POM).
Project ID: null:xfire-all:jar:1.2.4
Reason: Cannot find parent: org.codehaus.xfire:xfire-parent for project: null:xfire-all:jar:1.2.4

This fails as the org.codehaus.xfire bundles do not exist anymore on the java.net repository.

Please remove this link to the java.net repository, so that Maven uses the global repository (as normal), where all JARs exists.

Activity

Hide
Derrick Goodyear added a comment -

This still seems to be an issue. The repository should be removed from the pom file, because it tries to download it from there first. The manual work around is to download it manually from the maven central and manually install it in your local repository. This becomes a huge pain when dealing with continuous integration tools such as Hudson or CC as developers usually do not have the same permissions as the user who starts the continuous integration servers.

Show
Derrick Goodyear added a comment - This still seems to be an issue. The repository should be removed from the pom file, because it tries to download it from there first. The manual work around is to download it manually from the maven central and manually install it in your local repository. This becomes a huge pain when dealing with continuous integration tools such as Hudson or CC as developers usually do not have the same permissions as the user who starts the continuous integration servers.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated: