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
t;
> -Original Message-
> From: Eric Miles [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 12, 2008 4:24 PM
> To: users@maven.apache.org
> Subject: plugin dependencies question
>
> All,
>
> I have a plugin I wrote, that use framework FooBar. This plugin will
&
plugin will use FooBar version x.y by
default, but if they want to use another one, they can do so by
overriding it in their pom.
-Original Message-
From: Eric Miles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2008 4:24 PM
To: users@maven.apache.org
Subject: plugin dependencies
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,
All,
I have a plugin I wrote, that use framework FooBar. This plugin will
work with FooBar version 1.1 through 1.8. I have numerous maven
projects that use my plugin and all use different versions of FooBar.
The version of FooBar is important to each project as compilation is
performed (compiled
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
What is the intended use of project/build/plugins/plugin/dependencies
as compared to project/dependencies?
One would assume project/build/plugins/plugin/dependencies
are plugin specific in scope; that project/dependencies are
active project wide in scope.
And one would expect that if project/dep
11 matches
Mail list logo
