You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mykel Alvis (JIRA)" <ji...@codehaus.org> on 2007/02/07 17:28:44 UTC
[jira] Created: (MRELEASE-196) Release plugin needs a way to return
the SCM urls to previously defined version after release (based on
properties)
Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
-------------------------------------------------------------------------------------------------------------------
Key: MRELEASE-196
URL: http://jira.codehaus.org/browse/MRELEASE-196
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Environment: Any pom where SCM information is based on properties
Reporter: Mykel Alvis
My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
For example,
<scm>
<connection>scm:svn:${sird.scm.url.ro}</connection>
<developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
<url>${sird.scm.url.view}</url>
</scm>
is based on
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
<!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
<!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
<releaseTag>blah</releaseTag>
with some property called releaseTag set by the release plugin into my property sets
and then having the release plugin just change the scm url to
<scm>
...
<developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
...
</scm>
I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
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] (MRELEASE-196) Release plugin needs a way to return the SCM
urls to previously defined version after release (based on properties)
Posted by "Mykel Alvis (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mykel Alvis closed MRELEASE-196.
--------------------------------
Resolution: Won't Fix
Nope. Sorry. My bad.
I didn't mean that it needed re-opening.
This issue is a losing proposition and after 5 years, doesn't appear to solve the problem I originally wanted it to. Re-close.
> Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-196
> URL: https://jira.codehaus.org/browse/MRELEASE-196
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Environment: Any pom where SCM information is based on properties
> Reporter: Mykel Alvis
> Assignee: Robert Scholte
>
> My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
> When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
> However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
> For example,
> {code:xml}
> <scm>
> <connection>scm:svn:${sird.scm.url.ro}</connection>
> <developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
> <url>${sird.scm.url.view}</url>
> </scm>
> {code}
> is based on
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
> <!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
> {code}
> What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
> <releaseTag>blah</releaseTag>
> {code}
> with some property called releaseTag set by the release plugin into my property sets
> and then having the release plugin just change the scm url to
> {code:xml}
> <scm>
> ...
> <developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
> ...
> </scm>
> {code}
> I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-196) Release plugin needs a way to return the SCM
urls to previously defined version after release (based on properties)
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-196:
------------------------------------
Description:
My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
For example,
{code:xml}
<scm>
<connection>scm:svn:${sird.scm.url.ro}</connection>
<developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
<url>${sird.scm.url.view}</url>
</scm>
{code}
is based on
{code:xml}
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
<!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
<!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
{code}
What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
{code:xml}
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
<releaseTag>blah</releaseTag>
{code}
with some property called releaseTag set by the release plugin into my property sets
and then having the release plugin just change the scm url to
{code:xml}
<scm>
...
<developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
...
</scm>
{code}
I know at least a couple of other places that manage a large number of artifacts like to do things like this.
was:
My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
For example,
<scm>
<connection>scm:svn:${sird.scm.url.ro}</connection>
<developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
<url>${sird.scm.url.view}</url>
</scm>
is based on
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
<!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
<!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
<!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
<sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
<releaseTag>blah</releaseTag>
with some property called releaseTag set by the release plugin into my property sets
and then having the release plugin just change the scm url to
<scm>
...
<developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
...
</scm>
I know at least a couple of other places that manage a large number of artifacts like to do things like this.
> Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-196
> URL: https://jira.codehaus.org/browse/MRELEASE-196
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Environment: Any pom where SCM information is based on properties
> Reporter: Mykel Alvis
>
> My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
> When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
> However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
> For example,
> {code:xml}
> <scm>
> <connection>scm:svn:${sird.scm.url.ro}</connection>
> <developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
> <url>${sird.scm.url.view}</url>
> </scm>
> {code}
> is based on
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
> <!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
> {code}
> What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
> <releaseTag>blah</releaseTag>
> {code}
> with some property called releaseTag set by the release plugin into my property sets
> and then having the release plugin just change the scm url to
> {code:xml}
> <scm>
> ...
> <developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
> ...
> </scm>
> {code}
> I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-196) Release plugin needs a way to return the SCM
urls to previously defined version after release (based on properties)
Posted by "Mykel Alvis (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297876#comment-297876 ]
Mykel Alvis commented on MRELEASE-196:
--------------------------------------
The release.properties file doesn't do anything remotely close to what I'm suggesting, but I can't figure out a way to reverse inserting values into the POM.
> Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-196
> URL: https://jira.codehaus.org/browse/MRELEASE-196
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Environment: Any pom where SCM information is based on properties
> Reporter: Mykel Alvis
> Assignee: Robert Scholte
>
> My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
> When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
> However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
> For example,
> {code:xml}
> <scm>
> <connection>scm:svn:${sird.scm.url.ro}</connection>
> <developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
> <url>${sird.scm.url.view}</url>
> </scm>
> {code}
> is based on
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
> <!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
> {code}
> What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
> <releaseTag>blah</releaseTag>
> {code}
> with some property called releaseTag set by the release plugin into my property sets
> and then having the release plugin just change the scm url to
> {code:xml}
> <scm>
> ...
> <developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
> ...
> </scm>
> {code}
> I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-196) Release plugin needs a way to return the SCM
urls to previously defined version after release (based on properties)
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte reopened MRELEASE-196:
-------------------------------------
I'll reopen this issue to give you another chance to explain what you want. I'd prefer if you could attach 3 pom.xml files: pom.xml (the current one), pom.xml.tag (the released one) and pom.xml.next (for the next dev-cycle) to show me what you want.
Keep in mind that we won't add new properties to the pom.
> Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-196
> URL: https://jira.codehaus.org/browse/MRELEASE-196
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Environment: Any pom where SCM information is based on properties
> Reporter: Mykel Alvis
> Assignee: Robert Scholte
>
> My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
> When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
> However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
> For example,
> {code:xml}
> <scm>
> <connection>scm:svn:${sird.scm.url.ro}</connection>
> <developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
> <url>${sird.scm.url.view}</url>
> </scm>
> {code}
> is based on
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
> <!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
> {code}
> What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
> <releaseTag>blah</releaseTag>
> {code}
> with some property called releaseTag set by the release plugin into my property sets
> and then having the release plugin just change the scm url to
> {code:xml}
> <scm>
> ...
> <developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
> ...
> </scm>
> {code}
> I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-196) Release plugin needs a way to return
the SCM urls to previously defined version after release (based on
properties)
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-196:
-------------------------------------
Component/s: scm
> Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-196
> URL: http://jira.codehaus.org/browse/MRELEASE-196
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Environment: Any pom where SCM information is based on properties
> Reporter: Mykel Alvis
>
> My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
> When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
> However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
> For example,
> <scm>
> <connection>scm:svn:${sird.scm.url.ro}</connection>
> <developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
> <url>${sird.scm.url.view}</url>
> </scm>
> is based on
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
> <!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
> What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
> <releaseTag>blah</releaseTag>
> with some property called releaseTag set by the release plugin into my property sets
> and then having the release plugin just change the scm url to
> <scm>
> ...
> <developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
> ...
> </scm>
> I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
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] (MRELEASE-196) Release plugin needs a way to return the SCM
urls to previously defined version after release (based on properties)
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-196.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
The {{release:prepare}} generates a file called {{release.properties}}, which contains this kind of information.
> Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-196
> URL: https://jira.codehaus.org/browse/MRELEASE-196
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Environment: Any pom where SCM information is based on properties
> Reporter: Mykel Alvis
> Assignee: Robert Scholte
>
> My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and the artifactId
> When the release plugin runs, it overrides these properties with the expanded SCM information, as expected.
> However, when releasing a parent pom, this isn't an optimal situation. (My) parent poms need to be released by altering the property sets, not changing the SCM urls.
> For example,
> {code:xml}
> <scm>
> <connection>scm:svn:${sird.scm.url.ro}</connection>
> <developerConnection>scm:svn:${sird.scm.url.dev}</developerConnection>
> <url>${sird.scm.url.view}</url>
> </scm>
> {code}
> is based on
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the readonly url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.ro>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.ro>
> <!-- This is the view (eg fisheye) url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.view>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.view>
> {code}
> What I'd like is to be able to change the sird.scm.url.dev (for instance) to some OTHER value, such as substituting a different url like
> {code:xml}
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.dev>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/trunk</sird.scm.url.dev>
> <!-- This is the developer url for this project, made from the scm host, the namespace, and the artifact id -->
> <sird.scm.url.released>http://${sird.scm.host}/svnrepos/${sird.object.namespace}/${artifactId}/tags/${releaseTag}</sird.scm.url.dev>
> <releaseTag>blah</releaseTag>
> {code}
> with some property called releaseTag set by the release plugin into my property sets
> and then having the release plugin just change the scm url to
> {code:xml}
> <scm>
> ...
> <developerConnection>scm:svn:${sird.scm.url.released}</developerConnection>
> ...
> </scm>
> {code}
> I know at least a couple of other places that manage a large number of artifacts like to do things like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira