[jboss-jira] [JBoss JIRA] (WFLY-4572) wildfly-arquillian uses slf4j-api:1.7.7.jbossorg-1 which is not available in maven central repository

Nuno Godinho de Matos (JIRA) issues at jboss.org
Wed Aug 16 05:10:01 EDT 2017


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

Nuno Godinho de Matos edited comment on WFLY-4572 at 8/16/17 5:09 AM:
----------------------------------------------------------------------

One question, while trying to build wildfly locally using the build bat, I am confronted with unfound dependenicies.

So now trying to do the following on my local machine:

{panel}
SET GROUP_ID=org.slf4j
SET ARTIFACT_ID=slf4j-api
SET ARTIFACT_VERSION=1.7.7.jbossorg-1
mvn org.apache.maven.plugins:maven-dependency-plugin:copy -Dmdep.useBaseVersion=true -DoutputAbsoluteArtifactFilename -DoutputDirectory=%WORKING_DIR%  -Dartifact=%GROUP_ID%:%ARTIFACT_ID%:%ARTIFACT_VERSION%
{panel}

I end up getting that this artifact is not to be found in the remote repositories.


I am getting this for multiple artifacts.

Now  looking at the mirror file system:
http://uk.maven.org/maven2/org/slf4j/slf4j-api/

We can see that this true the dependencyh is not there.
But looking at maven central page.
https://mvnrepository.com/artifact/org.slf4j/slf4j-api/1.7.7.jbossorg-1

The dependency should be found.
What exactly is going on?

Kindest regards.


was (Author: nuno.godinhomatos):
One question, while trying to build wildfly locally using the build bat, I am confronted with unfound dependenicies.

So now trying to do the following on my local machine:

{panel}
SET GROUP_ID=org.slf4j
SET ARTIFACT_ID=slf4j-api
SET ARTIFACT_VERSION=1.7.7.jbossorg-1
mvn org.apache.maven.plugins:maven-dependency-plugin:copy -Dmdep.useBaseVersion=true -DoutputAbsoluteArtifactFilename -DoutputDirectory=%WORKING_DIR%  -Dartifact=%GROUP_ID%:%ARTIFACT_ID%:%ARTIFACT_VERSION%
{panel}

I end up getting that this artifact is not to be found in the remote repositories.

{panel}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:copy (default-cli) on project standalone-pom: Unable to resolve artifact. Could not transfer art
ifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 from/to snapshots (http://repository.scdc.swisslog.com:8080/nexus/content/repositories/snapshots/): Failed to transfer file: http://r
epository.scdc.swisslog.com:8080/nexus/content/repositories/snapshots/org/slf4j/slf4j-api/1.7.7.jbossorg-1/slf4j-api-1.7.7.jbossorg-1.jar. Return code is: 400 , ReasonPhrase:Reposi
tory version policy: SNAPSHOT does not allow version: 1.7.7.jbossorg-1.
{panel}

I am getting this for multiple artifacts.

Now  looking at the mirror file system:
http://uk.maven.org/maven2/org/slf4j/slf4j-api/

We can see that this true the dependencyh is not there.
But looking at maven central page.
https://mvnrepository.com/artifact/org.slf4j/slf4j-api/1.7.7.jbossorg-1

The dependency should be found.
What exactly is going on?

Kindest regards.

> wildfly-arquillian uses slf4j-api:1.7.7.jbossorg-1 which is not available in maven central repository
> -----------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-4572
>                 URL: https://issues.jboss.org/browse/WFLY-4572
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 8.2.0.Final, 9.0.0.Beta2
>            Reporter: Martin Kouba
>            Assignee: James Perkins
>             Fix For: 9.0.0.CR1
>
>
> GAV: {{org.slf4j:slf4j-api:1.7.7.jbossorg-1}}
> As a result, it's not possible to build a project which depends on some referencing module, e.g. {{wildfly-arquillian-common}}, and does not define JBoss repository at the same time.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list