[JBoss JIRA] (WFLY-13623) Organize feature pack code to facilitate separate EE 8 and EE 9 variants
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13623?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFCORE-5026 to WFLY-13623:
-------------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-13623 (was: WFCORE-5026)
Component/s: Build System
(was: Build System)
Fix Version/s: 21.0.0.Beta1
(was: 13.0.0.Beta1)
> Organize feature pack code to facilitate separate EE 8 and EE 9 variants
> ------------------------------------------------------------------------
>
> Key: WFLY-13623
> URL: https://issues.redhat.com/browse/WFLY-13623
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others.
> See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have.
> License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13623) Organize feature pack code to facilitate separate EE 8 and EE 9 variants
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13623?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13623:
------------------------------------
Description:
Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others.
See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have.
was:
Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others.
See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have.
License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well.
> Organize feature pack code to facilitate separate EE 8 and EE 9 variants
> ------------------------------------------------------------------------
>
> Key: WFLY-13623
> URL: https://issues.redhat.com/browse/WFLY-13623
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others.
> See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months