Just as an fyi, this is a nice addition but doesn't really deal with
the "Plugin hell" issue David is talking about. It seems to be hit
and miss trying to get the new plugins installed and used during any
particular maven run.
From my experience it seems as if you delete your ~/.maven/cache and
~/.maven/plugins, then the cache gets rebuilt and the latest verision
of the plugin from your ~/.maven/repository is used. But as the
plugin is updated in the future, it will never reach the ~/.maven/
cache and builds will eventually start failing because of it.
There is more too it than that, David highlighted the frustrations
around the problem a bit better in his email.
-David
On Dec 7, 2005, at 7:39 PM, Donald Woods wrote:
JIRA-1308 has been opened for this and I am creating the patch
files to attach right now.
configs/geronimo-gbean-deployer/project.xml - uncomment the following
<dependency>
<groupId>geronimo</groupId>
<artifactId>geronimo-packaging-plugin</artifactId>
<version>${geronimo_version}</version>
<type>plugin</type>
</dependency>
assemblies/j2ee-installer/project.xml - insert the following new
dependency
<dependency>
<groupId>geronimo</groupId>
<artifactId>geronimo-izpack-plugin</artifactId>
<type>plugin</type>
<version>${pom.currentVersion}</version>
</dependency>
-Donald
Bill Stoddard wrote:
Donald Woods wrote:
Finally got new4 goal to complete using Maven 1.1Beta2 (was
always failing with the same error you mention below), by editing
configs/geronimo-gbean-deployer/project.xml and removing the
comments from around the geronimo-packaging-plugin dependency to
re-enable it as a depend -
<!-- dependency on deployer -->
<dependency>
<groupId>geronimo</groupId>
<artifactId>geronimo-packaging-plugin</artifactId>
<version>${geronimo_version}</version>
<type>plugin</type>
</dependency>
I'm running a full build now via
maven m:clean new -Dmaven.test.skip=true -Dmaven.itest.skip=true
to verify the change works repeatably before I open a JIRA and
attach the patch.
-Donald
Thanks Donald, that change got me over the failure (and I'm using
maven 1.0.2). I manually placed geronimo-packaging-plugin into
the .maven/cache. Ran into another failure to statisfy a
dependency on tranql-connector-derby-embed-local-1.1-SNAPSHOT.rar
but that's probably because I was doing an offline build.
It was a bit tricky mapping this message:
[echo] Running car:install for Geronimo Configuration for
performing service deployments
to
geronimo-gbean-deployer/project.xml
I made the connection (thank you findstr/grep) but failed to
investigate the dependencies in project.xml. Won't make that
mistake again ;-)
Will clean out .maven/cache and kick off a 'maven clean new' build
this evening and report back the results.
Bill
