activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Work logged: (AMQNET-115) Remove strong naming of assemblies
Date Thu, 09 Oct 2008 20:51:52 GMT


Jim Gomes logged work on AMQNET-115:

                Author: Jim Gomes
            Created on: 09/Oct/08 01:50 PM
            Start Date: 09/Oct/08 01:46 PM
    Worklog Time Spent: 6 hours 
      Work Description: Removed the keyfile references from the Microsoft Visual Studio project
files.  This allows all developers to easily build and perform local deployments in their
own projects.

The NAnt scripts will optionally build a signed Release version of the assemblies if the ACTIVEMQ_DOTNET_SNK
environment variable is set to a pathname of the strong keyfile.

Official builds of NMS will be strongly named, as they will be generated from the NAnt scripts.

Issue Time Tracking

    Remaining Estimate: 0 minutes  (was: 1 hour)
            Time Spent: 6 hours

> 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
>          Time Spent: 6 hours
>  Remaining Estimate: 0 minutes
> 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