Re: [wildfly-dev] CLI Command Builder

Won't you miss some command handlers that can be loaded through the subsystems themselves ? Emmanuel Le 10/06/2015 09:27, Max Rydahl Andersen a écrit : > I think it has potential and is interesting. > > The big problem I keep having with these are that unless I'm missing > something > I can't use one version of this library to control multiple versions of > WildFly/EAP > - I must still have the matching jar to the exact runtime version, > correct ? > > meaning using it from tools that need to support multiple versions > without > wanting to ask the user to choose a specific jar this is of limited use > outside > something like maven plugins :/ > > /max > > >> 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 >> >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > /max > http://about.me/maxandersen > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev >