Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of paulmcmahan@gmail.com
 designates 209.85.198.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
        b=MYduLuL9171QFMWgD37SF/Hhhe4X7P+z7ACG3H2p/d+p5n+FYrHKKNyvumgc9S8HMuUKvmwyxc7f0HbP8qa5B+H4FXZlPfUY9gmwQYnfrITUG+Yk3bnt0XmGEkMqDA0m03fIwUf7JcB3V2LSsCRWMTC4er4nvUd/rc7S3DNwuY4=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <0F5164B3-EB2B-4861-9050-C25F57016D9F@gmail.com>
References: <362394.87631.qm@web31712.mail.mud.yahoo.com>
 <0F5164B3-EB2B-4861-9050-C25F57016D9F@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BF9A62F9-23BF-426D-B477-6976FB7949A3@gmail.com>
Content-Transfer-Encoding: 7bit
From: Paul McMahan <paulmcmahan@gmail.com>
Subject: Re: [DISCUSS] Moving the Monitoring Plugin Into Trunk
Date: Thu, 6 Dec 2007 13:06:34 -0500
To: dev@geronimo.apache.org


On Dec 6, 2007, at 12:45 PM, Kevan Miller wrote:

> 1. Are we ready to move monitoring plugin out of sandbox?
+1

> 2. If yes, then where should we move it to? Should it be in server/ 
> trunk/plugins or should the monitoring plugin be a subproject.
I would vote for server/trunk/plugins,  if for no other reason than  
to synchronize the monitoring plugin release with the server  
release.  When the plugin gets to be more mature and can support  
multiple versions of geronimo then maybe we would consider moving it  
to a separate subproject.  Also, moving it to trunk ensures that it  
will be included in the plugin catalog (~/.m2/repo/geronimo- 
plugins.xml) when you build trunk and will make it very easy to add  
monitoring to an assembly by just editing that assembly's pom.

> 3. What bug fixes/new features need to be added to the monitoring  
> plugin before it's ready to be released?
I agree with Anita that it will need some testing & feedback before  
releasing to the wild.  IMO the best way to facilitate that type of  
exposure is to move it into trunk.  I think that this new monitoring  
feature is important enough to justify holding up a 2.1 release if it  
actually comes down to that.


Best wishes,
Paul