You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2010/01/01 21:32:23 UTC
Maven 3 - Compatibility Wiki - Update
Hi,
i have tested Maven 3.0-alpha-5 with the maven-buildnumber-plugin
(1.0-beta-4)....
The wiki page
http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
talks about 1.0-beta-3...
BTW: What about other plugins like
maven-pmd-plugin,
maven-cobertura-plugin (codehaus),
appassembler-maven-plugin (codehaus),
antlr3-maven-plugin (,
maven-license-plugin (google code),
maven-changes-plugin,
maven-changelog-plugin...
i can't entries for them on the page above.
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3 - Compatibility Wiki - Update
Posted by Jason van Zyl <ja...@sonatype.com>.
On 2010-01-01, at 5:43 PM, Karl Heinz Marbaise wrote:
> Hi Jason,
>
>>> Of course not...
>>>
>> But we can, and will, hook into tests that people create. Benjamin has created and improved the core set of plugin
> > ITs that we have and recently made an appeal on the Mojo
> > list to try and get people to do the same.
> Ah...interesting...
>
> > If plugin projects follow the same pattern that we have
> > for our core plugins then we can integrate those into the
> > grid and proactively find problems.
> May be i oversight something or didn't found it...is the "pattern" documented in some place ? Or do you mean the pages about "plugin-testing.html" (maven-invoker-plugin) from the maven.apache.org site area (Plugin Development)...?
>
I would look at our core plugin as examples. Look at the use of the invoker plugin as the basis in the maven-compiler-plugin. It would certainly be great to have that codified and documented. It's the practice that has emerged as the de facto standard way for testing plugins.
>> If every Maven plugin project created consistent ITs
> > it would be quite easy to spin up some EC2 instances
> > and run versions of Maven over all of them.
> > It is not outside the realm of possibility to test the
> > entire Maven ecosystem of plugins if we can get
> > the individual projects to create ITs and register
> > them somehow.
> ...
>> I think ideally we should try to register the plugin
> > projects somewhere and the grid and try to help projects
> > do the testing where necessary.
> What about starting in the wiki with a separate "Compatibility Matrix" (many plugins exist already their on the compatibility notes page) as a first pragmatic way...and see how it works...
>
Sure.
> and with that an area for registering has been created as well...whatever this will mean...
I think if we get plugins to add some metadata to artifacts deployed we can find them by scanning the repository and make a list. Would be more accurate then trying to manually maintain the information. But we can start with the wiki.
>
>
> > Someone should really be able to look at the grid and see
> > if things are working for their plugin.
>
>
> > Not sure what the best way is to get this to happen
> > but it would be cool.
> So do i, but i would suggest to start with a wiki page...
> and make it known to the dev lists on maven.apache.org and of course on codehaus as well....but based on the above mentioned i assume that the success leaves to be desired...
>
>
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
> Hauptstrasse 177 USt.IdNr: DE191347579
> 52146 Würselen http://www.soebes.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3 - Compatibility Wiki - Update
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Jason,
>> Of course not...
>>
>
> But we can, and will, hook into tests that people create.
>
> Benjamin has created and improved the core set of plugin
> ITs that we have and recently made an appeal on the Mojo
> list to try and get people to do the same.
Ah...interesting...
> If plugin projects follow the same pattern that we have
> for our core plugins then we can integrate those into the
> grid and proactively find problems.
May be i oversight something or didn't found it...is the "pattern"
documented in some place ? Or do you mean the pages about
"plugin-testing.html" (maven-invoker-plugin) from the maven.apache.org
site area (Plugin Development)...?
>
> If every Maven plugin project created consistent ITs
> it would be quite easy to spin up some EC2 instances
> and run versions of Maven over all of them.
> It is not outside the realm of possibility to test the
> entire Maven ecosystem of plugins if we can get
> the individual projects to create ITs and register
> them somehow.
>
...
> I think ideally we should try to register the plugin
> projects somewhere and the grid and try to help projects
> do the testing where necessary.
What about starting in the wiki with a separate "Compatibility Matrix"
(many plugins exist already their on the compatibility notes page) as a
first pragmatic way...and see how it works...
and with that an area for registering has been created as
well...whatever this will mean...
> Someone should really be able to look at the grid and see
> if things are working for their plugin.
> Not sure what the best way is to get this to happen
> but it would be cool.
So do i, but i would suggest to start with a wiki page...
and make it known to the dev lists on maven.apache.org and of course on
codehaus as well....but based on the above mentioned i assume that the
success leaves to be desired...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3 - Compatibility Wiki - Update
Posted by Jason van Zyl <ja...@sonatype.com>.
On 2010-01-01, at 4:16 PM, Karl Heinz Marbaise wrote:
> Hi Jason,
>
>>> but not for the following:
>>>> appassembler-maven-plugin (codehaus),
>>>> antlr3-maven-plugin (,
>> Try them, we can't be responsible for testing every Maven plugin that exists.
> Of course not...
>
But we can, and will, hook into tests that people create.
Benjamin has created and improved the core set of plugin ITs that we have and recently made an appeal on the Mojo list to try and get people to do the same. If plugin projects follow the same pattern that we have for our core plugins then we can integrate those into the grid and proactively find problems.
If every Maven plugin project created consistent ITs it would be quite easy to spin up some EC2 instances and run versions of Maven over all of them. It is not outside the realm of possibility to test the entire Maven ecosystem of plugins if we can get the individual projects to create ITs and register them somehow.
> I just want to report that the above plugin's are working well with Maven 3.0-alpha-5 ...
>
Sweet.
> So my suggestion is just to put the information into the wiki page...to enhance that page with as much as possible of information about plugins that work...to make the transit to 3.0 as smooth as possible...
>
Sure.
I think ideally we should try to register the plugin projects somewhere and the grid and try to help projects do the testing where necessary. Someone should really be able to look at the grid and see if things are working for their plugin. Not sure what the best way is to get this to happen but it would be cool.
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
> Hauptstrasse 177 USt.IdNr: DE191347579
> 52146 Würselen http://www.soebes.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3 - Compatibility Wiki - Update
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Jason,
>> but not for the following:
>>> appassembler-maven-plugin (codehaus),
>>> antlr3-maven-plugin (,
>
> Try them, we can't be responsible for testing every Maven plugin that exists.
Of course not...
I just want to report that the above plugin's are working well with
Maven 3.0-alpha-5 ...
So my suggestion is just to put the information into the wiki page...to
enhance that page with as much as possible of information about plugins
that work...to make the transit to 3.0 as smooth as possible...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3 - Compatibility Wiki - Update
Posted by Jason van Zyl <ja...@sonatype.com>.
On 2010-01-01, at 3:35 PM, Karl Heinz Marbaise wrote:
> Hi,
>
>> maven-pmd-plugin,
>> maven-cobertura-plugin (codehaus),
>> maven-license-plugin (google code),
>> maven-changes-plugin,
>> maven-changelog-plugin...
>> i can't entries for them on the page above.
>
> Ah sorry found them for a few of them...on the following page...
> http://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html
>
> but not for the following:
> > appassembler-maven-plugin (codehaus),
> > antlr3-maven-plugin (,
>
Try them, we can't be responsible for testing every Maven plugin that exists. If you find something that doesn't work, give us an example to work from and we'll fix it.
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
> Hauptstrasse 177 USt.IdNr: DE191347579
> 52146 Würselen http://www.soebes.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven 3 - Compatibility Wiki - Update
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
> maven-pmd-plugin,
> maven-cobertura-plugin (codehaus),
> maven-license-plugin (google code),
> maven-changes-plugin,
> maven-changelog-plugin...
>
> i can't entries for them on the page above.
Ah sorry found them for a few of them...on the following page...
http://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html
but not for the following:
> appassembler-maven-plugin (codehaus),
> antlr3-maven-plugin (,
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org