RE: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8

2007-12-11 Thread William Hoover
Done: http://jira.codehaus.org/browse/PLX-358 complete w/sample project.

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10, 2007 4:49 PM
To: Maven Users List
Subject: Re: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8


Zip up a small sample project, create a JIRA issue, and attach it.
Then someone can look at your issue more closely.

Wayne

On 12/10/07, William Hoover [EMAIL PROTECTED] wrote:
 No takers?

 -Original Message-
 From: William Hoover [mailto:[EMAIL PROTECTED]
 Sent: Saturday, December 08, 2007 8:13 PM
 To: users@maven.apache.org
 Subject: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8


 I am using JDK 1.5 / Maven 2.0.8 and am attempting mvn clean install on a 
 simple project that contains the following snippet:

 ...

 public final Class? extends Enum? extends IDTOPhase 
 getDTOPhaseLifeCycleStrategy(){
return someEnumClass;
 }

 ...

 for(java.lang.Enum? extends IDTOPhase phase : 
 getDTOPhaseLifeCycleStrategy().getEnumConstants()){
...
 }

 ...

 The problem is that this compiles w/o a problem using ANT (or Eclipse build), 
 but fails using Maven. I get the error:

 ... incompatible types
 found : java.lang.Enum? extends IDTOPhase
 required : java.lang.Enum? extends IDTOPhase

 I even set the maven-compiler-plugin to ensure compilation in 1.5

 plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
 /plugin

 Any clue??? Thanks!


 -
 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: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8

2007-12-11 Thread Wayne Fay
I played with your sample a bit and wrote a lengthy response in JIRA.

I am reasonably convinced this is simply an example where Eclipse's
JDT compiler is doing something extra that allows your code to work,
but it really doesn't. You can't always trust Eclipse, as it does not
dispatch to your system's JDK for compiling like Maven does (as far as
I understand what is happening under the hood in Eclipse and Maven).

Wayne

On 12/11/07, William Hoover [EMAIL PROTECTED] wrote:
 Done: http://jira.codehaus.org/browse/PLX-358 complete w/sample project.

 -Original Message-
 From: Wayne Fay [mailto:[EMAIL PROTECTED]
 Sent: Monday, December 10, 2007 4:49 PM
 To: Maven Users List
 Subject: Re: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8


 Zip up a small sample project, create a JIRA issue, and attach it.
 Then someone can look at your issue more closely.

 Wayne

 On 12/10/07, William Hoover [EMAIL PROTECTED] wrote:
  No takers?
 
  -Original Message-
  From: William Hoover [mailto:[EMAIL PROTECTED]
  Sent: Saturday, December 08, 2007 8:13 PM
  To: users@maven.apache.org
  Subject: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8
 
 
  I am using JDK 1.5 / Maven 2.0.8 and am attempting mvn clean install on a 
  simple project that contains the following snippet:
 
  ...
 
  public final Class? extends Enum? extends IDTOPhase 
  getDTOPhaseLifeCycleStrategy(){
 return someEnumClass;
  }
 
  ...
 
  for(java.lang.Enum? extends IDTOPhase phase : 
  getDTOPhaseLifeCycleStrategy().getEnumConstants()){
 ...
  }
 
  ...
 
  The problem is that this compiles w/o a problem using ANT (or Eclipse 
  build), but fails using Maven. I get the error:
 
  ... incompatible types
  found : java.lang.Enum? extends IDTOPhase
  required : java.lang.Enum? extends IDTOPhase
 
  I even set the maven-compiler-plugin to ensure compilation in 1.5
 
  plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-compiler-plugin/artifactId
 version2.0.2/version
 configuration
 source1.5/source
 target1.5/target
 /configuration
  /plugin
 
  Any clue??? Thanks!
 
 
  -
  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: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8

2007-12-11 Thread Kallin Nagelberg
To verify this you should try switching Eclipse to use your installed JDK
compiler instead of the built in one.

William also mentioned that ANT was producing successful builds as well, so
unless ANT also uses it's own compiler it might be another issue..

On Dec 11, 2007 11:29 AM, Wayne Fay [EMAIL PROTECTED] wrote:

 I played with your sample a bit and wrote a lengthy response in JIRA.

 I am reasonably convinced this is simply an example where Eclipse's
 JDT compiler is doing something extra that allows your code to work,
 but it really doesn't. You can't always trust Eclipse, as it does not
 dispatch to your system's JDK for compiling like Maven does (as far as
 I understand what is happening under the hood in Eclipse and Maven).

 Wayne

 On 12/11/07, William Hoover [EMAIL PROTECTED] wrote:
  Done: http://jira.codehaus.org/browse/PLX-358 complete w/sample project.
 
  -Original Message-
  From: Wayne Fay [mailto:[EMAIL PROTECTED]
  Sent: Monday, December 10, 2007 4:49 PM
  To: Maven Users List
  Subject: Re: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8
 
 
  Zip up a small sample project, create a JIRA issue, and attach it.
  Then someone can look at your issue more closely.
 
  Wayne
 
  On 12/10/07, William Hoover [EMAIL PROTECTED] wrote:
   No takers?
  
   -Original Message-
   From: William Hoover [mailto:[EMAIL PROTECTED]
   Sent: Saturday, December 08, 2007 8:13 PM
   To: users@maven.apache.org
   Subject: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8
  
  
   I am using JDK 1.5 / Maven 2.0.8 and am attempting mvn clean install
 on a simple project that contains the following snippet:
  
   ...
  
   public final Class? extends Enum? extends IDTOPhase
 getDTOPhaseLifeCycleStrategy(){
  return someEnumClass;
   }
  
   ...
  
   for(java.lang.Enum? extends IDTOPhase phase :
 getDTOPhaseLifeCycleStrategy().getEnumConstants()){
  ...
   }
  
   ...
  
   The problem is that this compiles w/o a problem using ANT (or Eclipse
 build), but fails using Maven. I get the error:
  
   ... incompatible types
   found : java.lang.Enum? extends IDTOPhase
   required : java.lang.Enum? extends IDTOPhase
  
   I even set the maven-compiler-plugin to ensure compilation in 1.5
  
   plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-compiler-plugin/artifactId
  version2.0.2/version
  configuration
  source1.5/source
  target1.5/target
  /configuration
   /plugin
  
   Any clue??? Thanks!
  
  
   -
   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: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8

2007-12-10 Thread William Hoover
No takers?

-Original Message-
From: William Hoover [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 08, 2007 8:13 PM
To: users@maven.apache.org
Subject: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8


I am using JDK 1.5 / Maven 2.0.8 and am attempting mvn clean install on a 
simple project that contains the following snippet:

...

public final Class? extends Enum? extends IDTOPhase 
getDTOPhaseLifeCycleStrategy(){
return someEnumClass;
}

...

for(java.lang.Enum? extends IDTOPhase phase : 
getDTOPhaseLifeCycleStrategy().getEnumConstants()){
...
}

...

The problem is that this compiles w/o a problem using ANT (or Eclipse build), 
but fails using Maven. I get the error:

... incompatible types
found : java.lang.Enum? extends IDTOPhase
required : java.lang.Enum? extends IDTOPhase

I even set the maven-compiler-plugin to ensure compilation in 1.5

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin

Any clue??? Thanks!


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8

2007-12-10 Thread Wayne Fay
Zip up a small sample project, create a JIRA issue, and attach it.
Then someone can look at your issue more closely.

Wayne

On 12/10/07, William Hoover [EMAIL PROTECTED] wrote:
 No takers?

 -Original Message-
 From: William Hoover [mailto:[EMAIL PROTECTED]
 Sent: Saturday, December 08, 2007 8:13 PM
 To: users@maven.apache.org
 Subject: JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8


 I am using JDK 1.5 / Maven 2.0.8 and am attempting mvn clean install on a 
 simple project that contains the following snippet:

 ...

 public final Class? extends Enum? extends IDTOPhase 
 getDTOPhaseLifeCycleStrategy(){
return someEnumClass;
 }

 ...

 for(java.lang.Enum? extends IDTOPhase phase : 
 getDTOPhaseLifeCycleStrategy().getEnumConstants()){
...
 }

 ...

 The problem is that this compiles w/o a problem using ANT (or Eclipse build), 
 but fails using Maven. I get the error:

 ... incompatible types
 found : java.lang.Enum? extends IDTOPhase
 required : java.lang.Enum? extends IDTOPhase

 I even set the maven-compiler-plugin to ensure compilation in 1.5

 plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
 /plugin

 Any clue??? Thanks!


 -
 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]