Inconsistent Maven behaviour

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start project in STS 3.x with Maven and GWTP APT Processing use
2. Compile usage of code
3. Maven compile with apt processing ruins it !

What is the expected output? 

When I look at my generated sources in eclipse, I expect them to match the ones 
generated by maven

Ben Ritchie@BigPC /cygdrive/c/dev/src/job-mood
$ find . -name "HeaderMessageEvent*"
./.apt_generated/com/recruitmentlink/shared/generator/session/HeaderMessageEvent
.java
./target/jobmood-0.7/WEB-INF/classes/com/recruitmentlink/shared/generator/sessio
n/HeaderMessageEvent.java

What do you see instead?

Ben Ritchie@BigPC /cygdrive/c/dev/src/job-mood
F/classes/com/recruitmentlink/shared/generator/session/HeaderMessageEvent.javasa
geEvent.java ./target/jobmood-0.7/WEB-IN
11d10
<   int fadeDelay;
12a12
>   int fadeDelay;
18,19c18
<   public HeaderMessageEvent(int fadeDelay, java.lang.String message) {
<     this.fadeDelay = fadeDelay;

---
>   public HeaderMessageEvent(java.lang.String message, int fadeDelay) {
20a20
>     this.fadeDelay = fadeDelay;
23,24c23,24
<   public static void fire(HasHandlers source, int fadeDelay, java.lang.String 
message) {
<     HeaderMessageEvent eventInstance = new HeaderMessageEvent(fadeDelay, 
message);

---
>   public static void fire(HasHandlers source, java.lang.String message, int 
fadeDelay) {
>     HeaderMessageEvent eventInstance = new HeaderMessageEvent(message, 
fadeDelay);
56,59d55
<   public int getFadeDelay(){
<     return fadeDelay;
<   }
<
63a60,63
>   public int getFadeDelay(){
>     return fadeDelay;
>   }
>
73,74d72
<     if (fadeDelay != other.fadeDelay)
<         return false;
79a78,79
>     if (fadeDelay != other.fadeDelay)
>         return false;
86d85
<     hashCode = (hashCode * 37) + new Integer(fadeDelay).hashCode();
87a87
>     hashCode = (hashCode * 37) + new Integer(fadeDelay).hashCode();
94,95d93
<                  + fadeDelay
<                  + ","
96a95,96
>                  + ","
>                  + fadeDelay

What version of the product are you using? On what operating system?

GWTP 0.6
STS 3.x

Please provide any additional information below.

My pom is attached

Original issue reported on code.google.com by be...@longshanks-consulting.com on 14 Dec 2012 at 11:53

Attachments:

• pom.xml

[GoogleCodeExporter]

Sorry for the lazy bug report ..

notice the key part of how the constructor order and fire(...) args changes 
order between the maven and the eclipse build.. any ideas? 

Original comment by be...@longshanks-consulting.com on 14 Dec 2012 at 11:55

[GoogleCodeExporter]

Ah ha I see in the javadocs now (after hours of thinking my pom must be using a 
different apt lib and that Im obviously not worthy of code generation..)

---

The order the the fields can be optionally specified using the @{@link Order}
 * annotation. If @{@link Order} is not used, then the order of the parameters to the
 * constructor and to fire() is undefined.

---

Well this is going to get me out of trouble.. !

Original comment by be...@longshanks-consulting.com on 15 Dec 2012 at 12:17