[jbossts-issues] [JBoss JIRA] (JBTM-1754) Make project names consistent in poms

Paul Gier (JIRA) jira-events at lists.jboss.org
Thu Jun 6 13:13:54 EDT 2013

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

Paul Gier commented on JBTM-1754:

Yes, it's a bit redundant, but I think ok because it doesn't really make the name too long, and it makes it more clear that each module is part of the Narayana project vs. an external submodule or something like that.  It's also the same convention that the JBossAS/Wildfly poms use.
> Make project names consistent in poms
> -------------------------------------
>                 Key: JBTM-1754
>                 URL: https://issues.jboss.org/browse/JBTM-1754
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>            Reporter: Paul Gier
>            Assignee: Paul Gier
> The project names used in the build are not consistent which makes it difficult for someone unfamiliar with the project to debug build issues.
> Some examples are provided:
> ||Dir Name||Artifact ID||Project Name||Proposed Name||
> |/ArjunaJTA|narayana-jta-all|JBoss JTA everything|Narayana: ArjunaJTA|
> |/ArjunaJTS/narayana-jts-idlj|narayana-jts-idlj|JBossJTS packaged module with idlj stubs|Narayana: ArjunaJTS idlj|
> |/ArjunaJTS/orbportability|orbportability|JBossJTS orb portability|Narayana: ArjunaJTS orbportability|
> The project names can be changed without disrupting the way the build works, so these should be changed to match the dir and artifactId as much as possible.

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