On 9/11/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
So you end up with a hard wired dependency on G 1.1, even
if you deploy the plugin on 1.1.1.
This means that when I install this plugin on Geronimo 1.1.1,
the server will download G 1.1 jars and include them on the classpath.
Is that the intended behavior ?
I was talking about deploying to the m2 repo, not deploying to the Geronimo
server. Sorry about the confusion.
On Sep 11, 2006, at 10:46 AM, Guillaume Nodet wrote:
> Previously, there was a etc/explicit_versions.properties file which
> was used
> somehow to give G a hint. What is the replacement mechanism using
> the m2 build ?
This file is generated for each module, adding an entry for each
dependency of the car.
So you end up with a hard wired dependency on G 1.1, even
if you deploy the plugin on 1.1.1.
This means that when I install this plugin on Geronimo 1.1.1,
the server will download G 1.1 jars and include them on the classpath.
Is that the intended behavior ?
> Also, I noticed that the car-maven-plugin (both trunk and branched
> version for
> 1.1) do not deploy the car files. It seems there is a missing goal
> in the
> lifecycle ... I will fix that.
Deployment is not handled by this plugin, but by the geronimo-
deployment-plugin, soon to be wrapped up into the geronimo-maven-plugin.
I was talking about deploying to the m2 repo, not deploying to the Geronimo
server. Sorry about the confusion.
--jason
--
Cheers,
Guillaume Nodet
