embedded maven in future 0.9.5

[hgomez]

There was a problem with maven 2.1 and jax-ws mojo :

...

Reason: Failed to execute wsgen

java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
        at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
        at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)



Error stacktrace:
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen': Mojo execution
failed.
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo
execution failed.
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
        ... 12 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
execute wsgen
        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:102)
        at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
        ... 13 more
Caused by: java.lang.NoClassDefFoundError:
com/sun/mirror/apt/AnnotationProcessorFactory
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
        at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
        ... 15 more

...

Bugs report on http://jira.codehaus.org/browse/MNG-3586

What version of maven 2.1 will be bundled with 0.9.5, since I recall
seeing this bug has been fixed 2 or 3 weeks ago ?

Regards

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hgomez]

The problem is still here with the apache-maven-2.1-659801 ;(

Not fixed.

How can we make these one fixed ?

 I suspect it to be the cause of resources copy failures (and jaxws
binding not done) when doing Project Clean

2008/6/27 Henri Gomez <henri.gomez@...>:

> There was a problem with maven 2.1 and jax-ws mojo :
>
> ...
>
> Reason: Failed to execute wsgen
>
> java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
>        at java.lang.ClassLoader.defineClass1(Native Method)
>        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
>        at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
>        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>        at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
>        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
>        at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>
>
>
> Error stacktrace:
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
> in the plugin manager executing goal
> 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen': Mojo execution
> failed.
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo
> execution failed.
>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
>        ... 12 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
> execute wsgen
>        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:102)
>        at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
>        ... 13 more
> Caused by: java.lang.NoClassDefFoundError:
> com/sun/mirror/apt/AnnotationProcessorFactory
>        at java.lang.ClassLoader.defineClass1(Native Method)
>        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
>        at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
>        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>        at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
>        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
>        ... 15 more
>
> ...
>
> Bugs report on http://jira.codehaus.org/browse/MNG-3586
>
> What version of maven 2.1 will be bundled with 0.9.5, since I recall
> seeing this bug has been fixed 2 or 3 weeks ago ?
>
> Regards
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Eugene Kuleshov]

Henri,

  I am not exactly sure where you get apache-maven-2.1-659801, but if
you are able to reproduce this issue from the command line with this
Maven version, it would make sense to open JIRA issue on MNG project
and/or ask about it in Maven's user list.
  However if it does work from the command line with Maven 2.1 and only
fail in m2eclipse, then please cubmit bug report to m2eclipse and attach
a simple test project that would allow us to reproduce it.

  Thanks

  Eugene  


Henri Gomez wrote:

> The problem is still here with the apache-maven-2.1-659801 ;(
>
> Not fixed.
>
> How can we make these one fixed ?
>
>  I suspect it to be the cause of resources copy failures (and jaxws
> binding not done) when doing Project Clean
>
> 2008/6/27 Henri Gomez <henri.gomez@...>:
>  
>> There was a problem with maven 2.1 and jax-ws mojo :
>>
>> ...
>>
>> Reason: Failed to execute wsgen
>>
>> java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
>>        at java.lang.ClassLoader.defineClass1(Native Method)
>>        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>>        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>>        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>>        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>>        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>>        at java.security.AccessController.doPrivileged(Native Method)
>>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>>        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
>>        at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
>>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
>>        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>>        at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
>>        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
>>        at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
>>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>>        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>>        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>>        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>>
>>
>>
>> Error stacktrace:
>> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
>> in the plugin manager executing goal
>> 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsgen': Mojo execution
>> failed.
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>>        at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>>        at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>>        at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>>        at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>>        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>> Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo
>> execution failed.
>>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
>>        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
>>        ... 12 more
>> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
>> execute wsgen
>>        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:102)
>>        at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14)
>>        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
>>        ... 13 more
>> Caused by: java.lang.NoClassDefFoundError:
>> com/sun/mirror/apt/AnnotationProcessorFactory
>>        at java.lang.ClassLoader.defineClass1(Native Method)
>>        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>>        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>>        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>>        at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>>        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>>        at java.security.AccessController.doPrivileged(Native Method)
>>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>>        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadRealmClass(ClassRealm.java:174)
>>        at org.codehaus.plexus.classworlds.strategy.DefaultStrategy.loadClass(DefaultStrategy.java:67)
>>        at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:201)
>>        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>>        at com.sun.tools.ws.WsGen.doMain(WsGen.java:69)
>>        at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.java:97)
>>        ... 15 more
>>
>> ...
>>
>> Bugs report on http://jira.codehaus.org/browse/MNG-3586
>>
>> What version of maven 2.1 will be bundled with 0.9.5, since I recall
>> seeing this bug has been fixed 2 or 3 weeks ago ?
>>
>> Regards
>>
>>    
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>  

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hgomez]

> Henri,

Hello Eugene


>  I am not exactly sure where you get apache-maven-2.1-659801

Q4E has some snapshots :)

>but if you are
> able to reproduce this issue from the command line with this Maven version,
> it would make sense to open JIRA issue on MNG project and/or ask about it in
> Maven's user list.

Bugs allready opened, http://jira.codehaus.org/browse/MNG-3586.

>  However if it does work from the command line with Maven 2.1 and only fail
> in m2eclipse, then please cubmit bug report to m2eclipse and attach a simple
> test project that would allow us to reproduce it.

m2eclipse use embedded maven for all of its internal operation ?

Selecting the maven (embedded or externals) only works when doing Run
Maven ... ?

Regards

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Eugene Kuleshov]

Henri Gomez wrote:
>>  I am not exactly sure where you get apache-maven-2.1-659801
>>    
> Q4E has some snapshots :)
>  
  Are you sure you are asking question in the right mailing list? :)
  We couldn't possible know what bugs some random Maven version has.
>> but if you are able to reproduce this issue from the command line with this Maven version, it would make sense to open JIRA issue on MNG project and/or ask about it in Maven's user list.
>>    
> Bugs allready opened, http://jira.codehaus.org/browse/MNG-3586.
>  
  That doesn't quite answers my question. If it is a bug in Maven 2.1 it
is not going to work in m2eclipse and someone from Maven team would have
to look at this.
>>  However if it does work from the command line with Maven 2.1 and only fail
>> in m2eclipse, then please cubmit bug report to m2eclipse and attach a simple
>> test project that would allow us to reproduce it.
>>    
> m2eclipse use embedded maven for all of its internal operation ?
>
> Selecting the maven (embedded or externals) only works when doing Run
> Maven ... ?
>  
  That doesn't mean that m2eclipse team can fix all bugs found in Maven
2.1. We would love to help you, but unfortunately our time and resources
are not infinite. We did contributed some patches to Maven in a past to
fix most common issues, but for fundamental things like classloading,
backward incompatibility with Maven 2.0 for some plugins (like in your
case) and other core issues you really need to talk to the Maven team.

  regards,
  Eugene



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hgomez]

>  Are you sure you are asking question in the right mailing list? :)

Yes :)

>  We couldn't possible know what bugs some random Maven version has.

I know but since you're using the embedded maven 2.1 you should be
warned about this jaxws problem.

>  That doesn't quite answers my question. If it is a bug in Maven 2.1 it is
> not going to work in m2eclipse and someone from Maven team would have to
> look at this.

It's a bug in Maven 2.1 and still not fixed.

>  That doesn't mean that m2eclipse team can fix all bugs found in Maven 2.1.

Nope, I was asking if there is a way for m2eclipse to use an external
maven 2.0 for its internal operations

> We would love to help you, but unfortunately our time and resources are not
> infinite. We did contributed some patches to Maven in a past to fix most
> common issues, but for fundamental things like classloading, backward
> incompatibility with Maven 2.0 for some plugins (like in your case) and
> other core issues you really need to talk to the Maven team.

Allreadu ask but ... who care ;(

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Eugene Kuleshov]

Henri Gomez wrote:
>>  That doesn't mean that m2eclipse team can fix all bugs found in Maven 2.1.
>>    
> Nope, I was asking if there is a way for m2eclipse to use an external maven 2.0 for its internal operations
>  
  Unfortunately it is not possible, because Maven 2.0 is not embeddable.

  By the way, I thought you are not using m2eclipse anymore...

>> We would love to help you, but unfortunately our time and resources are not
>> infinite. We did contributed some patches to Maven in a past to fix most
>> common issues, but for fundamental things like classloading, backward
>> incompatibility with Maven 2.0 for some plugins (like in your case) and
>> other core issues you really need to talk to the Maven team.
>>    
> Allreadu ask but ... who care ;(
>  
  There is always an alternative. For instance, you can also try to fix
it yourself, submit patches and eventually became Maven committer, so
everything would be fixed in a blink of your eye. ;-)

  Seriously speaking, every team have priorities. There are over 600 bug
reports and enhancement requests issues open on Maven project. You can
do the math games to calculate how much time Maven team would need to
fix all of them. So, they have to prioritize what they believe is
important and take patches if someone contribute fixes to the low
priority issues.

  regards,
  Eugene



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hgomez]

>  Unfortunately it is not possible, because Maven 2.0 is not embeddable.

ok

>  By the way, I thought you are not using m2eclipse anymore...

no, I'm still using m2eclipse, 0.9.4 ;)

>  There is always an alternative. For instance, you can also try to fix it
> yourself, submit patches and eventually became Maven committer, so
> everything would be fixed in a blink of your eye. ;-)

Well why not :) I'll try to do, since I'm spend more time now with
maven than with tomcat (i'm an old time tomcat commiter)

>  Seriously speaking, every team have priorities. There are over 600 bug
> reports and enhancement requests issues open on Maven project. You can do
> the math games to calculate how much time Maven team would need to fix all
> of them. So, they have to prioritize what they believe is important and take
> patches if someone contribute fixes to the low priority issues.

I understand it well. I'll try to see if I could fix this one and
provide patches

>  regards,
>  Eugene

Regards

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email