You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/07/07 05:04:13 UTC

[jira] Closed: (MNG-3095) maven-plugin-testing-tools causes bad version in deployed artifacts after tests are run

     [ http://jira.codehaus.org/browse/MNG-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed MNG-3095.
--------------------------

         Assignee: Brian Fox
       Resolution: Fixed
    Fix Version/s: 2.0.8

The tool system creates a pom-test.xml file and reruns the build to create the plugin-test.jar. The problem is that this effectively overwrites the compiled class files and other metadata of the actual plugin build with the build for the test jar. I modified the test tools to create the pom-test.xml with build.outputDirectory=target/it-build-target/classes and build.directory=target/it-build-target

In this way, the products of the test build cannot interfere with the real build.

> maven-plugin-testing-tools causes bad version in deployed artifacts after tests are run
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-3095
>                 URL: http://jira.codehaus.org/browse/MNG-3095
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Shared
>    Affects Versions: 2.0.7
>            Reporter: Brian Fox
>            Assignee: Brian Fox
>             Fix For: 2.0.8
>
>
> After running tests with the plugin testing tools, the actual jar artifact contains /META-INF/maven/plugin.xml  containing the test version instead of the real version. In certain instances, this causes the plugin to fail at runtime.

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