[ 
https://issues.apache.org/jira/browse/XERCESC-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Cantor resolved XERCESC-1836.
-----------------------------------
    Resolution: Won't Do

Not aware of any demand for this and anybody doing a build of unreleased code 
can change it anyway they like.

> Add SVN revsion number to version number
> ----------------------------------------
>
>                 Key: XERCESC-1836
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1836
>             Project: Xerces-C++
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 3.0.0
>         Environment: MS Windows XP SP3, VS2005/8
>            Reporter: David Kelvin
>            Priority: Minor
>
> A number of Open Source projects, that generate executables and DLL files, 
> add the SVN version number to the version displayed via properties [I don't 
> know if the equivalent is available for non-Windows platforms].
> This is normally done in the custom Pre-Build step that uses TortoiseSVN's 
> "SubWCRev.exe" program to copy a file (e.g. version.in) to a new file 
> (version.h) which defines the current revision level.  This is included in 
> the corresponding resource file so that it is visible to the user. See 
> project http://passwordsafe.sourceforge.net/ as an example.
> So with the current level: the propery page would show the DLL was 
> 3.0.0.708302.
> I think this would be useful when an application wanted to make sure that the 
> version in use has a specific fix included prior to a formal release.
> Thanks.
> David



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to