[wildfly-dev] WildFly Bootstrap(ish)

[James R. Perkins]

Excellent. I'll have a look at what's going on there.

--
James R. Perkins
JBoss by Red Hat

On Jun 9, 2014 7:11 PM, Shelly McGowan <smcgowan at redhat.com> wrote:
>
>
>
> Launcher API JIRA: 
> https://issues.jboss.org/browse/WFLY-2427 
>
> contains p

Launcher API JIRA:
https://issues.jboss.org/browse/WFLY-2427

contains previous discussion and input from tools team.


Shelly


----- Original Message -----
From: "James R. Perkins" <jperkins at redhat.com>
To: "Stuart Douglas" <stuart.w.douglas at gmail.com>
Cc: wildfly-dev at lists.jboss.org
Sent: Monday, June 9, 2014 6:48:41 PM
Subject: Re: [wildfly-dev] WildFly Bootstrap(ish)

That would be easy enough to do. I created a quick project locally to 
just build a Server object to start, stop and check the state. Using 
some kind of builder to create the command or command parameters would 
be quite easy.

On 06/09/2014 03:45 PM, Stuart Douglas wrote:
> We talked about this in Brno, as this was something the tools team 
> wanted. I think what they were after was some bootstrap API that 
> basically gave them the command line arguments they needed to launch 
> the server, although I can't remember the full details.
>
> Stuart
>
> James R. Perkins wrote:
>> For the wildfly-maven-plugin I've written a simple class to launch a
>> process that starts WildFly. It also has a thin wrapper around the
>> deployment builder to ease the deployment process.
>>
>> I've heard we've been asked a few times about possibly creating a Gradle
>> plugin. As I understand it you can't use a maven plugin with Gradle. I'm
>> considering creating a separate bootstrap(ish) type of project to simple
>> launch WildFly from Java. Would anyone else find this useful? Or does
>> anyone have any objections to this?
>>

-- 
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