[jboss-jira] [JBoss JIRA] (WFBUILD-14) Conflicting feature pack dependency versions should not be allowed

[Thomas Diesler (JIRA)]

     [ https://issues.jboss.org/browse/WFBUILD-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler closed WFBUILD-14.
---------------------------------
    Resolution: Won't Fix


[10:24 AM] Thomas Diesler: My dep chain is wildfly-camel => fuse-patch + wildlfy, fuse-patch => wildfly. The versions of wildfly may be different. What should happen?
[10:24 AM] Thomas Diesler: The obvious thing to happen is an error, right?
[10:26 AM] Stuart Douglas: yes
[10:26 AM] Thomas Diesler: Another option is that the higher version of wildfly is used, if both are version compatible
[10:26 AM] Stuart Douglas: we don't know what is compatible
[10:26 AM] Stuart Douglas: error is the only this that really makes sense
[10:26 AM] Stuart Douglas: @AlexeyLoubyansky is actually working on version two of this
[10:27 AM] Stuart Douglas: so it is unlikely that there is going to be any big changes in the current code base
[10:27 AM] Thomas Diesler: Yep, I would agree. In that case this issue is reduced to a "does not fail" thing, which can be resolved as "won't fix"

https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc


> Conflicting feature pack dependency versions should not be allowed
> ------------------------------------------------------------------
>
>                 Key: WFBUILD-14
>                 URL: https://issues.jboss.org/browse/WFBUILD-14
>             Project: WildFly Build Tools
>          Issue Type: Bug
>            Reporter: James Netherton
>            Assignee: Stuart Douglas
>             Fix For: 1.1.7.Final
>
>
> There was a brief discussion about this on the WildFly dev mailing list so I'm capturing the problem here as well.
> Consider the following.
> Feature pack 'A' has a dependency on the WildFly 9 feature pack. E.g:
> {code:xml}
> <dependencies>
>   <artifact name="org.wildfly:wildfly-feature-pack:9.0.1.Final" />
> </dependencies>
> {code}
> Feature pack 'B' has a dependency on the WildFly 10 feature pack and also on feature pack 'A'. E.g:
> {code:xml}
> <dependencies>
>   <artifact name="org.wildfly:wildfly-feature-pack:10.0.0.CR3" />
>   <artifact name="org.foo:feature-pack-A" />
> </dependencies>
> {code}
> The result is that you'll have overlapping and possibly problematic non-overlapping file paths coming from the conflicting WildFly versions
> At the moment the plugins allow this scenario, which can lead to all sorts of horrors when using the server-provisioning plugin to provision an app server.
> CrossRef: https://github.com/wildfly-extras/fuse-patch/issues/101



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)