You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Joerg Schaible (JIRA)" <ji...@codehaus.org> on 2005/11/24 12:00:06 UTC

[jira] Created: (MNG-1674) configure test-jar to include only special classes of the test source

configure test-jar to include only special classes of the test source
---------------------------------------------------------------------

         Key: MNG-1674
         URL: http://jira.codehaus.org/browse/MNG-1674
     Project: Maven 2
        Type: Improvement
  Components: maven-jar-plugin  
    Reporter: Joerg Schaible
    Priority: Minor


The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-1674) configure test-jar to include only special classes of the test source

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1674?page=comments#action_52028 ] 

Brett Porter commented on MNG-1674:
-----------------------------------

added ability to link, and yes thats the related issue I was referring to.

> configure test-jar to include only special classes of the test source
> ---------------------------------------------------------------------
>
>          Key: MNG-1674
>          URL: http://jira.codehaus.org/browse/MNG-1674
>      Project: Maven 2
>         Type: Improvement
>   Components: maven-jar-plugin
>     Reporter: Joerg Schaible
>     Priority: Minor

>
>
> The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-1674) configure test-jar to include only special classes of the test source

Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1674?page=comments#action_51973 ] 

Joerg Schaible commented on MNG-1674:
-------------------------------------

Related issue: MNG-1330
(BTW: why can a user not create real JIRA links between issues ??)

> configure test-jar to include only special classes of the test source
> ---------------------------------------------------------------------
>
>          Key: MNG-1674
>          URL: http://jira.codehaus.org/browse/MNG-1674
>      Project: Maven 2
>         Type: Improvement
>   Components: maven-jar-plugin
>     Reporter: Joerg Schaible
>     Priority: Minor

>
>
> The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-1674) configure test-jar to include only special classes of the test source

Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1674?page=comments#action_51972 ] 

Joerg Schaible commented on MNG-1674:
-------------------------------------

Well, regarding the 1-source-1-artifact rule, the complete concept of the subtypes is flawed ... but they're a pragmatic solution for special cases. Normally I agree, but in this case you have that circular dependency and you cannot avoid it. The standard way seems something like (see the build section): http://svn.picocontainer.codehaus.org/java/picocontainer/trunk/tck/pom.xml?rev=2755&view=markup

With test-jar you already have 2/3 of the solution, why not complete it ?

> configure test-jar to include only special classes of the test source
> ---------------------------------------------------------------------
>
>          Key: MNG-1674
>          URL: http://jira.codehaus.org/browse/MNG-1674
>      Project: Maven 2
>         Type: Improvement
>   Components: maven-jar-plugin
>     Reporter: Joerg Schaible
>     Priority: Minor

>
>
> The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-1674) configure test-jar to include only special classes of the test source

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1674?page=comments#action_51951 ] 

Brett Porter commented on MNG-1674:
-----------------------------------

I think there is an open issue to do this WRT mock classes and maybe actually creating a mock source directory.

Other than that, I think adding features like this is a slippery slope. A lot of Maven's features work and are simple because of the 1 source directory, 1 artifact rule. Anything that starts to product multiple artifacts with a subset of a source directory might not integrate well with other features.

> configure test-jar to include only special classes of the test source
> ---------------------------------------------------------------------
>
>          Key: MNG-1674
>          URL: http://jira.codehaus.org/browse/MNG-1674
>      Project: Maven 2
>         Type: Improvement
>   Components: maven-jar-plugin
>     Reporter: Joerg Schaible
>     Priority: Minor

>
>
> The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org