7:13 p.m.
Hello All,
While working on the Maven deployment plugin we've been contemplating
what the goals should be named. Currently we have 4 goals; deploy,
deploy-or-redeploy, redeploy and undeploy.
We kind of feel deploy-or-redeploy will be the default most people would
use. It seems a little verbose for the default. I've thought about
making deploy act as the deploy-or-redeploy, but I'm a bit concerned
that users will assume it will fail if the deployment already exists.
So my question to the lot of you is how would you interpret these goals
and can you think of some better names? Mainly a replacement for
deploy-or-redeploy, but any other suggestions are welcome.
Currently as a replacement for deploy-or-redeploy we have always-deploy
and force-deploy.
Thanks in advance,
--
James R. Perkins
JBoss by Red Hat
2:01 a.m.
Take a look at this document:
http://community.jboss.org/wiki/AS7DeploymentTerms
On Jun 5, 2011, at 2:13 AM, James Perkins wrote:
Hello All,
While working on the Maven deployment plugin we've been contemplating
what the goals should be named. Currently we have 4 goals; deploy,
deploy-or-redeploy, redeploy and undeploy.
We kind of feel deploy-or-redeploy will be the default most people would
use. It seems a little verbose for the default. I've thought about
making deploy act as the deploy-or-redeploy, but I'm a bit concerned
that users will assume it will fail if the deployment already exists.
So my question to the lot of you is how would you interpret these goals
and can you think of some better names? Mainly a replacement for
deploy-or-redeploy, but any other suggestions are welcome.
Currently as a replacement for deploy-or-redeploy we have always-deploy
and force-deploy.
Thanks in advance,
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5:05 a.m.
On 5 Jun 2011, at 01:13, James Perkins wrote:
Hello All,
While working on the Maven deployment plugin we've been contemplating what the goals
should be named. Currently we have 4 goals; deploy, deploy-or-redeploy, redeploy and
undeploy.
We kind of feel deploy-or-redeploy will be the default most people would use. It seems a
little verbose for the default. I've thought about making deploy act as the
deploy-or-redeploy,
I'm for making deploy-or-redeploy the "default" - i.e. the deploy goal.
but I'm a bit concerned that users will assume it will fail if
the deployment already exists.
Something I mean to ask was why users would assume this? Because this is the way deploy
works in the AS7 deployment API?
So my question to the lot of you is how would you interpret these goals and can you think
of some better names? Mainly a replacement for deploy-or-redeploy, but any other
suggestions are welcome.
Currently as a replacement for deploy-or-redeploy we have always-deploy and
force-deploy.
Thanks in advance,
--
James R. Perkins
JBoss by Red Hat
5:09 a.m.
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:
On 5 Jun 2011, at 01:13, James Perkins wrote:
> Hello All,
> While working on the Maven deployment plugin we've been contemplating what the
goals should be named. Currently we have 4 goals; deploy, deploy-or-redeploy, redeploy and
undeploy.
>
> We kind of feel deploy-or-redeploy will be the default most people would use. It
seems a little verbose for the default. I've thought about making deploy act as the
deploy-or-redeploy,
I'm for making deploy-or-redeploy the "default" - i.e. the deploy goal.
> but I'm a bit concerned that users will assume it will fail if the deployment
already exists.
Something I mean to ask was why users would assume this? Because this is the way deploy
works in the AS7 deployment API?
>
> So my question to the lot of you is how would you interpret these goals and can you
think of some better names? Mainly a replacement for deploy-or-redeploy, but any other
suggestions are welcome.
>
> Currently as a replacement for deploy-or-redeploy we have always-deploy and
force-deploy.
>
> Thanks in advance,
>
> --
> James R. Perkins
> JBoss by Red Hat
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5:17 a.m.
+1. Most users will assume a deploy does redeployment, too.
On 06/06/2011 13:09, 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:
>
>
> On 5 Jun 2011, at 01:13, James Perkins wrote:
>
>> Hello All,
>> While working on the Maven deployment plugin we've been contemplating what
the goals should be named. Currently we have 4 goals; deploy, deploy-or-redeploy, redeploy
and undeploy.
>>
>> We kind of feel deploy-or-redeploy will be the default most people would use. It
seems a little verbose for the default. I've thought about making deploy act as the
deploy-or-redeploy,
>
> I'm for making deploy-or-redeploy the "default" - i.e. the deploy
goal.
>
>> but I'm a bit concerned that users will assume it will fail if the deployment
already exists.
>
> Something I mean to ask was why users would assume this? Because this is the way
deploy works in the AS7 deployment API?
>
>>
>> So my question to the lot of you is how would you interpret these goals and can
you think of some better names? Mainly a replacement for deploy-or-redeploy, but any other
suggestions are welcome.
>>
>> Currently as a replacement for deploy-or-redeploy we have always-deploy and
force-deploy.
>>
>> Thanks in advance,
>>
>> --
>> James R. Perkins
>> JBoss by Red Hat
>>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
9:22 a.m.
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
10:27 a.m.
I'm curious - is this maven plugin being done as a standalone thing or something
that can be used as part of Cargo (http://cargo.codehaus.org/) ?
JBoss 7 is likely the only server missing in that feature matrix on there.
Will this maven plugin have a mode that does not require a running server ?
i.e. can use the FS api with marker files ?
Or is this plugin *just* for using the deployment management API ?
/max
On Jun 6, 2011, at 16:22, James Perkins wrote:
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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
10:46 a.m.
On 06/06/2011 08:27 AM, Max Rydahl Andersen wrote:
I'm curious - is this maven plugin being done as a standalone
thing or something
that can be used as part of Cargo (http://cargo.codehaus.org/) ?
JBoss 7 is likely the only server missing in that feature matrix on there.
Will this maven plugin have a mode that does not require a running server ?
i.e. can use the FS api with marker files ?
Or is this plugin *just* for using the deployment management API ?
/max
I wasn't aware of Cargo so for now it's just standalone. It is something
we should probably look at though.
It's currently just used for deployment, so currently it does require a
running server. I'm happy to implement other functions if anyone can
think of any though :-).
On Jun 6, 2011, at 16:22, James Perkins wrote:
> 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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
--
James R. Perkins
JBoss by Red Hat
11:29 a.m.
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
3:20 p.m.
On 06/06/2011 09:29 AM, ssilvert(a)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
I like that idea. I do think we need the simple form as we do now, but
adding the ability to execute a script could be advantages. That would
especially help for the domain I'm guessing. Currently we're only
working with the standalone deployment.
Quoting James Perkins<jperkins(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
James R. Perkins
JBoss by Red Hat
6:28 p.m.
Quoting James Perkins <jperkins(a)redhat.com>:
On 06/06/2011 09:29 AM, ssilvert(a)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
I like that idea. I do think we need the simple form as we do now, but
adding the ability to execute a script could be advantages. That would
especially help for the domain I'm guessing. Currently we're only
working with the standalone deployment.
Yes, domain was what got me thinking along those lines. If you call
it "deploy" then it won't really deploy on domain unless several other
conditions are met. All it will do is upload to the content store.
But think of all the great things you could do testing-wise if you
have the ability to fully configure the server in your build. A CLI
Maven Plugin would be the Mac-Daddy mac and cheese.
> Quoting James Perkins<jperkins(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4:49 a.m.
that would require an external vm launch or are you saying CLI has API we can call ?
/max
On Jun 6, 2011, at 18:29, ssilvert(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
6:29 a.m.
Quoting Max Rydahl Andersen <max.andersen(a)redhat.com>:
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.
/max
On Jun 6, 2011, at 18:29, ssilvert(a)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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
7:15 a.m.
On 06/08/2011 01:29 PM, ssilvert(a)redhat.com wrote:
Quoting Max Rydahl Andersen<max.andersen(a)redhat.com>:
> 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/mai...
Carlo
>
> /max
>
> On Jun 6, 2011, at 18:29, ssilvert(a)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(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
7:29 a.m.
>> 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/mai...
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(a)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(a)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(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
9:29 a.m.
On 06/08/2011 01:29 PM, ssilvert(a)redhat.com wrote:
Quoting Max Rydahl Andersen<max.andersen(a)redhat.com>:
> 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.
Yes, the last one :)
Alexey
> /max
>
> On Jun 6, 2011, at 18:29, ssilvert(a)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(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
12:06 p.m.
On 6/8/11 9:29 AM, Alexey Loubyansky wrote:
On 06/08/2011 01:29 PM, ssilvert(a)redhat.com wrote:
> Quoting Max Rydahl Andersen<max.andersen(a)redhat.com>:
>
>> 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.
Yes, the last one :)
https://github.com/jbossas/jboss-as/tree/master/controller-client/src/mai...
includes convenience APIs built on top of the raw API. Let's make those
better before we think about creating another Java API.
Alexey
>> /max
>>
>> On Jun 6, 2011, at 18:29, ssilvert(a)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(a)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(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
9:24 a.m.
BTW, the CLI uses "deploy --force" to force redeploy.
On 06/06/2011 04:22 PM, James Perkins wrote:
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.
11:49 a.m.
On 06/08/2011 07:24 AM, Alexey Loubyansky wrote:
BTW, the CLI uses "deploy --force" to force redeploy.
In that case maybe we should change from strict to force and default it
to true. That way all the terminology remains the same.
On 06/06/2011 04:22 PM, James Perkins wrote:
> 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.
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
James R. Perkins
JBoss by Red Hat
12:02 p.m.
On 06/08/2011 06:49 PM, James Perkins wrote:
On 06/08/2011 07:24 AM, Alexey Loubyansky wrote:
> BTW, the CLI uses "deploy --force" to force redeploy.
In that case maybe we should change from strict to force and default it
to true. That way all the terminology remains the same.
Just FYI, in that case it will be different from the CLI in that, the
CLI deploy command will fail if the package has already been deployed
unless --force is explicitly specified.
BTW, if the package hasn't been deployed yet and --force is present,
--force is ignored.
Alexey
> On 06/06/2011 04:22 PM, James Perkins wrote:
>> 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.
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
12:25 p.m.
On 06/08/2011 10:02 AM, Alexey Loubyansky wrote:
On 06/08/2011 06:49 PM, James Perkins wrote:
> On 06/08/2011 07:24 AM, Alexey Loubyansky wrote:
>> BTW, the CLI uses "deploy --force" to force redeploy.
> In that case maybe we should change from strict to force and default it
> to true. That way all the terminology remains the same.
Just FYI, in that case it will be different from the CLI in that, the
CLI deploy command will fail if the package has already been deployed
unless --force is explicitly specified.
BTW, if the package hasn't been deployed yet and --force is present,
--force is ignored.
Alexey
It will be different in the way the defaults are set, but I think it's
what most users would prefer.
It's good to know --force will be ignored. Currently I'm using
processing a list of deployments returned to see if the deployment
already exists. I then create a deployment plan with
org.jboss.as.controller.client.helpers.standalone.DeploymentPlanBuilder.
Maybe I should look into skipping the check to see if it exists and just
use --force, if it's available to the API.
--
James R. Perkins
JBoss by Red Hat
4951
days inactive
4954
days old
20 comments
9 participants
participants (9)
-
Alexey Loubyansky -
Brian Stansberry -
Carlo de Wolf -
Dimitris Andreadis -
Heiko Braun -
James Perkins -
Max Rydahl Andersen -
Pete Muir -
ssilvert＠redhat.com