[
https://issues.jboss.org/browse/JBTM-1689?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1689:
-------------------------------------
I would be happy to remove: all, core, jta, jts, jts-idlj and stm from /pom.xml
[~marklittle] does use "mvn install -Pstm", but perhaps he will be happy to use:
"mvn install -pl STM -am" instead?
Leave it with me and I will raise the pull request if Mark is happy to stop using the
profile.
For completeness, this is what would be replaced:
all (as used in EAP builds) = mvn install
core = mvn install -am -pl ArjunaCore/arjunacore
jta = mvn install -am -pl ArjunaJTA/narayana-jta
jts = mvn install -am -pl ArjunaJTS/narayana-jts-jacorb
jts-idlj = mvn install -am -pl ArjunaJTS/narayana-jts-idlj -Didlj-enabled=true
stm = mvn install -am -pl stm
"jta" vs. "jts" profile seems duplicate
---------------------------------------
Key: JBTM-1689
URL:
https://issues.jboss.org/browse/JBTM-1689
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: 4.17.4
Reporter: Weinan Li
Assignee: Tom Jenkinson
Priority: Minor
"jta" vs. "jts" profile, they seem to build the same modules except
for ArjunaJTS.
As maven has some built in options for selecting which modules/directories to build,
would it be better to just use those options? Instead of defining profiles, it might look
something like "mvn install -pl common,ArjunaCore" instead of the build profile
"mvn install -Pcore"
--
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