I have just tried to install a plugin compiled for G 1.1 to the latest 1.1.1-rc3 version.
After having added this version to the plugin metadata, I noticed that when installing
the plugin, Geronimo downloaded all the referenced G 1.1 jars.

So, trying to find a hack, I added these dependencies explicitely inside my
plan.xml file, not specifying the version.  The result is that jars are put twice
in the processed plan, the first time without any version, and a second time
with an explicit 1.1 version.

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 ?

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.

--
Cheers,
Guillaume Nodet

Reply via email to