[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)]

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

Nuno Godinho de Matos edited comment on WFLY-4572 at 8/16/17 1:43 PM:
----------------------------------------------------------------------

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 dependencies 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 must be maven central results.
Only when I checked the download achieve link did I realize my mistake.

Finally, I also had issues with some files: 
I mention these files in:
https://issues.jboss.org/browse/WFLY-8954

Here is one example.
 jsf/multi-jsf-installer/src/main/resources/myfaces-undeploy.scr

The anti virus we have setup considers that these files are dangerous. 
Could be just an IT department thing, or it could be the extension of the file.

The effect was, that (a) git checout would file for these files with permission denied.
So you need to stop the scanner in fact.

(b) Even if you check them out, youll will later have read access errors with permission denied.
And this was a bit anoying since the anti virus tends to auto enable itself, no matter what you do.
:)
You can get short time windows to be mess around, but yeah...


Many thanks.



was (Author: nuno.godinhomatos):
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)