[ https://issues.jboss.org/browse/WFBUILD-4?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFBUILD-4: --------------------------------------- Here is an idea to support multiple versions of same artefacts: {code:xml} <?xml version="1.0" ?> <feature-pack xmlns="urn:wildfly:feature-pack:1.0"> <dependencies> <artifact name="org.wildfly:kickass-feature-pack" /> </dependencies> <artifact-resolver> <maven-artifact name="io.undertow:undertow-core:1.x" groupId="io.undertow" artifactId="undertow-core" version="1.1.0.Beta7"/> <maven-artifact name="io.undertow:undertow-core:2.x" groupId="io.undertow" artifactId="undertow-core" version="2.0.0.Alpha1"/> <url-artifact name="org.jboss.modules:jboss-modules" url="http://blablabla/my-jboss-modules.jar"/> <url-artifact name="org.wildfly:kickass-feature-pack" url="http://wildfly.org/feature-packs/kickass.zip"/> </artifact-resolver> <copy-artifacts> <copy-artifact artifact="org.jboss.modules:jboss-modules" to-location="jboss-modules.jar"/> </copy-artifacts> </feature-pack> {code} This is actually a small change compared to what we have now internally for feature packs, simply expose to wildfly-feature-pack.xml, the artifact reference name that is in module.xml (property name), other elements of the feature-pack xml such as the copy-artifact, or the ones computed from maven dependencies that are used as keys in the maven artifact resolver. The maven artifact version becomes just one more id, and we can even introduce - later - different type of artifacts, such as the url-artifact above. What do you think? -- This message was sent by Atlassian JIRA (v6.3.1#6329)