[jbossts-issues] [JBoss JIRA] (JBTM-1774) STM artifactId name potentially ambiguous?

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Mon Sep 30 05:03:02 EDT 2013

    [ https://issues.jboss.org/browse/JBTM-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12808136#comment-12808136 ] 

Tom Jenkinson edited comment on JBTM-1774 at 9/30/13 5:02 AM:

Resolved in: https://github.com/jbosstm/narayana/commit/5844f1858ee1c2a40447c97e52fd78702397554f
      was (Author: tomjenkinson):
> STM artifactId name potentially ambiguous?
> ------------------------------------------
>                 Key: JBTM-1774
>                 URL: https://issues.jboss.org/browse/JBTM-1774
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Build System, STM
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>            Priority: Optional
>             Fix For: 5.0.0.M5
> Most modules that a user is expected to build and use (e.g. XTS, ArjunaCore, the JTA/JTS uber jars) use an aggregate nominative part of the group plus a module-centric name to differentiate them.
> The problem such that it is, can be seen cleanest in JBTM-1769 (https://github.com/jbosstm/narayana/commit/8ec2ab2375e3efb67489e7702f20c4b37ea81eb4). Here the user is suggested to build :core to build STM which is ambiguous in context with the rest of the project in particular ArjunaCore. 
> Can the artifactId be changed to stm-core? or just stm?

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

More information about the jbossts-issues mailing list