activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Pollack (JIRA)" <>
Subject [jira] Commented: (AMQNET-115) Remove strong naming of assemblies
Date Mon, 15 Sep 2008 19:16:52 GMT


Mark Pollack commented on AMQNET-115:


Can you elaborate on what you mean by "It offers no real improvement since versioning can
be done with embedded naming if desired."  

In my experience, strongly signed assemblies are very important to users with the expectation
that important libraries are distributed as strongly signed assemblies.  Spring.NET, NHibernate,
Quartz.NET, Castle, and I'm sure many other .NET open source projects (perhaps even iBatis.NET)
distribute strongly signed assemblies and by extension require their dependencies to be strongly
signed.  Some put the private key in svn and other, like Spring.NET/Quartz.NET, just give
the key privately to whoever is doing the build.  The build has logic to detect 'release'
build done with a key and avoid building if no key is detected.  Users can then only perform
a debug build or create their own private key should they require a strongly signed assembly.


> Remove strong naming of assemblies
> ----------------------------------
>                 Key: AMQNET-115
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Task
>          Components: ActiveMQ Client, EMS, MSMQ, Stomp
>    Affects Versions: 1.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>             Fix For: 1.0
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> Strong naming of assemblies is problematic in an open-source build environment.  It offers
no real improvement since versioning can be done with embedded naming if desired.

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

View raw message