-
Task
-
Resolution: Done
-
Major
-
None
-
None
Currently core is installed implicitly as a dependency of wildfly and servlet. We use resolve-local elements in provision goal config for core and servlet feature-packs. Those are shortcuts to avoid the universe-based feature-pack resolver.
If instead of resolve-local elements we use feature-pack/transitive elements we will achieve the same effect avoiding the universe-based resolver and it will also allow us to specify the version of core using a system property.
The only difference will show up in .galleon/provisioning.xml, which will change from (based on build module)
<installation xmlns="urn:jboss:galleon:provisioning:2.0"> <feature-pack location="wildfly@maven(org.jboss.universe:community-universe):current#14.0.0.Beta2-SNAPSHOT"> <packages> <include name="docs.examples.configs"/> </packages> </feature-pack> </installation>
to
<installation xmlns="urn:jboss:galleon:provisioning:2.0"> <transitive> <feature-pack location="wildfly-core@maven(org.jboss.universe:community-universe):current#6.0.0.Alpha5"/> <feature-pack location="wildfly-servlet@maven(org.jboss.universe:community-universe):current#14.0.0.Beta2-SNAPSHOT"/> </transitive> <feature-pack location="wildfly@maven(org.jboss.universe:community-universe):current#14.0.0.Beta2-SNAPSHOT"> <packages> <include name="docs.examples.configs"/> </packages> </feature-pack> </installation>
