David Blevins wrote:
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
In the geronimo project we are experiencing severe problems with our
build related to plugins. Any advice on how to improve this situation
would be appreciated.
Both maven 1.0.2 and 1.1-b2 are being used to build.
We have 5 plugins that are built as part of the build and used in the
build.
David Jencks wrote:
In the geronimo project we are experiencing severe problems with our
build related to plugins. Any advice on how to improve this situation
would be appreciated.
Perhaps this is stating the obvious, but on the off chance it is useful, here
goes...
I am consistently
Bill Stoddard wrote:
David Jencks wrote:
In the geronimo project we are experiencing severe problems with our
build related to plugins. Any advice on how to improve this situation
would be appreciated.
Perhaps this is stating the obvious, but on the off chance it is useful,
here goes...
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 -
!--
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
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
groupIdgeronimo/groupId
artifactIdgeronimo-packaging-plugin/artifactId
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
