[
http://jira.codehaus.org/browse/MJAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict closed MJAR-126.
------------------------------
Resolution: Not A Bug
This is not a bug, but perhaps it exposes another. After trying to reproduce
it, I managed to discover the POM mapped <testResources> to both
src/main/resources and src/test/resources. Obviously this would effect the
producing of the test jar. However, I am concerned Maven allows this
configuration. Why would it be permissible to map the main resources as a test
resource?
> Test Jar should not include src/main/* contents
> -----------------------------------------------
>
> Key: MJAR-126
> URL: http://jira.codehaus.org/browse/MJAR-126
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Paul Benedict
> Attachments: MJAR-126.zip
>
>
> My project creates a jar and a test-jar. The first one is obviously the main
> program, but the second one contains test harnesses for consumption with
> other projects. What is annoying is how the test-jar gets all the
> src/main/resources contents. I don't understand (or see why or how) it should
> receive anything from src/main/. I actually think current behavior is
> incorrect; it should only get the contents from src/test/.
> This is especially true since src/main/resources contains my Hibernate
> mappings. To prevent duplicate mappings at load time (when both jars are
> used), I have to exclude every resource in the test-jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
