• Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: EAP 6.0.1 ER 3
    • Fix Version/s: EAP 6.0.1
    • Component/s: Web Services
    • Labels:


      While having a look at JBPAPP-10313, I analysed the dependency:tree of the artifact and noticed a problem with spring dependencies. I'm sure I mentioned this in the past (and the issue might already be in previous EAP version), can't remember if a jira was already created or not... sorry.
      The problem is that that artifact is not supposed to come with compile scope dependencies to spring artifacts. If you look at the 4.0.6.GA pom at [1] you see those dependencies, however they are with 'provided' scope given the definition in the parent pom at [2]. The same check on the productized versions of those artifacts [3][4] reveals that the dependency management block which are supposed to control the spring dependency scope are missing, hence the dependencies show up as 'compile' scope ones.
      The net effect of this is that any client application setting the dependency only (please note that's the convenient and suggested way in community for setting ws dependencies in a maven environment) ends up using Spring version of the jbossws-cxf integration, while it shouldn't unless users explicitly set spring artifacts dependencies. The dependency tree is altered.

      Generally speaking, the productization process should make sure the scope of dependencies is not altered. Dependency scopes reflects the fact a dependency is required at compile or runtime.


        Gliffy Diagrams




              • Assignee:
                pgier Paul Gier
                asoldano Alessio Soldano
              • Votes:
                0 Vote for this issue
                5 Start watching this issue


                • Created: