You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/08/02 02:44:22 UTC

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

The following comment has been added to this issue:

     Author: Felipe Leme
    Created: Sun, 1 Aug 2004 8:43 PM
       Body:
I agree this would be an useful feature, specially when you develop components with points of extension. In these cases, you could provide test cases that would be extended by applications using your component.

Of course, we could create another project for that, but I think it would be much easier if Maven packaged these test cases in the same project.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MPJAR-34?page=comments#action_22596

---------------------------------------------------------------------
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: Sun, 1 Aug 2004 8:43 PM

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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org