There is no MavenProject parameter in this mojo. The only parameter used is basedir. If requiresProject is set to true wouldn't that mean that the mojo would fail the first time around, when there is no pom.xml file?

Kenney Westerhof wrote:
On Thu, 25 May 2006, Dennis Lundberg wrote:

If you have a parameter of type MavenProject the requiresProject
is automatically set to true, so remove any MavenProject parameters
from the mojo.

I'm not sure that the pom will be ignored, though.

-- Kenney

Kenney Westerhof wrote:
On Thu, 25 May 2006, Dennis Lundberg wrote:
<snip>

I couldn't find a JIRA-project for either M2-sandbox or
M2-sandbox-plugins. Some of the plugins in the sandbox have their own
JIRA-project set up, but most of them haven't. Where should I should
attach my patches? Should I put them on MONE or MNG or ...
There's a component 'Sandbox' in the MNG project where you can attach your
patches for maven-maven1-plugin.
Thanks! The first patch is in MNG-2320.

I'm working on the second one now and have stumbled upon a small
problem. The plugin has been changed to use maven-model-converter
instead of the bundled class. The new converter is better that the
bundled one, in that it converts an M1 plugin entry into an M2
build/plugin entry.

The first time around the conversion works fine. On the second run the
conversion can fail. The project.xml file [1] that I am using for
testing uses the maven-cobertura-plugin. This is an M1 only plugin.
There is a M2 version, but that one is over at mojo and is called
cobertura-maven-plugin.

When the maven-maven1-plugin is run and there is a pom.xml in the same
folder it downloads the M1 pom for maven-cobertura-plugin and puts it in
my local M2 repo. This leads to a build error before maven-maven1-plugin
has even started working. See stack trace below.

Is there any way to make a mojo or plugin force Maven core to not do
anything with any existing pom.xml? The convert mojo in
maven-maven1-plugin has set
   @goal convert
   @requiresProject false

I also tried to add
   @phase validate
to make it jump in as early as possible in the life cycle, but that
didn't work.


[1]http://svn.apache.org/viewvc/jakarta/commons/proper/collections/trunk/project.xml?content-type=text%2Fplain&view=co

<snip>


--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to