You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Andreas Ländle (JIRA)" <ji...@apache.org> on 2010/02/08 18:03:34 UTC
[jira] Created: (AMQNET-229) Please sign compact framework
assemblies in official builds
Please sign compact framework assemblies in official builds
-----------------------------------------------------------
Key: AMQNET-229
URL: https://issues.apache.org/activemq/browse/AMQNET-229
Project: ActiveMQ .Net
Issue Type: Wish
Components: NMS, Stomp
Affects Versions: 1.2.0
Environment: .Net CF 2.0
Reporter: Andreas Ländle
Assignee: Jim Gomes
Please sign the compact framework assemblies in official builds so that the can be used without problems in signed projects.
I can't see any reason why the assemblies in the netcf-2.0-framework-configuration aren't signed with a strong name key ("<property name="current.build.framework.sign" value="false" />") - is there any reason?
Let me know if you need more information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQNET-229) Please sign compact framework
assemblies in official builds
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes resolved AMQNET-229.
------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Added signing to .NET Compact Framework builds.
> Please sign compact framework assemblies in official builds
> -----------------------------------------------------------
>
> Key: AMQNET-229
> URL: https://issues.apache.org/activemq/browse/AMQNET-229
> Project: ActiveMQ .Net
> Issue Type: Wish
> Components: NMS, Stomp
> Affects Versions: 1.2.0
> Environment: .Net CF 2.0
> Reporter: Andreas Ländle
> Assignee: Jim Gomes
> Fix For: 1.3.0
>
>
> Please sign the compact framework assemblies in official builds so that the can be used without problems in signed projects.
> I can't see any reason why the assemblies in the netcf-2.0-framework-configuration aren't signed with a strong name key ("<property name="current.build.framework.sign" value="false" />") - is there any reason?
> Let me know if you need more information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQNET-229) Please sign compact framework
assemblies in official builds
Posted by "Andreas Ländle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Ländle updated AMQNET-229:
----------------------------------
Attachment: SignCfAssemblies_svn907773mergedInto12xBranches.patch
For those who are interested in a patch for the 1.2.x branches.
(I only merged svn#907773 into the corresponding 1.2.x branches - no further code changes!).
> Please sign compact framework assemblies in official builds
> -----------------------------------------------------------
>
> Key: AMQNET-229
> URL: https://issues.apache.org/activemq/browse/AMQNET-229
> Project: ActiveMQ .Net
> Issue Type: Wish
> Components: NMS, Stomp
> Affects Versions: 1.2.0
> Environment: .Net CF 2.0
> Reporter: Andreas Ländle
> Assignee: Jim Gomes
> Fix For: 1.3.0
>
> Attachments: SignCfAssemblies_svn907773mergedInto12xBranches.patch
>
>
> Please sign the compact framework assemblies in official builds so that the can be used without problems in signed projects.
> I can't see any reason why the assemblies in the netcf-2.0-framework-configuration aren't signed with a strong name key ("<property name="current.build.framework.sign" value="false" />") - is there any reason?
> Let me know if you need more information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.