[
http://jira.codehaus.org/browse/MASSEMBLY-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240659#action_240659
]
Chad Lyon commented on MASSEMBLY-452:
-
Regression: This issue exists for version 2.2 of the pl
[
http://jira.codehaus.org/browse/MJAR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120498
]
Chad Lyon commented on MJAR-90:
---
Then I think creating a blank JAR is a good thing. It will cause the dependency
resolution to no
[
http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120492
]
Chad Lyon commented on MJAR-68:
---
right, but do you agree that in a multi-module project if you are skipping
tests (which includes
[
http://jira.codehaus.org/browse/MJAR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120467
]
Chad Lyon commented on MJAR-90:
---
This fix causes problems for multi-module projects. See MJAR-68
> when maven.test.Skip is set,
[
http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120466
]
Chad Lyon commented on MJAR-68:
---
clarification... to skip executing tests but still compile them the switch is
-DskipTests=true n
[
http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120463
]
Chad Lyon commented on MJAR-68:
---
The problem is actually in the resolution of dependencies. I have a
multi-module project. The