On 22 Feb 07, at 3:11 PM 22 Feb 07, David Jackman wrote:
That works great--the perfect solution for right now as I wait until
this fix is available with Maven 2.0.6.
Once in JIRA you can watch it and use a snapshot build once it's fixed.
Jason.
Thanks!
..David..
-----Original Message-----
From: Marcos Silva Pereira [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:38 AM
To: Maven Users List
Subject: Re: Mojo accessing project properties
Hello, David
Adding @requiresProject does nothing.
What about try inject the project object instead project.properties?
/**
* @parameter default-value="${project}"
* @required
* @readonly
*/
private MavenProject project;
I know that it is not a neat solution, but probably will works fine
for
you.
Interestingly, I'm getting the dependencies just fine without having
@requiresDependencyResolution
there (although in my case I don't want transitive dependencies--I
expected leaving this attribute out would only give me the direct
dependencies including inherited dependencies).
Not sure about it, but maybe it is working because dependencies were
already processed when your mojo is activated.
Kind Regards,
--
Marcos Silva Pereira
recife - pe
[EMAIL PROTECTED]
skype: marcos.silva.pereira
http://blastemica.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
