atom feed24 messages in net.java.dev.glassfish.adminRe: new asadmin command
FromSent OnAttachments
Bill ShannonJul 14, 2009 2:01 pm 
Byron NevinsJul 14, 2009 2:35 pm 
Paul DaviesJul 14, 2009 6:37 pm 
Bill ShannonJul 15, 2009 12:19 am 
Sankar NeelakandanJul 16, 2009 9:18 am 
Kedar MhaswadeJul 16, 2009 9:25 am 
Sankar NeelakandanJul 16, 2009 10:04 am 
Lloyd ChambersJul 16, 2009 10:05 am 
Kedar MhaswadeJul 16, 2009 10:08 am 
Kedar MhaswadeJul 16, 2009 10:11 am 
Lloyd ChambersJul 16, 2009 10:15 am 
Bill ShannonJul 16, 2009 1:37 pm 
Bill ShannonJul 16, 2009 2:29 pm 
Scott OaksJul 27, 2009 8:59 am 
Kedar MhaswadeJul 27, 2009 1:17 pm 
Paul DaviesJul 28, 2009 6:43 pm 
Paul DaviesAug 3, 2009 11:10 am 
Paul DaviesAug 3, 2009 2:23 pm 
Paul DaviesAug 4, 2009 6:27 pm 
Shreedhar GanapathyAug 4, 2009 7:25 pm 
Paul SterkAug 5, 2009 9:12 am 
Sreenivas MunnangiAug 5, 2009 9:34 am 
Dixie PineAug 5, 2009 9:46 am 
Paul DaviesAug 5, 2009 9:52 am 
Subject:Re: new asadmin command
From:Lloyd Chambers (Lloy@Sun.COM)
Date:Jul 16, 2009 10:05:28 am
List:net.java.dev.glassfish.admin

Yes, I think when we ship, it should definitely be AS_ADMIN_OLD.

We want to have people think in terms of the current version vs the *old*.

Lloyd

On Jul 15, 2009, at 12:20 AM, Bill Shannon wrote:

Byron Nevins wrote on 7/14/09 2:35 PM:

Kudos to Bill!

I have one suggestion and one Tip based on Bill's work:

Suggestion: Change the env. variable to ASADMIN_OLD instead of checking for a false value to ASASMIN_NEW. I.e. it ain't new anymore, the previous has now become old and the new has become regular. You can just drop the ASADMIN_OLD anytime later...

I was hoping to avoid confusing people who knew about ASADMIN_NEW, but it doesn't matter to me either way. Anyone else care?