You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "isabel drost (JIRA)" <ji...@codehaus.org> on 2010/06/02 17:10:12 UTC
[jira] Created: (DOXIA-394) Transitive dependency to old
commons-logging through HttpClient causes problems
Transitive dependency to old commons-logging through HttpClient causes problems
-------------------------------------------------------------------------------
Key: DOXIA-394
URL: http://jira.codehaus.org/browse/DOXIA-394
Project: Maven Doxia
Issue Type: Bug
Components: Maven plugin
Affects Versions: 1.1.3
Reporter: isabel drost
The issue (and resulting trouble) is described in more detail over in the MSITE issue tracker: http://jira.codehaus.org/browse/MSITE-459
Excluding the dependency entirely solved the problem for me. See attached diff for the changes I made.
--
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
[jira] Commented: (DOXIA-394) Transitive dependency to old
commons-logging through HttpClient causes problems
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224055#action_224055 ]
Lukas Theussl commented on DOXIA-394:
-------------------------------------
This patch makes the fml module test fail.
> Transitive dependency to old commons-logging through HttpClient causes problems
> -------------------------------------------------------------------------------
>
> Key: DOXIA-394
> URL: http://jira.codehaus.org/browse/DOXIA-394
> Project: Maven Doxia
> Issue Type: Bug
> Components: Maven plugin
> Affects Versions: 1.1.3
> Reporter: isabel drost
> Attachments: DOXIA-394.diff
>
>
> The issue (and resulting trouble) is described in more detail over in the MSITE issue tracker: http://jira.codehaus.org/browse/MSITE-459
> Excluding the dependency entirely solved the problem for me. See attached diff for the changes I made.
--
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
[jira] Commented: (DOXIA-394) Transitive dependency to old
commons-logging through HttpClient causes problems
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238198#action_238198 ]
Dennis Lundberg commented on DOXIA-394:
---------------------------------------
Isabel, could you please try my proposed fix described at http://jira.codehaus.org/browse/MSITE-459?focusedCommentId=235286&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_235286
> Transitive dependency to old commons-logging through HttpClient causes problems
> -------------------------------------------------------------------------------
>
> Key: DOXIA-394
> URL: http://jira.codehaus.org/browse/DOXIA-394
> Project: Maven Doxia
> Issue Type: Bug
> Components: Maven plugin
> Affects Versions: 1.1.3
> Reporter: isabel drost
> Attachments: DOXIA-394.diff
>
>
> The issue (and resulting trouble) is described in more detail over in the MSITE issue tracker: http://jira.codehaus.org/browse/MSITE-459
> Excluding the dependency entirely solved the problem for me. See attached diff for the changes I made.
--
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
[jira] Closed: (DOXIA-394) Transitive dependency to old
commons-logging through HttpClient causes problems
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed DOXIA-394.
---------------------------------
Resolution: Duplicate
> Transitive dependency to old commons-logging through HttpClient causes problems
> -------------------------------------------------------------------------------
>
> Key: DOXIA-394
> URL: http://jira.codehaus.org/browse/DOXIA-394
> Project: Maven Doxia
> Issue Type: Bug
> Components: Maven plugin
> Affects Versions: 1.1.3
> Reporter: isabel drost
> Attachments: DOXIA-394.diff
>
>
> The issue (and resulting trouble) is described in more detail over in the MSITE issue tracker: http://jira.codehaus.org/browse/MSITE-459
> Excluding the dependency entirely solved the problem for me. See attached diff for the changes I made.
--
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
[jira] Updated: (DOXIA-394) Transitive dependency to old
commons-logging through HttpClient causes problems
Posted by "isabel drost (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
isabel drost updated DOXIA-394:
-------------------------------
Attachment: DOXIA-394.diff
The changes that fixed the mvn site:deploy goal for me.
> Transitive dependency to old commons-logging through HttpClient causes problems
> -------------------------------------------------------------------------------
>
> Key: DOXIA-394
> URL: http://jira.codehaus.org/browse/DOXIA-394
> Project: Maven Doxia
> Issue Type: Bug
> Components: Maven plugin
> Affects Versions: 1.1.3
> Reporter: isabel drost
> Attachments: DOXIA-394.diff
>
>
> The issue (and resulting trouble) is described in more detail over in the MSITE issue tracker: http://jira.codehaus.org/browse/MSITE-459
> Excluding the dependency entirely solved the problem for me. See attached diff for the changes I made.
--
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