[
https://issues.jboss.org/browse/WFLY-10157?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-10157:
-----------------------------------------
This is an RFE and involves a big change in how the server is built.
The WildFly build brings in the core feature pack as a whole, including its dependencies,
it does not rebuild it. WFLY-9911 was not about changing that. It simply changed the
location where the dependencies the full build directly controls are declared.
version of the modules defined in wildfly core cannot be overrided in
wildfly full build
----------------------------------------------------------------------------------------
Key: WFLY-10157
URL:
https://issues.jboss.org/browse/WFLY-10157
Project: WildFly
Issue Type: Bug
Components: Build System
Environment: latest WildFly master (commit id:
0565fe6a47a121f5d25e4810572a2d6f277420bc)
latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219)
Reporter: Lin Gao
I suppose it is a bug but not for sure.
After WFLY-9911 is resolved, I think we are able to override version of modules defined
in wildfly-core at maven build time too.
Like:
{code:java}
mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT
-Dversion.io.undertow=2.0.2.Final
{code}
should produce module: io.undertow.core:2.0.2.Final instead of
io.undertow.core:2.0.3.Final which is defined in the wildfly-core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)