ailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 12, 2008 7:18 PM
> To: Maven Users List
> Subject: Re: plugin dependencies question
>
> That's new in 2.0.9. Well, not new, but now it works. ;-)
>
> Wayne
>
> On 3/12/08, Brian E. Fox <[EMAIL PROTECTED]> wr
ED]
> Sent: Wednesday, March 12, 2008 7:18 PM
> To: Maven Users List
> Subject: Re: plugin dependencies question
>
> That's new in 2.0.9. Well, not new, but now it works. ;-)
>
> Wayne
>
> On 3/12/08, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> &g
Handy, isn't it?
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2008 7:18 PM
To: Maven Users List
Subject: Re: plugin dependencies question
That's new in 2.0.9. Well, not new, but now it works. ;-)
Wayne
On 3/12/08, Brian E. F
That's new in 2.0.9. Well, not new, but now it works. ;-)
Wayne
On 3/12/08, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Yes. Compile against foobar normally. The users can specify the
> dependency they want in the plugin configuration block. This is working
> in 2.0.9, you can see http://jira.codeh
Yes. Compile against foobar normally. The users can specify the
dependency they want in the plugin configuration block. This is working
in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and
http://jira.codehaus.org/browse/MNG-2972 for more information.
In this way you can say your plu
Alternatively, write your plugin such that it can use any version 1.1
through 1.8 and specify the version with a configuration element. Your
plugin will need a bit more intelligence to pull this off.
Wayne
On 3/12/08, Wayne Fay <[EMAIL PROTECTED]> wrote:
> One immediate thought: make a version of
One immediate thought: make a version of your plugin that corresponds
with each version of FooBar.
FooBar 1.1 => foobar-maven-plugin v1.1.0 (bug fixes will bump the .0)
FooBar 1.2 => foobar-maven-plugin v1.2.0
etc
Then in your pom, lock down the foobar-m-p version with
[1.2].
Wayne
On 3/12/08,
Here is the issue I am trying to resolve.
I am developing a plugin. (It runs only in phase
generate-sources.) The underlaying code requires
knowledge of any user specified JAR files in order
to process java files. The user specified dependencies
should be plugin specific.
To date I have been
Hi Rebecca,
Please refer to http://maven.apache.org/pom.html for details about this.
I think there's a brief explanation there (Build Settings --> The
BaseBuild Element Set --> Plugins)
about the difference of those two elements :-)
Hope this helps!
Thanks,
Deng
Rebecca Searls wrote:
What
