[
https://issues.jboss.org/browse/WFBUILD-36?page=com.atlassian.jira.plugin...
]
Brian Stansberry updated WFBUILD-36:
------------------------------------
Description:
The provisioning plugin allows parameterization of a feature pack's version via
{code}${project.version}{code} but parameterizing the groupId via
{code}${project.groupId}{code} isn't supported. My guess is something like this for
groupId would do the trick:
https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning-m...
This would make it easier to use the same provisioning configs in different branches that
have different maven groupIds.
I see the TODO about the project.version thing I linked above, and I understand I'm
asking to expand a concept that the TODO indicates is suspect. So I won't be offended
if this is rejected.
was:
The provisioning plugin allows parameterization of a feature pack's version via
```${project.version}``` but parameterizing the groupId via ```${project.groupId}```
isn't supported. My guess is something like this for groupId would do the trick:
https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning-m...
This would make it easier to use the same provisioning configs in different branches that
have different maven groupIds.
I see the TODO about the project.version thing I linked above, and I understand I'm
asking to expand a concept that the TODO indicates is suspect. So I won't be offended
if this is rejected.
Support resolution of ${project.groupId} in the
server-provisioning.xml file
----------------------------------------------------------------------------
Key: WFBUILD-36
URL:
https://issues.jboss.org/browse/WFBUILD-36
Project: WildFly Build Tools
Issue Type: Enhancement
Reporter: Brian Stansberry
Assignee: Stuart Douglas
Priority: Minor
Fix For: 1.2.9.Final
The provisioning plugin allows parameterization of a feature pack's version via
{code}${project.version}{code} but parameterizing the groupId via
{code}${project.groupId}{code} isn't supported. My guess is something like this for
groupId would do the trick:
https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning-m...
This would make it easier to use the same provisioning configs in different branches that
have different maven groupIds.
I see the TODO about the project.version thing I linked above, and I understand I'm
asking to expand a concept that the TODO indicates is suspect. So I won't be offended
if this is rejected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)