I have exchanged some emails and chatted with Felipe. It appears that the
Maven EAR plugin v1.6.1 or greater is required for the cactifyear goal of
the Maven plugin for Cactus. However, Maven 1.0.2 bundles version 1.6 only
of the EAR plugin.
This is because the Cactus plugin uses the <ear:setPath> tag which has been
fixed by MPEAR-31 ("Fixed path of bundled dependency on generated
<code>application.xml</code>") in version 1.6.1.
Felipe, I see 2 solutions:
1/ Why do we need to use the ear.bundle.dir/ear.bundle.name properties in
our plugin tests? It seems these are the properties causing the problem and
I don't see why they are required for testing our cactifyear goal. Is it
possible to change the test to remove the issue altogether?
2/ If it's not possible (but I would really like to be sure it's not) then
we need to add a check in plugin.jelly to verify that the version of the ear
plugin used is greater or equal to 1.6.1. I'd rather we remove complexity
instead of adding it as much as possible though...
Can we do 1/?
Thanks
-Vincent
> -----Original Message-----
> From: Felipe Leme [mailto:[EMAIL PROTECTED]
> Sent: lundi 25 avril 2005 18:15
> To: Cactus Developers List
> Subject: RE: Problem in maven plugin tests?
>
> Vincent,
>
> Any progress in this front?
>
> -- Felipe
>
>
> On Mon, 2005-04-25 at 08:28 -0300, Felipe Leme wrote:
>
> > Could you please check where the file was bundled in the EAR? It might
> > be an error in the test case itself, due to different path separators on
> > windows/linux...
>
> --
> Felipe Leme <[EMAIL PROTECTED]>
> Falcon Informática
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
