You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/16 17:08:01 UTC
[jira] Created: (MPSCM-11) Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPSCM-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPSCM-11
Summary: Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: maven-scm-plugin
Assignee: Brett Porter
Reporter: Dulon Zaman
Created: Wed, 16 Jun 2004 11:07 AM
Updated: Wed, 16 Jun 2004 11:07 AM
Environment: - Windows 2000
- Maven RC3
- CVS client (version 1.12.7 - downloaded from http://www.cvshome.org/dev/codewindow.html)
Description:
Problem:
The problem is that sometimes the scm:prepare-release goal would commit blank project.xml into cvs.
Suggested Cause:
This looks like its due to the fact that the line <r:release-version version="${version_name}" tag="${tag_name}" /> has not finished updating the project.xml, before the project.xml is committed to cvs in the next line. However, our team has not come across any half-completed project.xml just blank or perfectly updated ones.
Suggested Solution:
Add a "sleep" goal inbetween the r:release line and the cvs commit line in the scm:prepare-release goal.
Extra Information:
Here is a maven.xml extract that I hope will you will be able to use to demonstrate the bug and the solution. You should notice in the CVS history of the project.xml you choose to test with that some versions of the checked-in project.xml was blank when running the test goal without the sleep inbetween.
<goal name="release:test-fault"
prereqs="scm:validate">
<echo>Release Test - fault</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<ant:cvs command="commit -m '[release:test-faulty] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
<goal name="release:test-fix"
prereqs="scm:validate">
<echo>Release Test - fix</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<echo>Sleeping for 5 secs to allow the Project.xml to be updated</echo>
<ant:sleep seconds="5"/>
<echo>Now doing the commit</echo>
<ant:cvs command="commit -m '[release:test-fix] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPSCM-11) Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Paul Spencer
Created: Fri, 6 Aug 2004 4:43 PM
Body:
This sounds very simular to MPSCM-24. I checked and I noticed the output file is not closed, or flushed, in the release plugin.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPSCM-11?page=comments#action_22824
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPSCM-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPSCM-11
Summary: Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: maven-scm-plugin
Assignee: Brett Porter
Reporter: Dulon Zaman
Created: Wed, 16 Jun 2004 11:07 AM
Updated: Fri, 6 Aug 2004 4:43 PM
Environment: - Windows 2000
- Maven RC3
- CVS client (version 1.12.7 - downloaded from http://www.cvshome.org/dev/codewindow.html)
Description:
Problem:
The problem is that sometimes the scm:prepare-release goal would commit blank project.xml into cvs.
Suggested Cause:
This looks like its due to the fact that the line <r:release-version version="${version_name}" tag="${tag_name}" /> has not finished updating the project.xml, before the project.xml is committed to cvs in the next line. However, our team has not come across any half-completed project.xml just blank or perfectly updated ones.
Suggested Solution:
Add a "sleep" goal inbetween the r:release line and the cvs commit line in the scm:prepare-release goal.
Extra Information:
Here is a maven.xml extract that I hope will you will be able to use to demonstrate the bug and the solution. You should notice in the CVS history of the project.xml you choose to test with that some versions of the checked-in project.xml was blank when running the test goal without the sleep inbetween.
<goal name="release:test-fault"
prereqs="scm:validate">
<echo>Release Test - fault</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<ant:cvs command="commit -m '[release:test-faulty] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
<goal name="release:test-fix"
prereqs="scm:validate">
<echo>Release Test - fix</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<echo>Sleeping for 5 secs to allow the Project.xml to be updated</echo>
<ant:sleep seconds="5"/>
<echo>Now doing the commit</echo>
<ant:cvs command="commit -m '[release:test-fix] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPSCM-11) Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Paul Spencer
Created: Fri, 6 Aug 2004 6:06 PM
Body:
Unless the plugin has been changed to use the CHANGES plugin, it is not a duplicate. I believe this plugin uses the RELEASE plugin.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPSCM-11?page=comments#action_22830
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPSCM-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPSCM-11
Summary: Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: maven-scm-plugin
Assignee: Brett Porter
Reporter: Dulon Zaman
Created: Wed, 16 Jun 2004 11:07 AM
Updated: Fri, 6 Aug 2004 6:06 PM
Environment: - Windows 2000
- Maven RC3
- CVS client (version 1.12.7 - downloaded from http://www.cvshome.org/dev/codewindow.html)
Description:
Problem:
The problem is that sometimes the scm:prepare-release goal would commit blank project.xml into cvs.
Suggested Cause:
This looks like its due to the fact that the line <r:release-version version="${version_name}" tag="${tag_name}" /> has not finished updating the project.xml, before the project.xml is committed to cvs in the next line. However, our team has not come across any half-completed project.xml just blank or perfectly updated ones.
Suggested Solution:
Add a "sleep" goal inbetween the r:release line and the cvs commit line in the scm:prepare-release goal.
Extra Information:
Here is a maven.xml extract that I hope will you will be able to use to demonstrate the bug and the solution. You should notice in the CVS history of the project.xml you choose to test with that some versions of the checked-in project.xml was blank when running the test goal without the sleep inbetween.
<goal name="release:test-fault"
prereqs="scm:validate">
<echo>Release Test - fault</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<ant:cvs command="commit -m '[release:test-faulty] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
<goal name="release:test-fix"
prereqs="scm:validate">
<echo>Release Test - fix</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<echo>Sleeping for 5 secs to allow the Project.xml to be updated</echo>
<ant:sleep seconds="5"/>
<echo>Now doing the commit</echo>
<ant:cvs command="commit -m '[release:test-fix] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MPRELEASE-9) Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Fri, 6 Aug 2004 6:50 PM
Fixed in version 1.5-SNAPSHOT of the release plugin
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPRELEASE-9
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPRELEASE-9
Summary: Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: maven-release-plugin
Assignee: Carlos Sanchez
Reporter: Dulon Zaman
Created: Wed, 16 Jun 2004 11:07 AM
Updated: Fri, 6 Aug 2004 6:50 PM
Environment: - Windows 2000
- Maven RC3
- CVS client (version 1.12.7 - downloaded from http://www.cvshome.org/dev/codewindow.html)
Description:
Problem:
The problem is that sometimes the scm:prepare-release goal would commit blank project.xml into cvs.
Suggested Cause:
This looks like its due to the fact that the line <r:release-version version="${version_name}" tag="${tag_name}" /> has not finished updating the project.xml, before the project.xml is committed to cvs in the next line. However, our team has not come across any half-completed project.xml just blank or perfectly updated ones.
Suggested Solution:
Add a "sleep" goal inbetween the r:release line and the cvs commit line in the scm:prepare-release goal.
Extra Information:
Here is a maven.xml extract that I hope will you will be able to use to demonstrate the bug and the solution. You should notice in the CVS history of the project.xml you choose to test with that some versions of the checked-in project.xml was blank when running the test goal without the sleep inbetween.
<goal name="release:test-fault"
prereqs="scm:validate">
<echo>Release Test - fault</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<ant:cvs command="commit -m '[release:test-faulty] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
<goal name="release:test-fix"
prereqs="scm:validate">
<echo>Release Test - fix</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<echo>Sleeping for 5 secs to allow the Project.xml to be updated</echo>
<ant:sleep seconds="5"/>
<echo>Now doing the commit</echo>
<ant:cvs command="commit -m '[release:test-fix] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPSCM-11) Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Paul Spencer
Created: Fri, 6 Aug 2004 6:07 PM
Body:
Look in the write() method of http://cvs.apache.org/viewcvs.cgi/maven-plugins/release/src/main/org/apache/maven/release/AbstractPomTransformer.java?view=markup
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPSCM-11?page=comments#action_22831
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPSCM-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPSCM-11
Summary: Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: maven-scm-plugin
Assignee: Brett Porter
Reporter: Dulon Zaman
Created: Wed, 16 Jun 2004 11:07 AM
Updated: Fri, 6 Aug 2004 6:07 PM
Environment: - Windows 2000
- Maven RC3
- CVS client (version 1.12.7 - downloaded from http://www.cvshome.org/dev/codewindow.html)
Description:
Problem:
The problem is that sometimes the scm:prepare-release goal would commit blank project.xml into cvs.
Suggested Cause:
This looks like its due to the fact that the line <r:release-version version="${version_name}" tag="${tag_name}" /> has not finished updating the project.xml, before the project.xml is committed to cvs in the next line. However, our team has not come across any half-completed project.xml just blank or perfectly updated ones.
Suggested Solution:
Add a "sleep" goal inbetween the r:release line and the cvs commit line in the scm:prepare-release goal.
Extra Information:
Here is a maven.xml extract that I hope will you will be able to use to demonstrate the bug and the solution. You should notice in the CVS history of the project.xml you choose to test with that some versions of the checked-in project.xml was blank when running the test goal without the sleep inbetween.
<goal name="release:test-fault"
prereqs="scm:validate">
<echo>Release Test - fault</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<ant:cvs command="commit -m '[release:test-faulty] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
<goal name="release:test-fix"
prereqs="scm:validate">
<echo>Release Test - fix</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<echo>Sleeping for 5 secs to allow the Project.xml to be updated</echo>
<ant:sleep seconds="5"/>
<echo>Now doing the commit</echo>
<ant:cvs command="commit -m '[release:test-fix] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPSCM-11) Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 6 Aug 2004 5:50 PM
Body:
Should be fixed with version 1.6 of the changes plugin
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPSCM-11?page=comments#action_22829
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPSCM-11
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPSCM-11
Summary: Sometimes the scm:prepare-release goal would commit blank project.xml into cvs
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 1 day
Time Spent: Unknown
Remaining: 1 day
Project: maven-scm-plugin
Assignee: Brett Porter
Reporter: Dulon Zaman
Created: Wed, 16 Jun 2004 11:07 AM
Updated: Fri, 6 Aug 2004 5:50 PM
Environment: - Windows 2000
- Maven RC3
- CVS client (version 1.12.7 - downloaded from http://www.cvshome.org/dev/codewindow.html)
Description:
Problem:
The problem is that sometimes the scm:prepare-release goal would commit blank project.xml into cvs.
Suggested Cause:
This looks like its due to the fact that the line <r:release-version version="${version_name}" tag="${tag_name}" /> has not finished updating the project.xml, before the project.xml is committed to cvs in the next line. However, our team has not come across any half-completed project.xml just blank or perfectly updated ones.
Suggested Solution:
Add a "sleep" goal inbetween the r:release line and the cvs commit line in the scm:prepare-release goal.
Extra Information:
Here is a maven.xml extract that I hope will you will be able to use to demonstrate the bug and the solution. You should notice in the CVS history of the project.xml you choose to test with that some versions of the checked-in project.xml was blank when running the test goal without the sleep inbetween.
<goal name="release:test-fault"
prereqs="scm:validate">
<echo>Release Test - fault</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<ant:cvs command="commit -m '[release:test-faulty] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
<goal name="release:test-fix"
prereqs="scm:validate">
<echo>Release Test - fix</echo>
<j:forEach begin="0" end="10" indexVar="index">
<j:set var="incrementedVersion" value="${index}-test-SNAPSHOT"/>
<r:release-version version="${incrementedVersion}" tag="Not Tagged"/>
<echo>Sleeping for 5 secs to allow the Project.xml to be updated</echo>
<ant:sleep seconds="5"/>
<echo>Now doing the commit</echo>
<ant:cvs command="commit -m '[release:test-fix] testing the release - no: ${index}' -f project.xml"
quiet="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.quiet')}"
cvsRsh="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.rsh')}"
cvsRoot="${pom.getPluginContext('maven-scm-plugin').getVariable('maven.scm.cvs.root')}"
failonerror="true"/>
</j:forEach>
</goal>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org