You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/04/05 20:25:48 UTC

[jira] Closed: (MPJAR-34) Add an option to include test classes in jars

     [ http://jira.codehaus.org/browse/MPJAR-34?page=all ]
     
Lukas Theussl closed MPJAR-34:
------------------------------

      Assign To: Lukas Theussl  (was: Jason van Zyl)
     Resolution: Won't Fix
    Fix Version: 1.8

It's not going to be fixed in m1. I don't know about m2, you might file a new feature request and refer back to this issue.

> Add an option to include test classes in jars
> ---------------------------------------------
>
>          Key: MPJAR-34
>          URL: http://jira.codehaus.org/browse/MPJAR-34
>      Project: maven-jar-plugin
>         Type: New Feature

>     Reporter: Michael Mattox
>     Assignee: Lukas Theussl
>     Priority: Minor
>      Fix For: 1.8

>
>
> 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.

-- 
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