I've fixed a few bugs reported in the new asadmin so I think it's
ready to make the switch. I've just checked in the changes that
make the new version of asadmin the default. If you run into
problems you can get the old version by setting the environment
variable ASADMIN_NEW=false.
In addition to the differences described below, there is a problem
with the create-jvm-options command - if the JVM option starts with
"-" (as it almost always does), you'll need to separate it from the
other options using "--", e.g.,
asadmin create-jvm-options -- -Dfoo=bar
This is a regression that I'll fix soon.
Also, the following commands haven't yet been converted to the new
asadmin framework:
create-domain
delete-domain
create-service
Again, that will happen soon.
If you run into any other problems, please do let me know.
Thanks!
Bill Shannon wrote on 7/14/09 2:01 PM:
> As some of you know, I've been fixing some problems in the asadmin
> command to make it more compatible with v2. All my work has been
> done "on the side", without impacting the existing v3 asadmin.
>
> After talking to Kedar and Byron, I think it's time to change that.
>
> Right now you can experiment with the new version of asadmin by setting
> the system environment variable ASADMIN_NEW=true, e.g.,
>
> export ASADMIN_NEW=true
> asadmin ...
>
> If you haven't already, please try that out and let me know of any
> problems.
>
> *If I don't hear complaints, I'm going to switch the default tomorrow.*
>
> After the change, you'll be able to set ASADMIN_NEW=false to get the old
> behavior, at least for a short time until we're completely convinced
> that the new version is working properly.
>
>
> The new version of asadmin has the following important differences:
>
> The --path option to (e.g.) the deploy command that appeared in v3 has
> been removed. Specify the path as the operand to the command.
>
> The asadmin "program options", e.g.
>
> --host
> --port
> --user
> --passwordfile
> --terse
> --interactive
> --secure
>
> can and should be specified *before* the command name, e.g.,
>
> $ asadmin --host myhost --port 5555 list-applications
>
> Although we still support supplying them after the command name,
> you'll get a warning about deprecated syntax.
>
> Other than those things, let me know where the new asadmin behaves
> differently than what you expect based on the v2 asadmin.
>
> Thanks.