Bug in Maven EAR plugin version 2.4

[André Duursma]

Hi,

I came across what I think is a bug in the EAR plugin (version 2.4). Since I
am not a registered contributor I cannot file this bug in JIRA myself, but I
felt I want to share this with you anyway and perhaps, after verification,
you can decide whether or not you will create the issue.

What happens is this. Using version 2.4 the "description" element in the
generated application.xml file is the *second* element, instead of the *
first* element, which causes a schema violation. I have tested this
behaviour with some earlier versions and they all generate the
application.xml file correctly. So to me it looks like a regression issue
where the "description" and "display-name" elements have switched places.


Cheers,

André Duursma

Agility IT Services
Trimbeets 12
8401 XC Gorredijk
The Netherlands

[phone]
[phone]
andre@...
http://www.agility-it-services.nl

[snicoll]

Hi André,

Thanks for the notification. You can freely create an account on
jira.codehaus.org and you will have access. I am bit surprised about the
regression because the only thing we changed is JavaEE6 support but I'll
double check if some regression was not introduced.

Thanks,
Stéphane

On Sat, Oct 31, 2009 at 1:16 PM, André Duursma <andre@...
> wrote:

> Hi,
>
> I came across what I think is a bug in the EAR plugin (version 2.4). Since
> I
> am not a registered contributor I cannot file this bug in JIRA myself, but
> I
> felt I want to share this with you anyway and perhaps, after verification,
> you can decide whether or not you will create the issue.
>
> What happens is this. Using version 2.4 the "description" element in the
> generated application.xml file is the *second* element, instead of the *
> first* element, which causes a schema violation. I have tested this
> behaviour with some earlier versions and they all generate the
> application.xml file correctly. So to me it looks like a regression issue
> where the "description" and "display-name" elements have switched places.
>
>
> Cheers,
>
> André Duursma
>
> Agility IT Services
> Trimbeets 12
> 8401 XC Gorredijk
> The Netherlands
>
> [phone]
> [phone]
> andre@...
> http://www.agility-it-services.nl
>

--
Large Systems Suck: This rule is 100% transitive. If you build one, you
suck" -- S.Yegge

[Milos Kleint-2]

a sample project demonstrating the problem is essential here. I've tried to
reproduce but always ended up with the display name being first.

Thanks

Milos

On Tue, Nov 3, 2009 at 2:10 PM, Stephane Nicoll
<stephane.nicoll@...>wrote:

> Hi André,
>
> Thanks for the notification. You can freely create an account on
> jira.codehaus.org and you will have access. I am bit surprised about the
> regression because the only thing we changed is JavaEE6 support but I'll
> double check if some regression was not introduced.
>
> Thanks,
> Stéphane
>
> On Sat, Oct 31, 2009 at 1:16 PM, André Duursma <
> andre@...
> > wrote:
>
> > Hi,
> >
> > I came across what I think is a bug in the EAR plugin (version 2.4).
> Since
> > I
> > am not a registered contributor I cannot file this bug in JIRA myself,
> but
> > I
> > felt I want to share this with you anyway and perhaps, after
> verification,
> > you can decide whether or not you will create the issue.
> >
> > What happens is this. Using version 2.4 the "description" element in the
> > generated application.xml file is the *second* element, instead of the *
> > first* element, which causes a schema violation. I have tested this
> > behaviour with some earlier versions and they all generate the
> > application.xml file correctly. So to me it looks like a regression issue
> > where the "description" and "display-name" elements have switched places.
> >
> >
> > Cheers,
> >
> > André Duursma
> >
> > Agility IT Services
> > Trimbeets 12
> > 8401 XC Gorredijk
> > The Netherlands
> >
> > [phone]
> > [phone]
> > andre@...
> > http://www.agility-it-services.nl
> >
>
>
>
> --
> Large Systems Suck: This rule is 100% transitive. If you build one, you
> suck" -- S.Yegge
>

[Jörg Schaible-2]

Stephane Nicoll wrote at Dienstag, 3. November 2009 14:10:

> Hi André,
>
> Thanks for the notification. You can freely create an account on
> jira.codehaus.org and you will have access. I am bit surprised about the
> regression because the only thing we changed is JavaEE6 support but I'll
> double check if some regression was not introduced.

Please check also HashMap vs. LinkedHashMap. With Java 5 typically the
(undefined) order of the HashMap changes because of internal modifications
of the algorithm.

- Jörg


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

[snicoll]

We are not using that there as far as I know but I'll check anyway

Thx

Sent from my iPhone

On 03 Nov 2009, at 15:49, Jörg Schaible <joerg.schaible@...> wrote:

> Stephane Nicoll wrote at Dienstag, 3. November 2009 14:10:
>
>> Hi André,
>>
>> Thanks for the notification. You can freely create an account on
>> jira.codehaus.org and you will have access. I am bit surprised  
>> about the
>> regression because the only thing we changed is JavaEE6 support but  
>> I'll
>> double check if some regression was not introduced.
>
> Please check also HashMap vs. LinkedHashMap. With Java 5 typically the
> (undefined) order of the HashMap changes because of internal  
> modifications
> of the algorithm.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

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