[jboss-jira] [JBoss JIRA] Commented: (AS7-1403) Excluded/Banned transitive dependencies for Maven Dependency Resolver are too strict

[Karel Piwko (JIRA)]

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

Karel Piwko commented on AS7-1403:
----------------------------------

I'll try to reword that:

ShrinkWrap Dependency Resolver (SWR) dependencies were not flattened and shrinkwrap-resolver-impl-maven got to the jboss-as-parent bom as a part of ShrinkWrap project. 

If user wants to use SWR in AS7, he has to add all its dependencies manually, as its dependencies were excluded and banned. These excluded dependencies are required for SWR to run, but nobody mentioned that because at time of the excluded/banned list creation this library was not used in any tests.

My point is that it would make much more sense:

1/ Use SWR as an external utility, e.g. not mentioned in jboss-as-parent at all. This way user can simply include only shrinkwrap-resolver-impl-maven at place where he wants to use it

2/ If dependency control is requirement, I can flatten shrinkwrap-resolver-impl end explicitly enumerate all required dependecies there. Then jboss-as-parent will have to be modified (e.g. remove excludes from shrinkwrap-resolver-impl). This way user can simply include shrinkwrap-resolver-impl-amven at place where you wants to use it and you get the dependency control.




> Excluded/Banned transitive dependencies for Maven Dependency Resolver are too strict
> ------------------------------------------------------------------------------------
>
>                 Key: AS7-1403
>                 URL: https://issues.jboss.org/browse/AS7-1403
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 7.0.0.Final
>            Reporter: Karel Piwko
>            Assignee: Paul Gier
>
> During 7.0.0.CR1 build, there was a decision to remove transitive dependencies from other projects and exclude/ban them in jboss-as-parent.
> This decision has effectively crippled usage of Maven Dependency Resolver, which wasn't used in CR1-date based testsuite, so the change passed silently. 
> If user wants to use the ShrinkWrap Dependency Resolver in the AS7 testsuite, he won't get the required transitive dependencies, such as wagon or aether, so the resolver is unusable.
> According to disscussion with Vladimir, it would help "to flatten" dependency tree for ShrinkWrap dependency Resolver, however, that's only the part of the solution, the restrictions posed in AS7 parent must be relaxed afterwards.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira