harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HARMONY-1083) [drlvm][build] Avoid touching svn_version_tag.h if svn information is not available
Date Wed, 11 Oct 2006 17:02:36 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1083?page=all ]

Mark Hindess resolved HARMONY-1083.

    Resolution: Fixed

Thanks Salikh.  I've applied your patch in r462856.  Please confirm that this has been applied
as expected.

> [drlvm][build] Avoid touching svn_version_tag.h if svn information is not available
> -----------------------------------------------------------------------------------
>                 Key: HARMONY-1083
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1083
>             Project: Harmony
>          Issue Type: Improvement
>         Environment: Windows/ia32
>            Reporter: Salikh Zakirov
>         Assigned To: Mark Hindess
>         Attachments: 0001-Restricted-svn-revision-stamping-to-svn-workspaces.patch, 0001-Restricted-svn-revision-stamping-to-svn-workspaces.patch,
> I would like to suggest to make svn revision stamping optional.
> In my use case, I do not have .svn directory in most of my
> workspaces, because I use other version control system for managing
> local patches, so 'java -version' says on my local builds
>   java version "1.5.0" 
>   pre-alpha : not complete or compatible
>   svn = rsvn: '.' is not a working copy, (Aug  7 2006), Windows/ia32/msvc 1310, debug
>   http://incubator.apache.org/harmony
> and obviously is not helpful.
> However, having version_svn_tag.h file modified after each
> build is annoying -- it always shows up in diff, prevents me
> from merging with latest revision from SVN etc.
> The attached patch solves the problem.
> It prevents the version_svn_tag.h from being overwritten if svn revision information
> is not available.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message