Use 'svn info' instead of 'svn status' and 'svn update' to determine revision 
number
------------------------------------------------------------------------------------

                 Key: MOJO-1356
                 URL: http://jira.codehaus.org/browse/MOJO-1356
             Project: Mojo
          Issue Type: Improvement
          Components: buildnumber
    Affects Versions: buildnumber-maven-plugin-1.0-beta-3
         Environment: [INFO] [enforcer:display-info {execution: default}]
[INFO] Maven Version: 2.1.0
[INFO] JDK Version: 1.5.0_16 normalized as: 1.5.0-16
[INFO] OS Info: Arch: i386 Family: unix Name: linux Version: 2.6.28.10
            Reporter: jieryn


The buildnumber plugin attempts at least two separate ways to determine the 
revision number for a particular module. The two ways that I see happening are, 
from the horse's mouth:

[INFO] [buildnumber:create {execution: default}]
[INFO] Verifying there are no local modifications ...
[INFO] Executing: /bin/sh -c cd /home/jesse/workspace/project/base/discovery && 
svn --non-interactive status
[INFO] Working directory: /home/jesse/workspace/project/base/discovery
[INFO] Executing: /bin/sh -c cd /home/jesse/workspace/project/base/discovery && 
svn --non-interactive update /home/jesse/workspace/project/base/discovery
[INFO] Working directory: /home/jesse/workspace/project/base/discovery
[INFO] Got a revision during update: 381
[INFO] No files needed updating.

And yet, `svn --non-interactive info` gives a very clear and concise way to 
obtain the information. Whereas `svn --non-interactive update` could 
potentially harm the checkout depending on a user's $HOME/.svn/config settings. 
Please just use the status command to obtain the revision information when SCM 
is detected to be Subversion.


-- 
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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to