Hi Nicolas,
I'm still investigating this approach. Personally I'm not so sure about
the following statement of yours:
> In fact it his an elegant solution as you can produce one artifact per
> ear (it is the maven politic too) for each server kind/environement.
> The specific goes in application
Hi Nicolas,
I'm still investigating this approach. Personally I'm not so sure about
the following statement of yours:
> In fact it his an elegant solution as you can produce one artifact per
> ear (it is the maven politic too) for each server kind/environement.
> The specific goes in application
> -Original Message-
> From: Nicolas Chalumeau [mailto:[EMAIL PROTECTED]
> Sent: jeudi 31 mars 2005 14:16
> To: Maven Users List; [EMAIL PROTECTED]
> Subject: Re: Targeting multiple appservers
>
> I imagine you can ask Vincent if there was evolution since 2003 (he
&
I imagine you can ask Vincent if there was evolution since 2003 (he
read this list so he can aswer...)
In fact it his an elegant solution as you can produce one artifact per
ear (it is the maven politic too) for each server kind/environement.
The specific goes in application and you reuse module (
Thanks Nicolas! I imagined this easier than that, taken into
consideration that the article dated from 2003 I hoped that something
orthogonal to projects had been introduced to manage portability...
Georg
Nicolas Chalumeau wrote:
One good this is to have in-container tests : look at cactus
(jaka
One good this is to have in-container tests : look at cactus
(jakarat.apache.org/cactus), it allow you to run the test in multiple
server.
A great pdf talk about a possible structuration (it's not the "unique"
one) : http://www.pivolis.com/pdf/J2EE_projects_Maven_V1.1.pdf
Nicolas,
On Wed, 30 Mar
