You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2008/01/11 12:27:34 UTC

[jira] Created: (QPID-731) Version in .Net assemblies should be corrected.

Version in .Net assemblies should be corrected.
-----------------------------------------------

                 Key: QPID-731
                 URL: https://issues.apache.org/jira/browse/QPID-731
             Project: Qpid
          Issue Type: Bug
          Components: Dot Net Client
    Affects Versions: M2
            Reporter: Rupert Smith
             Fix For: M2.1


The .Net uses assembly files which contain a version stamp, currently 0.5.* which gets written into the binary build artifacts. This would cause people using the .Net to believe they are using version 0.5.x when in fact they are using a version 2.x. This could cause a lot of confusion because 0.5 versions are of GDM/GTW vintage and their are already issues around knowing which versions are in production.

Update version to 2.x and rebuild. Also investigate version stamps in existing binaries and try to map version stamp onto release number.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (QPID-731) Version in .Net assemblies should be corrected.

Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575448#action_12575448 ] 

Aidan Skinner commented on QPID-731:
------------------------------------

http://svn.apache.org/viewvc?rev=611826&view=rev http://svn.apache.org/viewvc?rev=611828&view=rev

> Version in .Net assemblies should be corrected.
> -----------------------------------------------
>
>                 Key: QPID-731
>                 URL: https://issues.apache.org/jira/browse/QPID-731
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>    Affects Versions: M2
>            Reporter: Rupert Smith
>             Fix For: M2.1
>
>
> The .Net uses assembly files which contain a version stamp, currently 0.5.* which gets written into the binary build artifacts. This would cause people using the .Net to believe they are using version 0.5.x when in fact they are using a version 2.x. This could cause a lot of confusion because 0.5 versions are of GDM/GTW vintage and their are already issues around knowing which versions are in production.
> Update version to 2.x and rebuild. Also investigate version stamps in existing binaries and try to map version stamp onto release number.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (QPID-731) Version in .Net assemblies should be corrected.

Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aidan Skinner resolved QPID-731.
--------------------------------

    Resolution: Fixed

> Version in .Net assemblies should be corrected.
> -----------------------------------------------
>
>                 Key: QPID-731
>                 URL: https://issues.apache.org/jira/browse/QPID-731
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>    Affects Versions: M2
>            Reporter: Rupert Smith
>             Fix For: M2.1
>
>
> The .Net uses assembly files which contain a version stamp, currently 0.5.* which gets written into the binary build artifacts. This would cause people using the .Net to believe they are using version 0.5.x when in fact they are using a version 2.x. This could cause a lot of confusion because 0.5 versions are of GDM/GTW vintage and their are already issues around knowing which versions are in production.
> Update version to 2.x and rebuild. Also investigate version stamps in existing binaries and try to map version stamp onto release number.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.