[m2]Compilation error when using maven version 2.0-alpha-2

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[m2]Compilation error when using maven version 2.0-alpha-2

Zachi Hazan
I have just upgraded mvaen 2 to version alpha 2.
When running compiler:compile plugin the an exception is thrown (see below).
I have checked in maven sources and I saw that the method "compile"
exists only on the new plexus jar, which was upgraded  after alpha 2
realesed.

How can I solve this problem?

[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
        at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
        at
org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
        at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
Caused by: java.lang.NoSuchMethodException: compile
        at java.lang.Class.getMethod0(Class.java:1742)
        at java.lang.Class.getMethod(Class.java:951)
        at
org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
        at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
        ... 14 more



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [m2]Compilation error when using maven version 2.0-alpha-2

Brett Porter
Have you hard coded the 2.0-alpha-1 plugin version for
maven-compiler-plugin in your POM?

- Brett

On 6/5/05, Zachi Hazan <[hidden email]> wrote:

> I have just upgraded mvaen 2 to version alpha 2.
> When running compiler:compile plugin the an exception is thrown (see below).
> I have checked in maven sources and I saw that the method "compile"
> exists only on the new plexus jar, which was upgraded  after alpha 2
> realesed.
>
> How can I solve this problem?
>
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
>         at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
>         at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
>         at
> org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
>         at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
> Caused by: java.lang.NoSuchMethodException: compile
>         at java.lang.Class.getMethod0(Class.java:1742)
>         at java.lang.Class.getMethod(Class.java:951)
>         at
> org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
>         at
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
>         ... 14 more
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [m2]Compilation error when using maven version 2.0-alpha-2

Zachi Hazan
No, only defined the plugin artifactid and group id
   <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
      </plugin>
       ....

Brett Porter wrote:

>Have you hard coded the 2.0-alpha-1 plugin version for
>maven-compiler-plugin in your POM?
>
>- Brett
>
>On 6/5/05, Zachi Hazan <[hidden email]> wrote:
>  
>
>>I have just upgraded mvaen 2 to version alpha 2.
>>When running compiler:compile plugin the an exception is thrown (see below).
>>I have checked in maven sources and I saw that the method "compile"
>>exists only on the new plexus jar, which was upgraded  after alpha 2
>>realesed.
>>
>>How can I solve this problem?
>>
>>[ERROR] Cause:
>>org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
>>        at
>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
>>        at
>>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
>>        at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
>>        at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
>>        at
>>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
>>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>        at
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>        at
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>        at java.lang.reflect.Method.invoke(Method.java:324)
>>        at
>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
>>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
>>        at
>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
>>        at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
>>Caused by: java.lang.NoSuchMethodException: compile
>>        at java.lang.Class.getMethod0(Class.java:1742)
>>        at java.lang.Class.getMethod(Class.java:951)
>>        at
>>org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
>>        at
>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
>>        ... 14 more
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail: [hidden email]
>>
>>
>>    
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [m2]Compilation error when using maven version 2.0-alpha-2

Brett Porter
Ok, on closer inspection - it looks like your JDK doesn't support the
sun standard interface to Javac.

What JDK are you using, and what is JAVA_HOME set to?

Thanks,
Brett

On 6/6/05, Zachi Hazan <[hidden email]> wrote:

> No, only defined the plugin artifactid and group id
>    <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-compiler-plugin</artifactId>
>       </plugin>
>        ....
>
> Brett Porter wrote:
>
> >Have you hard coded the 2.0-alpha-1 plugin version for
> >maven-compiler-plugin in your POM?
> >
> >- Brett
> >
> >On 6/5/05, Zachi Hazan <[hidden email]> wrote:
> >
> >
> >>I have just upgraded mvaen 2 to version alpha 2.
> >>When running compiler:compile plugin the an exception is thrown (see below).
> >>I have checked in maven sources and I saw that the method "compile"
> >>exists only on the new plexus jar, which was upgraded  after alpha 2
> >>realesed.
> >>
> >>How can I solve this problem?
> >>
> >>[ERROR] Cause:
> >>org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
> >>        at
> >>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
> >>        at
> >>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> >>        at
> >>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
> >>        at
> >>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
> >>        at
> >>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
> >>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
> >>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>        at
> >>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>        at
> >>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>        at java.lang.reflect.Method.invoke(Method.java:324)
> >>        at
> >>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
> >>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
> >>        at
> >>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
> >>        at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
> >>Caused by: java.lang.NoSuchMethodException: compile
> >>        at java.lang.Class.getMethod0(Class.java:1742)
> >>        at java.lang.Class.getMethod(Class.java:951)
> >>        at
> >>org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
> >>        at
> >>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
> >>        ... 14 more
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [hidden email]
> >>For additional commands, e-mail: [hidden email]
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [hidden email]
> >For additional commands, e-mail: [hidden email]
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [m2]Compilation error when using maven version 2.0-alpha-2

Zachi Hazan
Thanks for the quick response.
I am using JDK version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)

My java home is set to "/sun/jdk/x86/linux/".
I am working with this jdk in other projects.

I saw in maven svn that this "compile" was added immediately after alpha
2 release to plexsus.
Can it be that there is matching problems between maven 2.0-alpha-2 and
plexsus jars?

Brett Porter wrote:

>Ok, on closer inspection - it looks like your JDK doesn't support the
>sun standard interface to Javac.
>
>What JDK are you using, and what is JAVA_HOME set to?
>
>Thanks,
>Brett
>
>On 6/6/05, Zachi Hazan <[hidden email]> wrote:
>  
>
>>No, only defined the plugin artifactid and group id
>>   <plugins>
>>      <plugin>
>>        <groupId>org.apache.maven.plugins</groupId>
>>        <artifactId>maven-compiler-plugin</artifactId>
>>      </plugin>
>>       ....
>>
>>Brett Porter wrote:
>>
>>    
>>
>>>Have you hard coded the 2.0-alpha-1 plugin version for
>>>maven-compiler-plugin in your POM?
>>>
>>>- Brett
>>>
>>>On 6/5/05, Zachi Hazan <[hidden email]> wrote:
>>>
>>>
>>>      
>>>
>>>>I have just upgraded mvaen 2 to version alpha 2.
>>>>When running compiler:compile plugin the an exception is thrown (see below).
>>>>I have checked in maven sources and I saw that the method "compile"
>>>>exists only on the new plexus jar, which was upgraded  after alpha 2
>>>>realesed.
>>>>
>>>>How can I solve this problem?
>>>>
>>>>[ERROR] Cause:
>>>>org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
>>>>       at
>>>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
>>>>       at
>>>>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
>>>>       at
>>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
>>>>       at
>>>>u using, and what is JAVA_HOME set to?
>>>>
>>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
>>>>       at
>>>>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
>>>>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
>>>>       at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
>>>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>       at
>>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>       at
>>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>       at java.lang.reflect.Method.invoke(Method.java:324)
>>>>       at
>>>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
>>>>       at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
>>>>       at
>>>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
>>>>       at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
>>>>Caused by: java.lang.NoSuchMethodException: compile
>>>>       at java.lang.Class.getMethod0(Class.java:1742)
>>>>       at java.lang.Class.getMethod(Class.java:951)
>>>>       at
>>>>org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
>>>>       at
>>>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
>>>>       ... 14 more
>>>>
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: [hidden email]
>>>>For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [hidden email]
>>>For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail: [hidden email]
>>
>>
>>    
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [m2]Compilation error when using maven version 2.0-alpha-2

Brett Porter
Yes, the compiler was changed in the last release to bettter support JDK 5.

This is a bit strange. The programmatic interface we are using was
only declared in JDK 5.0's documentation, but it has been tested on
1.4.2.

It works for me on 1.4.2_08, on Windows.

Is there a way you can discover what methods com.sun.tools.javac.Main
has on your JDK, through the IDE perhaps? You could also try upgrading
to _08, but I don't see anything in the release notes indicating it
has changed.

What specific JDK do you have installed? Is it the one from Sun?

- Brett

On 6/6/05, Zachi Hazan <[hidden email]> wrote:

> Thanks for the quick response.
> I am using JDK version
> java version "1.4.2_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
> Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
>
> My java home is set to "/sun/jdk/x86/linux/".
> I am working with this jdk in other projects.
>
> I saw in maven svn that this "compile" was added immediately after alpha
> 2 release to plexsus.
> Can it be that there is matching problems between maven 2.0-alpha-2 and
> plexsus jars?
>
> Brett Porter wrote:
>
> >Ok, on closer inspection - it looks like your JDK doesn't support the
> >sun standard interface to Javac.
> >
> >What JDK are you using, and what is JAVA_HOME set to?
> >
> >Thanks,
> >Brett
> >
> >On 6/6/05, Zachi Hazan <[hidden email]> wrote:
> >
> >
> >>No, only defined the plugin artifactid and group id
> >>   <plugins>
> >>      <plugin>
> >>        <groupId>org.apache.maven.plugins</groupId>
> >>        <artifactId>maven-compiler-plugin</artifactId>
> >>      </plugin>
> >>       ....
> >>
> >>Brett Porter wrote:
> >>
> >>
> >>
> >>>Have you hard coded the 2.0-alpha-1 plugin version for
> >>>maven-compiler-plugin in your POM?
> >>>
> >>>- Brett
> >>>
> >>>On 6/5/05, Zachi Hazan <[hidden email]> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>I have just upgraded mvaen 2 to version alpha 2.
> >>>>When running compiler:compile plugin the an exception is thrown (see below).
> >>>>I have checked in maven sources and I saw that the method "compile"
> >>>>exists only on the new plexus jar, which was upgraded  after alpha 2
> >>>>realesed.
> >>>>
> >>>>How can I solve this problem?
> >>>>
> >>>>[ERROR] Cause:
> >>>>org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
> >>>>       at
> >>>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
> >>>>       at
> >>>>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
> >>>>       at
> >>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
> >>>>       at
> >>>>u using, and what is JAVA_HOME set to?
> >>>>
> >>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
> >>>>       at
> >>>>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
> >>>>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
> >>>>       at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
> >>>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>>       at
> >>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>>>       at
> >>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >>>>       at java.lang.reflect.Method.invoke(Method.java:324)
> >>>>       at
> >>>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
> >>>>       at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
> >>>>       at
> >>>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
> >>>>       at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
> >>>>Caused by: java.lang.NoSuchMethodException: compile
> >>>>       at java.lang.Class.getMethod0(Class.java:1742)
> >>>>       at java.lang.Class.getMethod(Class.java:951)
> >>>>       at
> >>>>org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
> >>>>       at
> >>>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
> >>>>       ... 14 more
> >>>>
> >>>>
> >>>>
> >>>>---------------------------------------------------------------------
> >>>>To unsubscribe, e-mail: [hidden email]
> >>>>For additional commands, e-mail: [hidden email]
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: [hidden email]
> >>>For additional commands, e-mail: [hidden email]
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [hidden email]
> >>For additional commands, e-mail: [hidden email]
> >>
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [hidden email]
> >For additional commands, e-mail: [hidden email]
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [m2]Compilation error when using maven version 2.0-alpha-2

Zachi Hazan
I switched to another JDK (j2sdk1.4.2_04) I have installed and it solve
the problem.
Thanks for the hint ;)

Brett Porter wrote:

>Yes, the compiler was changed in the last release to bettter support JDK 5.
>
>This is a bit strange. The programmatic interface we are using was
>only declared in JDK 5.0's documentation, but it has been tested on
>1.4.2.
>
>It works for me on 1.4.2_08, on Windows.
>
>Is there a way you can discover what methods com.sun.tools.javac.Main
>has on your JDK, through the IDE perhaps? You could also try upgrading
>to _08, but I don't see anything in the release notes indicating it
>has changed.
>
>What specific JDK do you have installed? Is it the one from Sun?
>
>- Brett
>
>On 6/6/05, Zachi Hazan <[hidden email]> wrote:
>  
>
>>Thanks for the quick response.
>>I am using JDK version
>>java version "1.4.2_04"
>>Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
>>Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
>>
>>My java home is set to "/sun/jdk/x86/linux/".
>>I am working with this jdk in other projects.
>>
>>I saw in maven svn that this "compile" was added immediately after alpha
>>2 release to plexsus.
>>Can it be that there is matching problems between maven 2.0-alpha-2 and
>>plexsus jars?
>>
>>Brett Porter wrote:
>>
>>    
>>
>>>Ok, on closer inspection - it looks like your JDK doesn't support the
>>>sun standard interface to Javac.
>>>
>>>What JDK are you using, and what is JAVA_HOME set to?
>>>
>>>Thanks,
>>>Brett
>>>
>>>On 6/6/05, Zachi Hazan <[hidden email]> wrote:
>>>
>>>
>>>      
>>>
>>>>No, only defined the plugin artifactid and group id
>>>>  <plugins>
>>>>     <plugin>
>>>>       <groupId>org.apache.maven.plugins</groupId>
>>>>       <artifactId>maven-compiler-plugin</artifactId>
>>>>     </plugin>
>>>>      ....
>>>>
>>>>Brett Porter wrote:
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>Have you hard coded the 2.0-alpha-1 plugin version for
>>>>>maven-compiler-plugin in your POM?
>>>>>
>>>>>- Brett
>>>>>
>>>>>On 6/5/05, Zachi Hazan <[hidden email]> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>I have just upgraded mvaen 2 to version alpha 2.
>>>>>>When running compiler:compile plugin the an exception is thrown (see below).
>>>>>>I have checked in maven sources and I saw that the method "compile"
>>>>>>exists only on the new plexus jar, which was upgraded  after alpha 2
>>>>>>realesed.
>>>>>>
>>>>>>How can I solve this problem?
>>>>>>
>>>>>>[ERROR] Cause:
>>>>>>org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
>>>>>>      at
>>>>>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:137)
>>>>>>      at
>>>>>>org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
>>>>>>      at
>>>>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
>>>>>>      at
>>>>>>u using, and what is JAVA_HOME set to?
>>>>>>
>>>>>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
>>>>>>      at
>>>>>>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
>>>>>>      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
>>>>>>      at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
>>>>>>      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>      at
>>>>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>      at
>>>>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>      at java.lang.reflect.Method.invoke(Method.java:324)
>>>>>>      at
>>>>>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
>>>>>>      at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
>>>>>>      at
>>>>>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
>>>>>>      at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
>>>>>>Caused by: java.lang.NoSuchMethodException: compile
>>>>>>      at java.lang.Class.getMethod0(Class.java:1742)
>>>>>>      at java.lang.Class.getMethod(Class.java:951)
>>>>>>      at
>>>>>>org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161)
>>>>>>      at
>>>>>>org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:132)
>>>>>>      ... 14 more
>>>>>>
>>>>>>
>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe, e-mail: [hidden email]
>>>>>>For additional commands, e-mail: [hidden email]
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: [hidden email]
>>>>>For additional commands, e-mail: [hidden email]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: [hidden email]
>>>>For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [hidden email]
>>>For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail: [hidden email]
>>
>>
>>    
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]