[cargo-dev] M2 / Tomcat

[Arnaud HERITIER]

Hi guys,

A user reported me that to start a local tomcat server and to deploy in it
a war We ahve to define in the m2 plugin:

<configuration>

<configuration>

<type>existing</type>

<!--

To Deploye War file , for mvn cargo:deploy

-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20</home>
</configuration>
<container>
<containerId>tomcat5x</containerId>
<!--

To Start Tomcat , for mvn cargo:start

-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20</home>
</container>
</configuration>

Is it normal that we have to define 2 times the home parameter ?

Arnaud

[Vincent Massol]

Hi Arnaud,

You can tell your user that he should read the documentation on the
web site :-)

There are 2 home parameters yes but they server different purposes:
- container home
- configuration home

That said this is not the first time someone asks (users do not read
documentation, this is a well known fact) so maybe we should change
their names in the future (Actually before we had "home" and "dir"
and I moved both to "home" to align with the Java API which uses home).

hmm... What it really means I think is that users do not get the
difference between a container and a configuration, so having
different names would probably not help.

Thanks
-Vincent

Post by Arnaud HERITIER
Hi guys,
A user reported me that to start a local tomcat server and to
<configuration>
<configuration>
<type>existing</ type>
<!--
To Deploye War file , for mvn cargo:deploy
-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20 </home>
</configuration>
<container>
<containerId>tomcat5x</ containerId>
<!--
To Start Tomcat , for mvn cargo:start
-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20 </home>
</container>
</configuration>
Is it normal that we have to define 2 times the home parameter ?
Arnaud

[Arnaud HERITIER]

I didn't find it on the web site (I just have a look quicly)
Isn't it possible in our API to use by default for the configuration home
the container home ?
Sorry, but I didn't have a look at the code since several months, thus it's
perhaps a stupid question

Arnaud

Post by Vincent Massol
Hi Arnaud,
You can tell your user that he should read the documentation on the web
site :-)
- container home
- configuration home
That said this is not the first time someone asks (users do not read
documentation, this is a well known fact) so maybe we should change their
names in the future (Actually before we had "home" and "dir" and I moved
both to "home" to align with the Java API which uses home).
hmm... What it really means I think is that users do not get the
difference between a container and a configuration, so having different
names would probably not help.
Thanks
-Vincent
Hi guys,
A user reported me that to start a local tomcat server and to deploy in
<configuration>
<configuration>
<type>existing</ type>
<!--
To Deploye War file , for mvn cargo:deploy
-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20 </home>
</configuration>
<container>
<containerId>tomcat5x</ containerId>
<!--
To Start Tomcat , for mvn cargo:start
-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20 </home>
</container>
</configuration>
Is it normal that we have to define 2 times the home parameter ?
Arnaud

[Vincent Massol]

Post by Arnaud HERITIER
I didn't find it on the web site (I just have a look quicly)

hmm.. it's here (in the reference guide):
http://cargo.codehaus.org/Maven2+plugin

I'm curious to know where you were looking so that we can improve this.

Post by Arnaud HERITIER
Isn't it possible in our API to use by default for the
configuration home the container home ?

This completely depends on the container and this would only make
sense in the case of existing configuration (for standalone config we
pick a tmp dir if none is specified).

But yes, for existing configs we could have the container
implementations pick a default location. This is a good idea. We need
a JIRA...

Post by Arnaud HERITIER
Sorry, but I didn't have a look at the code since several months,
thus it's perhaps a stupid question

It's not :)

Thanks
-Vincent

Post by Arnaud HERITIER
Hi Arnaud,
You can tell your user that he should read the documentation on the
web site :-)
- container home
- configuration home
That said this is not the first time someone asks (users do not
read documentation, this is a well known fact) so maybe we should
change their names in the future (Actually before we had "home" and
"dir" and I moved both to "home" to align with the Java API which
uses home).
hmm... What it really means I think is that users do not get the
difference between a container and a configuration, so having
different names would probably not help.
Thanks
-Vincent

Post by Arnaud HERITIER
Hi guys,
A user reported me that to start a local tomcat server and to
<configuration >
<configuration>
<type>existing </ type>
<!--
To Deploye War file , for mvn cargo:deploy
-->
<home>C:/HOMEWARE/crsdev/apps/apache- tomcat-5.5.20 </home>
</ configuration>
<container>
<containerId>tomcat5x</ containerId>
<!--
To Start Tomcat , for mvn cargo:start
-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20 </home>
</ container>
</configuration>
Is it normal that we have to define 2 times the home parameter ?
Arnaud

[Vincent Massol]

Post by Vincent Massol

Post by Arnaud HERITIER
I didn't find it on the web site (I just have a look quicly)

http://cargo.codehaus.org/Maven2+plugin

Sorry I meant http://cargo.codehaus.org/Maven2+Plugin+Reference+Guide

[snip]

-Vincent

[Arnaud HERITIER]

Post by Arnaud HERITIER
I didn't find it on the web site (I just have a look quicly)
http://cargo.codehaus.org/Maven2+plugin
I'm curious to know where you were looking so that we can improve this.

I looked at this page ;-)
And not the one you sent in your second email (I never saw that one) !


Isn't it possible in our API to use by default for the configuration home

Post by Arnaud HERITIER
the container home ?
This completely depends on the container and this would only make sense in
the case of existing configuration (for standalone config we pick a tmp dir
if none is specified).
But yes, for existing configs we could have the container implementations
pick a default location. This is a good idea. We need a JIRA...

ok, I'll feel it.

Sorry, but I didn't have a look at the code since several months, thus it's

Post by Arnaud HERITIER
perhaps a stupid question
It's not :)

;-)

Thanks

Post by Arnaud HERITIER
-Vincent

Post by Vincent Massol
Hi Arnaud,
You can tell your user that he should read the documentation on the web
site :-)
- container home
- configuration home
That said this is not the first time someone asks (users do not read
documentation, this is a well known fact) so maybe we should change their
names in the future (Actually before we had "home" and "dir" and I moved
both to "home" to align with the Java API which uses home).
hmm... What it really means I think is that users do not get the
difference between a container and a configuration, so having different
names would probably not help.
Thanks
-Vincent
Hi guys,
A user reported me that to start a local tomcat server and to deploy
<configuration >
<configuration>
<type>existing </ type>
<!--
To Deploye War file , for mvn cargo:deploy
-->
<home>C:/HOMEWARE/crsdev/apps/apache- tomcat-5.5.20 </home>
</ configuration>
<container>
<containerId>tomcat5x</ containerId>
<!--
To Start Tomcat , for mvn cargo:start
-->
<home>C:/HOMEWARE/crsdev/apps/apache-tomcat-5.5.20 </home>
</ container>
</configuration>
Is it normal that we have to define 2 times the home parameter ?
Arnaud

[Arnaud HERITIER]

...

Post by Arnaud HERITIER
But yes, for existing configs we could have the container implementations

Post by Arnaud HERITIER
pick a default location. This is a good idea. We need a JIRA...

ok, I'll feel it.

s/feel/fill ;-)
http://jira.codehaus.org/browse/CARGO-506

Arnaud


...