You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2008/04/27 14:26:46 UTC
[jira] Moved: (MPLUGINTESTING-4) maven-plugin-testing-tools causes
bad version in deployed artifacts after tests are run
[ http://jira.codehaus.org/browse/MPLUGINTESTING-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton moved MNG-3095 to MPLUGINTESTING-4:
---------------------------------------------------
Affects Version/s: (was: 2.0.7)
Fix Version/s: (was: 2.0.8)
1.1
Component/s: (was: Shared)
plugin-testing-tools
Key: MPLUGINTESTING-4 (was: MNG-3095)
Project: Maven 2.x Plugin Testing (was: Maven 2)
> maven-plugin-testing-tools causes bad version in deployed artifacts after tests are run
> ---------------------------------------------------------------------------------------
>
> Key: MPLUGINTESTING-4
> URL: http://jira.codehaus.org/browse/MPLUGINTESTING-4
> Project: Maven 2.x Plugin Testing
> Issue Type: Bug
> Components: plugin-testing-tools
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.1
>
>
> 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