[ http://issues.apache.org/jira/browse/IO-103?page=all ]
Jochen Wiedmann updated IO-103:
-------------------------------
Attachment: (was: commons-io-resources.patch)
> commons-io cannot be deployed with Maven 2
> ------------------------------------------
>
> Key: IO-103
> URL: http://issues.apache.org/jira/browse/IO-103
> Project: Commons IO
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Jochen Wiedmann
>
> The commons-io POM contains a resource section, which specifies that the
> NOTICE.txt and LICENSE.txt files are being added to the jar files META-INF
> directory. Unfortunately, this triggers MSOURCES-6, a well known bug in the
> maven-sources-plugin, which attempts to include the base directory into the
> source jar file. The base directory includes the sources jar itself, which is
> growing while it is being included into itself, which is growing while it is
> included into itself, ...
> In other words, the maven-sources-plugin is creating a jar file endleseely.
> When deploying the commons-io with
> mvn -Prc commons-io deploy
> or
> mvn -Prelease commons-io deploy
> then the maven-sources-plugin is invoked by the commons-parent POM. In other
> words, the commons-io jar file cannot be deployed.
> The attached patch removes the resources section from the commons-parent POM:
> This can easily be done, because the commons-parent POM is already addressing
> this by invoking the antrun plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
