Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of jason@sonatype.com designates
 63.246.20.110 as permitted sender)
From: Jason van Zyl <jason@sonatype.com>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/alternative; boundary=Apple-Mail-65-834962283
Subject: Re: DefaultPluginManager.executeMojo not supported with Maven 3?
Date: Wed, 2 Jun 2010 09:08:25 -0700
In-Reply-To: 
 <398D073D88E19D44800690752F9426F10135FB934C@PSCMAIL03.bedford.progress.com>
To: "Maven Developers List" <dev@maven.apache.org>
References: 
 <398D073D88E19D44800690752F9426F10135FB934C@PSCMAIL03.bedford.progress.com>
Message-Id: <9668A6F1-D3BD-40CC-8FF2-EC0F06054B35@sonatype.com>

--Apple-Mail-65-834962283
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

No, you'll have to adjust to the new API. We are striving to be =
compatible from the CLI perspective. We'll have a new method published =
for the 3.0 release.

On Jun 2, 2010, at 8:21 AM, Jamie Townsend wrote:

> I'm trying to get http://code.google.com/p/mojo-executor/ to work with =
Maven 3, but I'm running into an UnsupportedOperationExecption coming =
from DefaultPluginManager.executeMojo.
>=20
> I've had a look at both the maven-sonar-plugin & maven-cli-plugin =
approaches to solving this issue, but as far as I can tell, those =
solutions are not backwards compatible.  Is there a backwards compatible =
way to achieve this?
>=20
> TIA,
> Jamie

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

A language that doesn=92t affect the way you think about programming is =
not worth knowing.=20
=20
 -=97 Alan Perlis


--Apple-Mail-65-834962283--