RE: plugin dependencies question
The RC will probably go out tomorrow. I planned on today, but I ran into issues with the integration tests and I had to stop and setup some CI. -Original Message- From: Eric Miles [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 8:55 PM To: Maven Users List Subject: RE: plugin dependencies question I see there's only 5 issues outstanding left for 2.0.9. Does anyone know when the expected release date is? Thanks so much! On Wed, 2008-03-12 at 19:22 -0400, Brian E. Fox wrote: > 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. 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.codehaus.org/browse/MNG-3426 and > > http://jira.codehaus.org/browse/MNG-2972 for more information. > > > > In this way you can say your 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 question > > > > 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 units are not backwards compatible). Is there a > way > > to create my plugin so that it uses FooBar for compilation, however > the > > individual projects specify which version of FooBar to the plugin via > > the pom? > > > > Thanks in advance, > > Eric Miles > > > > - > > 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] > > > - > 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]
RE: plugin dependencies question
I see there's only 5 issues outstanding left for 2.0.9. Does anyone know when the expected release date is? Thanks so much! On Wed, 2008-03-12 at 19:22 -0400, Brian E. Fox wrote: > 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. 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.codehaus.org/browse/MNG-3426 and > > http://jira.codehaus.org/browse/MNG-2972 for more information. > > > > In this way you can say your 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 question > > > > 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 units are not backwards compatible). Is there a > way > > to create my plugin so that it uses FooBar for compilation, however > the > > individual projects specify which version of FooBar to the plugin via > > the pom? > > > > Thanks in advance, > > Eric Miles > > > > - > > 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] > > > - > 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]
RE: plugin dependencies question
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. 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.codehaus.org/browse/MNG-3426 and > http://jira.codehaus.org/browse/MNG-2972 for more information. > > In this way you can say your 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 question > > 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 units are not backwards compatible). Is there a way > to create my plugin so that it uses FooBar for compilation, however the > individual projects specify which version of FooBar to the plugin via > the pom? > > Thanks in advance, > Eric Miles > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: > 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 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 question > > 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 units are not backwards compatible). Is there a way > to create my plugin so that it uses FooBar for compilation, however the > individual projects specify which version of FooBar to the plugin via > the pom? > > Thanks in advance, > Eric Miles > > - > 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]
RE: plugin dependencies question
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 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 question 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 units are not backwards compatible). Is there a way to create my plugin so that it uses FooBar for compilation, however the individual projects specify which version of FooBar to the plugin via the pom? Thanks in advance, Eric Miles - 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]
Re: plugin dependencies question
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 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, Eric Miles <[EMAIL PROTECTED]> wrote: > > 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 units are not backwards compatible). Is there a way > > to create my plugin so that it uses FooBar for compilation, however the > > individual projects specify which version of FooBar to the plugin via > > the pom? > > > > Thanks in advance, > > Eric Miles > > > > - > > 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]
Re: plugin dependencies question
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, Eric Miles <[EMAIL PROTECTED]> wrote: > 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 units are not backwards compatible). Is there a way > to create my plugin so that it uses FooBar for compilation, however the > individual projects specify which version of FooBar to the plugin via > the pom? > > Thanks in advance, > Eric Miles > > - > 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]
plugin dependencies question
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 units are not backwards compatible). Is there a way to create my plugin so that it uses FooBar for compilation, however the individual projects specify which version of FooBar to the plugin via the pom? Thanks in advance, Eric Miles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin/dependencies question
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 unable to accesss the plugin's dependency
artifacts within the mojo. I have tried a variety of APIs
without success (see below). I am using 2.0.4. How do I do it.
(The corresponding POM is below code segment.)
** fails to list ALL project level dependencies (see POM below)
Set p = project.getArtifacts();
DefaultArtifact df = (DefaultArtifact)itl.next();
df.toString();
output:
javax.xml.bind:jsr173_api:jar:1.0:compile
** lists plugins only
Set p = project.getPluginArtifacts();
DefaultArtifact df = (DefaultArtifact)itl.next();
df.toString();
output:
com.sun.tools.jxc.maven2:maven-jaxb-schemagen-plugin:maven-plugin:RELEASE:runt
ime
** Lists project level dependencies only
Set p = project.getDependencyArtifacts();
DefaultArtifact df = (DefaultArtifact)itl.next();
df.toString();
output:
javax.xml.bind:jsr173_api:jar:1.0:compile
jdk-rt:jar:0.0:system
** Lists incomplete set of project level artifacts
List p = project.getRuntimeClasspathElements();
((String)itl.next().toString()
output:
/d3/bschemagen/target/classes
/d5/maven-2.0.4/repository/javax/xml/bind/jsr173_api/1.0/jsr173_api-1.0.jar
** No access to plugin level artifact.
List p = project.getBuildPlugins();
d = (org.apache.maven.model.Dependency)itl.next();
d.getDependencies();
d.toString();
output:
{groupId=javax.activation, artifactId=activation, version=1.1, type=jar}
d.getSystemPath();
output:
null
:
javax.xml.bind
jsr173_api
1.0
local.rt
jdk-rt
0.0
system
/d5/jdk1.5.0_06/jre/lib/rt.jar
com.sun.tools.jxc.maven2
maven-jaxb-schemagen-plugin
javax.activation
activation
1.1
:
Rebecca Searls wrote:
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/dependencies are
accessable as artifacts then project/build/plugins/plugin/dependencies
would be accessable as artifacts by some means as well but
where or how?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: plugin/dependencies question
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 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/dependencies are accessable as artifacts then project/build/plugins/plugin/dependencies would be accessable as artifacts by some means as well but where or how? - 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]
plugin/dependencies question
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/dependencies are accessable as artifacts then project/build/plugins/plugin/dependencies would be accessable as artifacts by some means as well but where or how? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
