[
https://issues.jboss.org/browse/WFBUILD-14?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated WFBUILD-14:
----------------------------------
Description:
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
was:
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:
<dependencies>
<artifact name="org.wildfly:wildfly-feature-pack:9.0.1.Final" />
</dependencies>
Feature pack 'B' has a dependency on the WildFly 10 feature pack and also on
feature pack 'A'. E.g:
<dependencies>
<artifact name="org.wildfly:wildfly-feature-pack:10.0.0.CR3" />
<artifact name="org.foo:feature-pack-A" />
</dependencies>
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.
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
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)