I don't know if such approach is feasible for JBoss, but for PMD, I had
the same issues. Every time we added a new "main" (ie a tool) we had yet
another scripts. As all of those scripts more/less did the same thing, I
end up having one, single bash script called "run.sh" that required,
as a first param the name of the "main class" to run.
I wonder if we could have something like that:
(and so on...)
This would work only if all those "admin utilities" more/less required
the same classpath. (or at least survives sharing classpath with other
On Thu, May 07, 2015 at 09:41:21AM -0400, Edward Wertz wrote:
I'm currently working on an upgrade of the AESH console used by the CLI. Mostly to
get a more familiarity with the code base, but also to fix some lingering issues and make
it easier to create new commands. After that, and possibly some refactoring, I was going
to start trying to gather some information about how people use the interface, either CLI
or GUI, and what else they'd like it to be able to do. I hadn't given further
development too much thought yet though.
Folding in the other script's functionality, like add-user at minimum since it's
in wildfly-core, does seem like an obvious place to start when you mention it. If
something is going to be called 'the' CLI, after all, it should probably be the
only necessary interface. I was already working on getting AESH to handle nested commands.
Something simple for the upgrade, but it might be able to expand into something able to
act as an entry point for the other script functionality as well.
I'm not sure about how to handle scripts outside of core. But, I suppose that's a
bridge to cross after add-user works.
I'll keep this in mind. I might have been trying to think of large enhancements, but
the small annoyance of needing to use 2 or 3 different scripts instead of one can easily
be just as bad as any missing functionality. It's already there, just badly organized,
which is almost worse than it not existing in the first place.
----- Original Message -----
> From: "Darran Lofthouse" <darran.lofthouse(a)jboss.com>
> To: wildfly-dev(a)lists.jboss.org
> Sent: Thursday, May 7, 2015 6:16:33 PM
> Subject: [wildfly-dev] Bring back jboss-admin.sh
> Before it was called jboss-cli,sh the script was called
> IMO the latter was always a more obvious name for users to call but
> it was only a CLI the name was changed. Then we added a GUI mode.
> I would think we could then add more to it: -
> - Give our admin tool the ability to start jconsole.
> - Add the user maintenance and SSL maintenance features to it.
> - Give it the ability to start your web browser for the admin
> For the latter I wonder if we could benefit from the tool having a
> connection to the server, maybe make use of KeyCloak to obtain an SSO
> token that is included in the URL to start the browser and we could
> possibly achieve a form of local auth for web.
> Not sure what other thoughts are but these are just a couple of
> on my mind.
> Darran Lofthouse.
> wildfly-dev mailing list
wildfly-dev mailing list
Red Hat GmbH
Zieher Business Centers,
Am Treptower Park 75,
Cell (DE): +49 (0) 172-7442628
Cell (FR): +33 (0) 669304455
Delivering value year after year
Red Hat ranks # 1 in value among software vendors
Red Hat GmbH, http://www.de.redhat.com/
Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Charles