[wildfly-dev] CLI Command Builder

Alexey Loubyansky alexey.loubyansky at redhat.com
Wed Jun 10 08:07:21 EDT 2015


I agree with Joe. Thanks James for looking into this.

Alexey

On 06/10/2015 01:01 PM, Edward Wertz wrote:
> I was actually about to create a much more basic process builder to restructure the CLI tests a bit.
>
> In a general sense I think I'm comfortable maintaining an API like this. If it's not maintained here, something similar, but more basic, should already be getting maintained in the testsuite anyway. Otherwise we're missing test coverage. So I don't see much additional work involved. It's just a matter of remembering where to do it. Not whether it would be getting done.
>
> Unless there's some other impact I'm not seeing?
>
> -- Joe
>
> ----- Original Message -----
>> From: "James R. Perkins" <jperkins at redhat.com>
>> To: wildfly-dev at lists.jboss.org
>> Sent: Wednesday, June 10, 2015 4:17:53 AM
>> Subject: Re: [wildfly-dev] CLI Command Builder
>>
>> 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
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


More information about the wildfly-dev mailing list