I changed the title as this is a different topic.
It's a good point, Max. It seems like it should be possible to have some
sort of factory API to specify the version of the process being launched.
Apologies in advance, James, if that's already there.
There are funny details to consider, e.g. how to specify the version,
since now it's really WildFly Core versions that are relevant, while
previous releases are AS or EAP or WildFly full.
My guess is what's there now will work for any release we've had since
AS 7.0. We haven't been changing our launch commands. Of course there
may be some new args introduced over time that won't work on old
releases, but that's to be expected.
On 6/10/15 2:27 AM, Max Rydahl Andersen wrote:
I think it has potential and is interesting.
The big problem I keep having with these are that unless I'm missing
I can't use one version of this library to control multiple versions of
- I must still have the matching jar to the exact runtime version,
meaning using it from tools that need to support multiple versions
wanting to ask the user to choose a specific jar this is of limited use
something like maven plugins :/
> Hello All,
> I've had a few issues file recently against the wildfly-maven-plugin
> about CLI commands that aren't available to the plugin. The issue is
> using the CLI API to take commands and create DMR operations out of
> them. Since the commands can be defined in the subsystems I don't see
> those commands as I'm not operating in a modular environment.
> This led me to create a new API in for the Launcher API . All this
> does is build a command to launch a new CLI process. I'm sure if it
> would be useful to others or not. If not maybe it doesn't belong in
> launcher API and I should just keep it in the maven plugin.
> Any opinions are welcome. Let me know if you'd find this useful.
> : https://github.com/wildfly/wildfly-core/pull/764
> James R. Perkins
> JBoss by Red Hat
> wildfly-dev mailing list
wildfly-dev mailing list
Senior Principal Software Engineer
JBoss by Red Hat