[forge-issues] [JBoss JIRA] (FORGE-2062) Aether can't find artifact when using -Dmaven.repo.local

[Ondrej Zizka (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012624#comment-13012624 ] 

Ondrej Zizka commented on FORGE-2062:
-------------------------------------

The original exception is gone. However, this appears now:

(18:26:12) ozizka-FN: Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.slf4j:slf4j-jdk14:jar:1.7.2 in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/)
(18:26:12) ozizka-FN:         at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$6.wrap(WagonRepositoryConnector.java:1012)
...

There's no mention of that in Windup codebase. The dependency tree also doesn't show that.
So, not sure where is this coming from.

I've run a build against clean repo and checked where it appears:

{code}
ondra at lenovo:~/work/Migration/Windup$ grep -R  slf4j-jdk localRepoAA/
localRepoAA/com/github/jsonld-java/jsonld-java-parent/0.3/jsonld-java-parent-0.3.pom:                           <artifactId>slf4j-jdk14</artifactId>
localRepoAA/com/github/jsonld-java/jsonld-java/0.3/jsonld-java-0.3.pom:                 <artifactId>slf4j-jdk14</artifactId>
localRepoAA/com/github/jsonld-java/jsonld-java-sesame/0.3/jsonld-java-sesame-0.3.pom:                   <artifactId>slf4j-jdk14</artifactId>
localRepoAA/org/jboss/forge/furnace/container/cdi-parent/2.12.0.Final/cdi-parent-2.12.0.Final.pom:            <artifactId>slf4j-jdk14</artifactId>
localRepoAA/org/slf4j/slf4j-parent/1.7.2/slf4j-parent-1.7.2.pom:    <module>slf4j-jdk14</module>
localRepoAA/org/slf4j/slf4j-parent/1.7.2/slf4j-parent-1.7.2.pom:        <artifactId>slf4j-jdk14</artifactId>
localRepoAA/org/slf4j/slf4j-parent/1.5.6/slf4j-parent-1.5.6.pom:                <module>slf4j-jdk14</module>
localRepoAA/org/slf4j/slf4j-parent/1.6.1/slf4j-parent-1.6.1.pom:                <module>slf4j-jdk14</module>
localRepoAA/org/slf4j/slf4j-parent/1.6.1/slf4j-parent-1.6.1.pom:        <artifactId>slf4j-jdk14</artifactId>
localRepoAA/org/slf4j/slf4j-parent/1.7.5/slf4j-parent-1.7.5.pom:    <module>slf4j-jdk14</module>
localRepoAA/org/slf4j/slf4j-parent/1.7.5/slf4j-parent-1.7.5.pom:        <artifactId>slf4j-jdk14</artifactId>
localRepoAA/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.pom:  <artifactId>slf4j-jdk14</artifactId>
localRepoAA/org/slf4j/slf4j-jdk14/1.5.6/_remote.repositories:slf4j-jdk14-1.5.6.jar>central=
localRepoAA/org/slf4j/slf4j-jdk14/1.5.6/_remote.repositories:slf4j-jdk14-1.5.6.pom>central=
Binary file localRepoAA/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar matches
localRepoAA/org/openrdf/sesame/sesame/2.7.10/sesame-2.7.10.pom:                         <artifactId>slf4j-jdk14</artifactId>
{code}

> Aether can't find artifact when using -Dmaven.repo.local
> --------------------------------------------------------
>
>                 Key: FORGE-2062
>                 URL: https://issues.jboss.org/browse/FORGE-2062
>             Project: Forge
>          Issue Type: Bug
>            Reporter: Ondrej Zizka
>
> When building the Windup project, the tests fail if using local Maven repo - Forge can't find certain dependency. I'm not sure how local repo setting is passed, but according to Lincoln, it should propagate - it's used in Forge tests.
> Compare these two jobs (the second uses -Dmaven.repo.local=localRepo):
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Windup/job/Windup-daily/191/
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Windup/job/Windup-daily/192/



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)