You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Hoeve (JIRA)" <ji...@codehaus.org> on 2006/12/04 15:42:41 UTC
[jira] Created: (SCM-259) Running scm:changelog after scm:update
should be made configurable
Running scm:changelog after scm:update should be made configurable
------------------------------------------------------------------
Key: SCM-259
URL: http://jira.codehaus.org/browse/SCM-259
Project: Maven SCM
Issue Type: New Feature
Components: maven-scm-api
Reporter: Jan Hoeve
Priority: Minor
I do have a environment with cruisecontrol as a buildserver and clearcase as SCM provider.
One entire build loop takes half an hour to complete. This is because the scm:update command fires an changelog command to get the changed files.
This changelog process takes about 20 minutes to complete. My clearcase view has some 8500 files in it.
(note: changelog is fired without the startDate, bad for performance on clearcase).
It would be very nice if there was an option i could pass to mvn scm:update which skips the changelog process.
--
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: (SCM-259) Running scm:changelog after scm:update
should be made configurable
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89753 ]
Emmanuel Venisse commented on SCM-259:
--------------------------------------
you can use the system property maven.scm.update.skipChangelog=true
> Running scm:changelog after scm:update should be made configurable
> ------------------------------------------------------------------
>
> Key: SCM-259
> URL: http://jira.codehaus.org/browse/SCM-259
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Jan Hoeve
> Assigned To: Emmanuel Venisse
> Priority: Minor
> Fix For: 1.0
>
>
> I do have a environment with cruisecontrol as a buildserver and clearcase as SCM provider.
> One entire build loop takes half an hour to complete. This is because the scm:update command fires an changelog command to get the changed files.
> This changelog process takes about 20 minutes to complete. My clearcase view has some 8500 files in it.
> (note: changelog is fired without the startDate, bad for performance on clearcase).
> It would be very nice if there was an option i could pass to mvn scm:update which skips the changelog process.
--
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: (SCM-259) Running scm:changelog after scm:update
should be made configurable
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed SCM-259.
--------------------------------
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: 1.0
> Running scm:changelog after scm:update should be made configurable
> ------------------------------------------------------------------
>
> Key: SCM-259
> URL: http://jira.codehaus.org/browse/SCM-259
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Jan Hoeve
> Assigned To: Emmanuel Venisse
> Priority: Minor
> Fix For: 1.0
>
>
> I do have a environment with cruisecontrol as a buildserver and clearcase as SCM provider.
> One entire build loop takes half an hour to complete. This is because the scm:update command fires an changelog command to get the changed files.
> This changelog process takes about 20 minutes to complete. My clearcase view has some 8500 files in it.
> (note: changelog is fired without the startDate, bad for performance on clearcase).
> It would be very nice if there was an option i could pass to mvn scm:update which skips the changelog process.
--
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: (SCM-259) Running scm:changelog after scm:update
should be made configurable
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse updated SCM-259:
---------------------------------
Comment: was deleted
> Running scm:changelog after scm:update should be made configurable
> ------------------------------------------------------------------
>
> Key: SCM-259
> URL: http://jira.codehaus.org/browse/SCM-259
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Jan Hoeve
> Assigned To: Emmanuel Venisse
> Priority: Minor
> Fix For: 1.0
>
>
> I do have a environment with cruisecontrol as a buildserver and clearcase as SCM provider.
> One entire build loop takes half an hour to complete. This is because the scm:update command fires an changelog command to get the changed files.
> This changelog process takes about 20 minutes to complete. My clearcase view has some 8500 files in it.
> (note: changelog is fired without the startDate, bad for performance on clearcase).
> It would be very nice if there was an option i could pass to mvn scm:update which skips the changelog process.
--
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: (SCM-259) Running scm:changelog after scm:update
should be made configurable
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89908 ]
Emmanuel Venisse commented on SCM-259:
--------------------------------------
I added a new parameter in update mojo
> Running scm:changelog after scm:update should be made configurable
> ------------------------------------------------------------------
>
> Key: SCM-259
> URL: http://jira.codehaus.org/browse/SCM-259
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Jan Hoeve
> Assigned To: Emmanuel Venisse
> Priority: Minor
> Fix For: 1.0
>
>
> I do have a environment with cruisecontrol as a buildserver and clearcase as SCM provider.
> One entire build loop takes half an hour to complete. This is because the scm:update command fires an changelog command to get the changed files.
> This changelog process takes about 20 minutes to complete. My clearcase view has some 8500 files in it.
> (note: changelog is fired without the startDate, bad for performance on clearcase).
> It would be very nice if there was an option i could pass to mvn scm:update which skips the changelog process.
--
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