Headache to create plugins compatibles with both m1.0 and m1.1

[Arnaud HERITIER <ah...@gmail.com>]

Hi guys,

As you seen it, I'm working on maven 1.1 to allow us to publish it ASAP.
I'm facing to more and more problems to create plugins compatibles with 
maven 1.0 and 1.1 :
- We had a lot of problems with the xml parser.
- Today I realized that the little tag I created on the plugin-plugin works 
only with maven 1.1 because the jelly-util API is different in 1.0 and 
doesn't support to replace a String in another one.
I'm afraid to encounter more and more problems....

We lost a lot of time to create plugins compatibles with both maven releases 
(without talking about maven 2 !!) and it put back the release for maven 1.1

I would like to know your point of view about these problems. Must we focus 
on the release for maven 1.1 (and there's again a lot of work - I found a 
new blocking issue today with the mutliproject :-( ) or take the time to 
create plugins at most compatible with maven 1.0.

WDYT ?

Arnaud

Re: Headache to create plugins compatibles with both m1.0 and m1.1

[Brett Porter <br...@apache.org>]

It entirely depends on the work being done on the plugin, and how hard
it is. I thought there might have been an easier alternative for the
jelly-util problem. The XML stuff is trickier, but I think all the
plugins most affected by it are done now.

I think it is entirely reasonable to release a plugin as beta that is
1.1 only, and release it as final at the 1.1 release. But that's just my
opinion. I would not jump to that first without investigating a 1.0.2
compatible solution though - otherwise if there is a lot of differences
it could become confusing.

- Brett

Arnaud HERITIER wrote:

>Hi guys,
>
>As you seen it, I'm working on maven 1.1 to allow us to publish it ASAP.
>I'm facing to more and more problems to create plugins compatibles with 
>maven 1.0 and 1.1 :
>- We had a lot of problems with the xml parser.
>- Today I realized that the little tag I created on the plugin-plugin works 
>only with maven 1.1 because the jelly-util API is different in 1.0 and 
>doesn't support to replace a String in another one.
>I'm afraid to encounter more and more problems....
>
>We lost a lot of time to create plugins compatibles with both maven releases 
>(without talking about maven 2 !!) and it put back the release for maven 1.1
>
>I would like to know your point of view about these problems. Must we focus 
>on the release for maven 1.1 (and there's again a lot of work - I found a 
>new blocking issue today with the mutliproject :-( ) or take the time to 
>create plugins at most compatible with maven 1.0.
>
>WDYT ?
>
>Arnaud
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org