[
https://issues.jboss.org/browse/WFBUILD-34?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFBUILD-34:
------------------------------------
We _could_ enhance version 1.7 of the schema to expect g:a:t:c:v if that's the Maven
standard. Then the build tools could examine the namespace to decide what format to use.
But we should only use the format that is standardized in Maven if possible.
Use the same groupId:artifactId[:type[:classifier[:version]]] format
everywhere
-------------------------------------------------------------------------------
Key: WFBUILD-34
URL:
https://issues.jboss.org/browse/WFBUILD-34
Project: WildFly Build Tools
Issue Type: Enhancement
Reporter: Peter Palaga
Assignee: Stuart Douglas
Fix For: 1.2.8.Final
This both a usability issue and a feature request.
On the usability side, the artifact formats in module.xml files vs. in
feature-pack-build.xml files are not the same:
* `{{groupId:artifactId\[:version\[:classifier]]}}` in module.xml files
* `{{groupId:artifactId\[:type\[:classifier]]}}` in feature-pack-build.xml files
The missing feature is the impossibility to define type/extension in module.xml files and
the impossibility to had code version in feature-pack-build.xml files
The current proposal is to use the same
{{groupId:artifactId\[:type\[:classifier\[:version]]]}} format in both kinds of files.
The proposal is backwards incompatible for module.xml files. But given that the support
for hardcoded versions in module.xml files was added just 11 days ago, this will probably
impact just a few users.
I am not sure what artifact format is used by JBoss modules. Maybe
`{{groupId:artifactId\[:version\[:classifier]]}}` is taken from there?
WDYT [~swd847]?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)