The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 2 Aug 2004 8:32 AM
Body:
"Sometimes a few people really want/need a feature but others do not. I think it's not
possible to satisify everyone 100% of the time."
Hence maven.xml and post/pre goals, plugins...
"If you don't want the test classes in the jar then that's fine, why force others to
feel as you do?"
I'm not forcing anyone, but Maven simply can't be all configurable, it'd be a mess.
"Overall I think adding the property is the easiest quick fix to this problem. As it
currently is I'm forced to put mock objects and some of my integration junit tests in
my src/java tree. Anything is better than that."
Quick fixes are not often the best ones.
A quicker fix would be for you to postGoal the jar goal and add any test classes into
the jar....
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPJAR-34?page=comments#action_22624
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPJAR-34
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJAR-34
Summary: Add an option to include test classes in jars
Type: New Feature
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jar-plugin
Assignee: Jason van Zyl
Reporter: Michael Mattox
Created: Fri, 30 Jul 2004 5:26 AM
Updated: Mon, 2 Aug 2004 8:32 AM
Description:
I have mock objects defined in my src/test tree. Other projects then use these mock
objects for their tests. With Maven, test classes are not included in the
distribution jars. Searching the mailing list, this seems to be a common need. The
only viable solution I've seen is to move the mock objects to the src/java tree. I
don't like this at all. I'd like to propose a new property:
maven.jar.include.test.classes
it could be false by default. Setting it to true would include the test classes in
the jar. I consider test code just as important as my application code, so this
option makes a lot of sense to me. I don't see any reason not to include, but at
least adding the property would give the user the choice.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
