You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Jochen Wiedmann (JIRA)" <ji...@apache.org> on 2006/12/06 09:43:20 UTC
[jira] Created: (IO-103) commons-io cannot be deployed with Maven 2
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
Attachments: commons-io-resources.patch
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (IO-103) commons-io cannot be deployed with Maven 2
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (IO-103) commons-io cannot be deployed with Maven 2
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=all ]
Henri Yandell updated IO-103:
-----------------------------
Fix Version/s: 1.3
> 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
> Fix For: 1.3
>
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (IO-103) commons-io cannot be deployed with Maven 2
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=all ]
Jochen Wiedmann updated IO-103:
-------------------------------
Attachment: 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
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (IO-103) commons-io cannot be deployed with Maven
2
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=comments#action_12455930 ]
Henri Yandell commented on IO-103:
----------------------------------
svn ci -m "Removing the NOTICE.txt and LICENSE.txt packing inside the META-INF. Commons-parent takes care of this. Patch supplied by Jochen in #IO-103" pom.xml
Sending pom.xml
Transmitting file data .
Committed revision 482976.
---
Will let Jochen reply on the above before resolving.
> 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
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (IO-103) commons-io cannot be deployed with Maven 2
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=all ]
Jochen Wiedmann updated IO-103:
-------------------------------
Attachment: commons-io-resources.patch
Fixed 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
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (IO-103) commons-io cannot be deployed with Maven
2
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=comments#action_12455938 ]
Jochen Wiedmann commented on IO-103:
------------------------------------
I have checked beanutils and cli. Both do. Fileupload doesn't, but that's simply because I am aware of the problem. Most likely the others do as well.
> 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
> Fix For: 1.3
>
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Resolved: (IO-103) commons-io cannot be deployed with Maven
2
Posted by "Stephen Colebourne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=all ]
Stephen Colebourne resolved IO-103.
-----------------------------------
Resolution: Fixed
Assignee: Henri Yandell
I don't use Maven2, but this change appears to have been committed.
> 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
> Assigned To: Henri Yandell
> Fix For: 1.3
>
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Commented: (IO-103) commons-io cannot be deployed with Maven
2
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/IO-103?page=comments#action_12455929 ]
Henri Yandell commented on IO-103:
----------------------------------
Looks like beanutils, cli, dbutils, digester, fileupload, lang, logging and scxml all have references to NOTICE.txt (and presumably LICENSE.txt). If the parent is doing it, sounds like they all could go. Sound plausible?
> 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
> Attachments: commons-io-resources.patch
>
>
> 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org