[jboss-dev-forums] [Design the new POJO MicroContainer] - Maven build broken again - Microcontainer
adrian@jboss.org
do-not-reply at jboss.com
Thu Jan 24 13:38:08 EST 2008
I just resynched with the MC trunk.
It said it couldn't find jdocbook
| Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plugin/2.0.0/maven-jdocbook-plugin-2.0.0.pom
| [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2)
| Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plugin/2.0.0/maven-jdocbook-plugin-2.0.0.pom
| [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2)
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] Failed to resolve artifact.
|
| GroupId: org.jboss.maven.plugins
| ArtifactId: maven-jdocbook-plugin
| Version: 2.0.0
|
| Reason: Unable to download the artifact from any repository
|
| org.jboss.maven.plugins:maven-jdocbook-plugin:pom:2.0.0
|
| from the specified remote repositories:
| central (http://repo1.maven.org/maven2)
|
I thought it was my repository broken again, so I nuked it
and then I got
| Downloading: http://repo1.maven.org/maven2/org/jboss/jboss-parent/3/jboss-parent-3.pom
| [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2)
| [INFO] ------------------------------------------------------------------------
| [ERROR] FATAL ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] Failed to resolve artifact.
|
| GroupId: org.jboss
| ArtifactId: jboss-parent
| Version: 3
|
| Reason: Unable to download the artifact from any repository
|
| org.jboss:jboss-parent:pom:3
|
| from the specified remote repositories:
| central (http://repo1.maven.org/maven2)
|
Which told me it wasn't even looking at the jboss repository(ies).
Adding the repositories into the root pom.xml as well a the build/pom.xml
seems to have fixed the problem, but this is either:
1) Somebody updating the poms without testing it properly
2) Maven showing different results for different people
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123161#4123161
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123161
More information about the jboss-dev-forums
mailing list