Well, since this is a jar included in the core directory of Maven 2.0.5,
I can't just reference a snapshot build from the plugin.  I would have
to tell all the developers in the company to patch the jar in their
Maven installation.  Having the plugin just use project will be easier
than trying to scale an unreleased fix, especially since the plugin
won't be able to detect an unpatched installation since having no
properties is a valid state.

..David..


-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 22, 2007 1:15 PM
To: Maven Users List
Subject: Re: Mojo accessing project properties


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]


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

Reply via email to