You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexander Betaev (JIRA)" <ji...@codehaus.org> on 2011/08/26 08:57:32 UTC
[jira] Created: (MRELEASE-707) release plugin does not use neither
${project.scm.connection} nor ${project.scm.developerConnection}
release plugin does not use neither ${project.scm.connection} nor ${project.scm.developerConnection}
----------------------------------------------------------------------------------------------------
Key: MRELEASE-707
URL: https://jira.codehaus.org/browse/MRELEASE-707
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: prepare
Affects Versions: 2.2.1
Environment: ArchLinux
Maven 3.0.3
Mercurial 1.9.1
Reporter: Alexander Betaev
Use case: I don't want to include <scm/> section in all my POM's since I want to perform releases only using CI software. It seems for me to be more useful configuration for distributed SCM's than using release plugins locally.
So I am providing '-Dproject.scm.connection=scm:hg:file://${basedir}/../' and '-Dproject.scm.developerConnection=scm:hg:file://${basedir}/../' to Maven's JVM. But it does not affect anything in maven-release-plugin. Also I did not find any property which I should use instead of project.scm.connection.
The error message I receive looks like I forgot to configure maven-scm-plugin:
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project parent: Missing required setting: scm connection or developerConnection must be specified. -> [Help 1]
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-707) release plugin does not use
neither ${project.scm.connection} nor ${project.scm.developerConnection}
Posted by "Alexander Betaev (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277454#comment-277454 ]
Alexander Betaev commented on MRELEASE-707:
-------------------------------------------
I have created a bug regarding all release process with distributed SCM with my patch: http://jira.codehaus.org/browse/MRELEASE-709
> release plugin does not use neither ${project.scm.connection} nor ${project.scm.developerConnection}
> ----------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-707
> URL: https://jira.codehaus.org/browse/MRELEASE-707
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.2.1
> Environment: ArchLinux
> Maven 3.0.3
> Mercurial 1.9.1
> Reporter: Alexander Betaev
>
> Use case: I don't want to include <scm/> section in all my POM's since I want to perform releases only using CI software. It seems for me to be more useful configuration for distributed SCM's than using release plugins locally.
> So I am providing '-Dproject.scm.connection=scm:hg:file://${basedir}/../' and '-Dproject.scm.developerConnection=scm:hg:file://${basedir}/../' to Maven's JVM. But it does not affect anything in maven-release-plugin. Also I did not find any property which I should use instead of project.scm.connection.
> The error message I receive looks like I forgot to configure maven-scm-plugin:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project parent: Missing required setting: scm connection or developerConnection must be specified. -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-707) release plugin does not use
neither ${project.scm.connection} nor ${project.scm.developerConnection}
Posted by "Timothy Soehnlin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278885#comment-278885 ]
Timothy Soehnlin commented on MRELEASE-707:
-------------------------------------------
I am currently running into this issue as well. I really want to centralize the SCM access to our CI environment, and not have the developers accidentally committing/updating from the maven command line.
> release plugin does not use neither ${project.scm.connection} nor ${project.scm.developerConnection}
> ----------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-707
> URL: https://jira.codehaus.org/browse/MRELEASE-707
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.2.1
> Environment: ArchLinux
> Maven 3.0.3
> Mercurial 1.9.1
> Reporter: Alexander Betaev
>
> Use case: I don't want to include <scm/> section in all my POM's since I want to perform releases only using CI software. It seems for me to be more useful configuration for distributed SCM's than using release plugins locally.
> So I am providing '-Dproject.scm.connection=scm:hg:file://${basedir}/../' and '-Dproject.scm.developerConnection=scm:hg:file://${basedir}/../' to Maven's JVM. But it does not affect anything in maven-release-plugin. Also I did not find any property which I should use instead of project.scm.connection.
> The error message I receive looks like I forgot to configure maven-scm-plugin:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project parent: Missing required setting: scm connection or developerConnection must be specified. -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-707) release plugin does not use
neither ${project.scm.connection} nor ${project.scm.developerConnection}
Posted by "Alexander Betaev (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277098#comment-277098 ]
Alexander Betaev commented on MRELEASE-707:
-------------------------------------------
Forgot to mention that my project's structure is
{noformat}
\root
\parent
\pom.xml
\module1
\pom.xml
\module2
\pom.xml
...
\moduleN
\pom.xml
{noformat}
> release plugin does not use neither ${project.scm.connection} nor ${project.scm.developerConnection}
> ----------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-707
> URL: https://jira.codehaus.org/browse/MRELEASE-707
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.2.1
> Environment: ArchLinux
> Maven 3.0.3
> Mercurial 1.9.1
> Reporter: Alexander Betaev
>
> Use case: I don't want to include <scm/> section in all my POM's since I want to perform releases only using CI software. It seems for me to be more useful configuration for distributed SCM's than using release plugins locally.
> So I am providing '-Dproject.scm.connection=scm:hg:file://${basedir}/../' and '-Dproject.scm.developerConnection=scm:hg:file://${basedir}/../' to Maven's JVM. But it does not affect anything in maven-release-plugin. Also I did not find any property which I should use instead of project.scm.connection.
> The error message I receive looks like I forgot to configure maven-scm-plugin:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project parent: Missing required setting: scm connection or developerConnection must be specified. -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira