[jboss-as7-dev] Looking for naming help

[Max Rydahl Andersen]

>>> that would require an external vm launch or are you saying CLI has
>>> API we can call ?
>> I don't know if it does or not.  Alexey?
>> 
>> If not, I can't imagine that it would be that hard to create.
>> 
> I would say https://github.com/jbossas/jboss-as/blob/master/controller-client/src/main/java/org/jboss/as/controller/client/ModelControllerClient.java#L89

That API is like handing out a HashMap to someone who would like a typed interface ;)

anyway - my point is that using the CLI doesn't give much unless there are significant work done on making a higher level "API" for the CLI (i.e. like glassfish has a set of standard operations)
and using it from the mvn plugin (or any other tooling) efficiently would need a way to do that without requiring a new VM instance IMO.

Until then, yes - the only API we have is the detyped one which means alot of guess work and trial and errors for everyone trying to use it - but at least
they will use the same api :)


/max

> 
> Carlo
>>> 
>>> /max
>>> 
>>> On Jun 6, 2011, at 18:29, ssilvert at redhat.com wrote:
>>> 
>>>> Here's an idea.  Why not just have your Maven plugin kick off a CLI
>>>> script?  The script could be read from a file or specified inside the
>>>> POM.  Then you could do anything you want and you don't need to create
>>>> your own command vocabulary.
>>>> 
>>>> Stan
>>>> 
>>>> Quoting James Perkins<jperkins at redhat.com>:
>>>> 
>>>>> On 06/06/2011 03:09 AM, Pete Muir wrote:
>>>>>> Another option is add a strict flag to the deploy goal:
>>>>>> 
>>>>>> e.g.
>>>>>> 
>>>>>> strict -- default false, if false, the plugin will deploy the
>>>>>> application if not already deployed, otherwise it will attempt a
>>>>>> redeploy.
>>>>>> 
>>>>>> Of course, I'm arguing for false as the default, but we could have
>>>>>> true. Either way, removes the naming problem..
>>>>>> 
>>>>>> On 6 Jun 2011, at 11:05, Pete Muir wrote:
>>>>>> 
>>>>> I like the strict option. I think I'll go with that. Seems to make the
>>>>> most sense and could loosen up other options in the future if needed too.
>>>>> 
>>>>> So in the end we'll end up with 3 goals; deploy, redeploy and undeploy.
>>>>> 
>>>>> Thanks for the help all.
>>>>> 
>>>>> --
>>>>> James R. Perkins
>>>>> JBoss by Red Hat
>>>>> 
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>> /max
>>> http://about.me/maxandersen
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> 

/max
http://about.me/maxandersen