You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Xavier Dury (Created) (JIRA)" <ji...@apache.org> on 2011/11/25 10:44:40 UTC
[jira] [Created] (VFS-395) VFS2 should declare maven-scm-*
dependencies as optional in pom
VFS2 should declare maven-scm-* dependencies as optional in pom
---------------------------------------------------------------
Key: VFS-395
URL: https://issues.apache.org/jira/browse/VFS-395
Project: Commons VFS
Issue Type: Wish
Affects Versions: 2.0
Reporter: Xavier Dury
VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VFS-395) [POM] Declare maven-scm-* dependencies
as optional.
Posted by "Gary D. Gregory (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory updated VFS-395:
--------------------------------
Fix Version/s: 2.1
Summary: [POM] Declare maven-scm-* dependencies as optional. (was: VFS2 should declare maven-scm-* dependencies as optional in pom)
> [POM] Declare maven-scm-* dependencies as optional.
> ---------------------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Xavier Dury
> Fix For: 2.1
>
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VFS-395) VFS2 should declare maven-scm-*
dependencies as optional in pom
Posted by "Karsten Sperling (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257940#comment-13257940 ]
Karsten Sperling commented on VFS-395:
--------------------------------------
If additional wagon / SCM provider dependencies are necessary, they can be defined on the <plugin> element for the release plugin. Having them as project dependencies is extremely broken.
> VFS2 should declare maven-scm-* dependencies as optional in pom
> ---------------------------------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Xavier Dury
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (VFS-395) [POM] Declare maven-scm-* dependencies
as optional.
Posted by "Gary D. Gregory (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory resolved VFS-395.
---------------------------------
Resolution: Fixed
Removed the offeding plugins.
Committed revision 1328366.
> [POM] Declare maven-scm-* dependencies as optional.
> ---------------------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Xavier Dury
> Fix For: 2.1
>
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VFS-395) VFS2 should declare maven-scm-*
dependencies as optional in pom
Posted by "Joerg Schaible (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joerg Schaible updated VFS-395:
-------------------------------
Issue Type: Bug (was: Wish)
> VFS2 should declare maven-scm-* dependencies as optional in pom
> ---------------------------------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Xavier Dury
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VFS-395) VFS2 should declare maven-scm-*
dependencies as optional in pom
Posted by "Joerg Schaible (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185548#comment-13185548 ]
Joerg Schaible commented on VFS-395:
------------------------------------
These artifacts may not be declared at dependencies at all, because it's simply wrong. If they are needed for the release plugin, they must be declared as extensions.
> VFS2 should declare maven-scm-* dependencies as optional in pom
> ---------------------------------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Wish
> Affects Versions: 2.0
> Reporter: Xavier Dury
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VFS-395) [POM] Remove maven-scm-* dependencies.
Posted by "Gary D. Gregory (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory updated VFS-395:
--------------------------------
Summary: [POM] Remove maven-scm-* dependencies. (was: [POM] Declare maven-scm-* dependencies as optional.)
> [POM] Remove maven-scm-* dependencies.
> --------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Xavier Dury
> Fix For: 2.1
>
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VFS-395) VFS2 should declare maven-scm-*
dependencies as optional in pom
Posted by "Ralph Goers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186258#comment-13186258 ]
Ralph Goers commented on VFS-395:
---------------------------------
These are almost certainly not required. I'm pretty sure they were added by accident when I was trying to figure out how to generated the release notes from changes.xml during execution of the release plugin. I finally gave up as it required changes to the Maven changes plugin to make its API available.
Interestingly, the commit where these were added is marked as a rollback of the maven release plugin.
These two should be removed.
> VFS2 should declare maven-scm-* dependencies as optional in pom
> ---------------------------------------------------------------
>
> Key: VFS-395
> URL: https://issues.apache.org/jira/browse/VFS-395
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Xavier Dury
>
> VFS2 includes weird dependencies: maven-scm-api, maven-scm-provider-svnexe.
> See http://commons.apache.org/vfs/commons-vfs2/dependencies.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira