I don't mind maintaining it, but yeah their input would be helpful.
Though if I'm the only one that would use it then maybe it just doesn't
belong in WildFly at all :)
On 06/09/2015 12:57 PM, Brian Stansberry wrote:
The biggest thing is whether Alexey and Joe are comfortable to
commiting
to what you've done as a long term API.
On 6/9/15 12:34 PM, James R. Perkins wrote:
> 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 I'm
> 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 [1]. 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 the
> 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.
>
> [1]:
https://github.com/wildfly/wildfly-core/pull/764
>
--
James R. Perkins
JBoss by Red Hat