[
https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin....
]
Weinan Li commented on JBTM-1598:
---------------------------------
Hi Tom, because of EAP6 current policy, all the dependency management sections will be
removed by VMan automatically (a EAP prod tool), so we have to refer ${project.version}
explicitly in the poms. I have done that in EAP6 version, unfortunately I've tried but
the patch could not be easily reused on upstream code. I believe we could first have a
profile for EAP6, and then just add these version tags for the necessary components,
wdyt?
version tags missed for all the sub-components
----------------------------------------------
Key: JBTM-1598
URL:
https://issues.jboss.org/browse/JBTM-1598
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Weinan Li
Assignee: Tom Jenkinson
Hi Tom, the problem I've found is that all the dependencies of its own components are
lack of version section. For example:
{code}
<dependencies>
<dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>common</artifactId>
</dependency>
</dependencies>
{code}
Should be:
{code}
<dependencies>
<dependency>
<groupId>org.jboss.jbossts</groupId>
<artifactId>common</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
{code}
Could you please help to add these tags? Thanks!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira