[ 
https://issues.apache.org/jira/browse/QPID-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813000#comment-13813000
 ] 

ASF subversion and git services commented on QPID-5287:
-------------------------------------------------------

Commit 1538674 from [email protected] in branch 'qpid/trunk'
[ https://svn.apache.org/r1538674 ]

QPID-5287: .NET binding does not set AssemblyVersion to build version.
The fix is
1. rename the AssemblyInfo.cpp to indicate that it is a template.
2. put replacement strings into the template (see sessionreceiver for correct 
pattern).
3. configure the template during cmake run.
4. Refer to generated file in projects that need it.

> .NET binding does not set Assembly version number
> -------------------------------------------------
>
>                 Key: QPID-5287
>                 URL: https://issues.apache.org/jira/browse/QPID-5287
>             Project: Qpid
>          Issue Type: Bug
>          Components: Build Tools
>    Affects Versions: 0.25
>         Environment: Windows .NET binding; any visual studio, any platform, 
> any configuration
>            Reporter: Chuck Rolke
>            Assignee: Chuck Rolke
>              Labels: build
>
> The build scheme sets the File and Product version numbers. A stock trunk 
> build will set the File Properties version numbers to 0.22.0.1. Overrides can 
> set these to any desired release values, for instance 1.2.0.100.
> However, in file AssemblyInfo.cpp the Assembly version number is set to
> [assembly:AssemblyVersionAttribute("1.0.*")];
> The net effect is that the Assembly version number is autogenerated and not a 
> predictable value. 
> This issue tracks creating a cmake template AssemblyInfo.cpp file and using 
> configure_file to generate the source with the desired version number in it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to