[
https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1754:
-------------------------------------
Hi Paul, is the "Narayana: " prefix implied and therefore a little redundant (I
realise I added the redundancy myself with JBossJTS, so just trying to get your opinion
here)? if not the table looks good to me - thanks!
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