[
https://issues.jboss.org/browse/WFLY-4572?page=com.atlassian.jira.plugin....
]
Nuno Godinho de Matos commented on WFLY-4572:
---------------------------------------------
I forked wildfly from git hub.
Finally, on my local git repository I have branched the 10.X branch.
And the 10.x branch is what I have tried to build.
Two issues I experienced.
The first was the problem resolving of dependnecies that were well available on the
red-hat public repository.
I was a bit surprised, because in the:
https://mvnrepository.com/
I was getting results and at first I suspected these results must be maven central
results.
Finally, I also had issues with some files:
see
https://issues.jboss.org/browse/WFLY-8954
E.g.
jsf/multi-jsf-installer/src/main/resources/myfaces-undeploy.scr
The anti virus we have setup considered these files as dangerous. So you could check them
out of the repository.
Nor if they were checked out could you access them ... and since our antivirus kicks in
automatically, it can be an interesting dance.
Many thanks.
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)