You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Orjan Austvold <au...@colibria.com> on 2005/09/23 22:01:00 UTC
dependency resolution only before compile phase?
I noticed that the artifacts attribute of my plugin configured with
parameter expression="${project.artifacts}
did not get initialized with current project dependencies when the
plugin ran in the process-resource phase.
When run in the compile phase it got initalized with the expected result.
Is this an inteded behaviour?
Ørjan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency resolution only before compile phase?
Posted by Brett Porter <br...@gmail.com>.
That's correct: process-resources is a phase (a part of the build
lifecycle), not a scope (a category of dependency). While the scopes
bear names resembling phases, they are not the same thing.
Did you have a problem using the tag?
Regards,
Brett
On 9/24/05, Orjan Austvold <au...@colibria.com> wrote:
> The documentation for the @requiresDependencyResolution descriptor
> element states that it only works for compile, runtime and test scopes,
> not for the process-resources phase.
>
> http://maven.apache.org/maven2/developers/mojo-api-specification.html
>
> Maybe the docs are outdated then.
>
>
> Ørjan
>
>
> Brett Porter wrote:
> > Yes, you should add @requiresDependencyResolution to your tags.
> >
> > On 9/24/05, Orjan Austvold <au...@colibria.com> wrote:
> >
> >>I noticed that the artifacts attribute of my plugin configured with
> >>
> >>parameter expression="${project.artifacts}
> >>
> >>did not get initialized with current project dependencies when the
> >>plugin ran in the process-resource phase.
> >>
> >>When run in the compile phase it got initalized with the expected result.
> >>
> >>Is this an inteded behaviour?
> >>
> >>
> >>Ørjan
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> --
> Ørjan Austvold - Senior Software Architect
> www.colibria.com - putting the presence into messaging
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency resolution only before compile phase?
Posted by Orjan Austvold <au...@colibria.com>.
The documentation for the @requiresDependencyResolution descriptor
element states that it only works for compile, runtime and test scopes,
not for the process-resources phase.
http://maven.apache.org/maven2/developers/mojo-api-specification.html
Maybe the docs are outdated then.
Ørjan
Brett Porter wrote:
> Yes, you should add @requiresDependencyResolution to your tags.
>
> On 9/24/05, Orjan Austvold <au...@colibria.com> wrote:
>
>>I noticed that the artifacts attribute of my plugin configured with
>>
>>parameter expression="${project.artifacts}
>>
>>did not get initialized with current project dependencies when the
>>plugin ran in the process-resource phase.
>>
>>When run in the compile phase it got initalized with the expected result.
>>
>>Is this an inteded behaviour?
>>
>>
>>Ørjan
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Ørjan Austvold - Senior Software Architect
www.colibria.com - putting the presence into messaging
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency resolution only before compile phase?
Posted by Brett Porter <br...@gmail.com>.
Yes, you should add @requiresDependencyResolution to your tags.
On 9/24/05, Orjan Austvold <au...@colibria.com> wrote:
> I noticed that the artifacts attribute of my plugin configured with
>
> parameter expression="${project.artifacts}
>
> did not get initialized with current project dependencies when the
> plugin ran in the process-resource phase.
>
> When run in the compile phase it got initalized with the expected result.
>
> Is this an inteded behaviour?
>
>
> Ørjan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org