[
http://jira.codehaus.org/browse/MOJO-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176196#action_176196
]
darren hartford commented on MOJO-1356:
---------------------------------------
looked at the source code. The tags they have documented:
<doCheck>true</doCheck>
<doUpdate>true</doUpdate>
These determine whether or not to remotely check via 'svn update'. The project
is also using 'svn info' for actual information in the beta-3 tag (last
modified May 1) -- setting both doCheck/doUpdate to false will never call the
SVN server/no remote calls.
BUT...
The 'svn info' doesn't seem to get the correct revision number, only the last
revision number until an 'svn update' is run. commiting files so there is a
new svn revision does NOT reflect without the doCheck=true/doUpdate=true OR
manually doing an 'svn update' to get a new update --- this makes sense as this
is the understanding of any SCM - just because you commited a file, doesn't
mean you have the full revision of that project available.
Going back to maven convention, since you probably don't want developers to
constantly be doing manual 'svn update', the existing functionality with
doCheck/doUpdate seems appropriate. Just need to get the remoting aspects to
the SCM's worked out.
my two coppers as a user,
-D
> 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
> Attachments: SvnInfo.xml, XpathSvnInfoParser.java
>
>
> 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
