Well the pom already had this declaration in it:
<!-- get every artifact through maven.glassfish.org, which proxies all the artifacts that we need -->
<repositories>
<repository>
<id>m.g.o-public</id>
<url>http://maven.glassfish.org/content/groups/public/</url>
</repository>
</repositories>

<pluginRepositories>
<pluginRepository>
<id>m.g.o-public</id>
<url>http://maven.glassfish.org/content/groups/public/</url>
</pluginRepository>
</pluginRepositories>

Which I would have assumed it would suffice. None the less I tried your suggestion and I still get the failure: Downloading: http://download.java.net/maven/2//org/kohsuke/stapler/stapler/1.167/stapler-1.167.jar [INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.kohsuke.stapler:stapler:jar:1.167

  Try downloading the file manually from the project website.

  Then, install it using the command:
mvn install:install-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler -Dversion=1.167 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler -Dversion=1.167 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
      1) com.nirima.jenkins.repository:pom:pom:0.6.2-SNAPSHOT
      2) org.jenkins-ci.main:jenkins-core:jar:1.417
      3) org.kohsuke.stapler:stapler-adjunct-timeline:jar:1.3
      4) org.kohsuke.stapler:stapler:jar:1.167

----------
1 required artifact is missing.

for artifact:
  com.nirima.jenkins.repository:pom:pom:0.6.2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  m.g.o-public (http://maven.glassfish.org/content/groups/public/),
jboss-public-repository-group (http://maven.glassfish.org/content/groups/public/)



Could something be wrong with the repository itself?

On 10/15/2011 12:21 AM, Mark Struberg wrote:
Hi!

it seems that this repository is not listed in the projects pom. So it seems to 
be assumed that you add the following analog for what I did for the jboss repos 
to your ~/.m2/settings.xml:

<profiles>
       <profile>
           <id>jbossrepo</id>
           <repositories>
               <repository>
                   <id>jboss-public-repository-group</id>
                   <name>JBoss Public Repository Group</name>
                   
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
                   <layout>default</layout>
                   <releases>
                       <enabled>true</enabled>
                       <updatePolicy>never</updatePolicy>
                   </releases>
                   <snapshots>
                       <enabled>true</enabled>
                       <updatePolicy>never</updatePolicy>
                   </snapshots>
               </repository>
           </repositories>
           <pluginRepositories>
               <pluginRepository>
                   <id>jboss-public-repository-group</id>
                   <name>JBoss Public Repository Group</name>
                   
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
                   <releases>
                       <enabled>true</enabled>
                   </releases>
                   <snapshots>
                       <enabled>true</enabled>
                   </snapshots>
               </pluginRepository>
           </pluginRepositories>
       </profile>
   </profiles>

just change the profilename to 'glassfishrepo' and use the URL as you need it.

Then start maven with this profile activated:

$ mvn clean install -Pglassfishrepo
LieGrue,
strub

----- Original Message -----

From: Mike Power<[email protected]>
To: Maven Users List<[email protected]>
Cc:
Sent: Saturday, October 15, 2011 7:00 AM
Subject: maven failing to resolve artifact that exists in repository

I am really confused.  Maven is failing to resolve an artifact that I can easily
find in the remote repository.

I am trying to build an open source project whose git repository is found at

https://github.com/magnayn/Jenkins-Repository.git

I get the following error:
Downloading:
http://download.java.net/maven/2//org/kohsuke/stapler/stapler/1.167/stapler-1.167.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.kohsuke.stapler:stapler:jar:1.167

   Try downloading the file manually from the project website.

   Then, install it using the command:
       mvn install:install-file -DgroupId=org.kohsuke.stapler
-DartifactId=stapler -Dversion=1.167 -Dpackaging=jar -Dfile=/path/to/file

   Alternatively, if you host your own repository you can deploy the file there:
       mvn deploy:deploy-file -DgroupId=org.kohsuke.stapler -DartifactId=stapler
-Dversion=1.167 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

   Path to dependency:
       1) com.nirima.jenkins.repository:pom:pom:0.6.2-SNAPSHOT
       2) org.jenkins-ci.main:jenkins-core:jar:1.417
       3) org.kohsuke.stapler:stapler-adjunct-timeline:jar:1.3
       4) org.kohsuke.stapler:stapler:jar:1.167

----------
1 required artifact is missing.

for artifact:
   com.nirima.jenkins.repository:pom:pom:0.6.2-SNAPSHOT

from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   m.g.o-public (http://maven.glassfish.org/content/groups/public/)
*
*

It seems to be only trying central.  However it is not available on central.  It
is available on m.g.o-public.  Here is the url:
http://maven.glassfish.org/content/groups/public/org/kohsuke/stapler/stapler/1.161/stapler-1.161.jar

Why is maven going to central to find the jar, and not going to m.g.o-public? It says it tried m.g.o-public but I do not see that happening.*
*

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to