-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
+
-
-
Subtask 1
Currently when anybody wants to use the wildfly-channel-maven-plugin to align dependencies versions in the pom.xml according to a manifest file, full configuration for the plugin needs to be provided in the maven command:
mvn org.wildfly:wildfly-channel-maven-plugin:upgrade \ -DmanifestFile=path/to/eap8-manifest.yaml \ -DignoreModules=org.jboss.eap:wildfly-legacy-ee-bom \ -DignorePropertiesPrefixedWith=legacy. \ -DignoreProperties=version.org.glassfish.jaxb.jaxb-runtime
The plugin now has an ability to read the configuration from the .wildfly-channel-maven-plugin file located in the root of the project. After this file is merged in the jboss-eap8 repository, the maven call can be simplified to this:
mvn org.wildfly:wildfly-channel-maven-plugin:upgrade \ -DmanifestFile=path/to/eap8-manifest.yaml
...simplifying peoples lifes.
Subtask 2
Provide a script to perform the dependency alignment, like:
align-dependencies.sh [path/to/manifest.yaml]
Without manifest path use default manifest GAV?
Subtask 3
Update README file to describe that dependencies may need to be aligned and how to do it.
- is cloned by
-
JBEAP-26106 (8.0.z) Add the wildfly-channel-maven-plugin configuration file to the wildfly-core-eap git repo
- Closed
- is duplicated by
-
JBEAP-26707 (8.0.z) Document latest local EAP provisioning
- Closed