Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <31639829.1172572746712.JavaMail.jira@brutus>
Date: Tue, 27 Feb 2007 02:39:06 -0800 (PST)
From: "james strachan (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Moved: (AMQNET-31) Use Apache prefix for .Net namespace
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQNET-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

james strachan moved AMQ-946 to AMQNET-31:
------------------------------------------

          Component/s:     (was: NMS (C# client))
    Affects Version/s:     (was: 4.x)
                  Key: AMQNET-31  (was: AMQ-946)
              Project: ActiveMQ .Net  (was: ActiveMQ)

> Use Apache prefix for .Net namespace
> ------------------------------------
>
>                 Key: AMQNET-31
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-31
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>            Reporter: Rob Lugt
>            Priority: Minor
>
> .Net namespaces shoudl follow guidelines similar to Java namespaces.  Microsofts guidelines are available here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/cpconNamespaceNamingGuidelines.asp
> In order to be a good neighbour, the NMS and ActiveMQ namespaces should be part of an Apache top-level namespace e.g. 
> namespace Apache.NMS
> {
> }

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