[
http://jira.codehaus.org/browse/MOJO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206609#action_206609
]
Tuomas Kiviaho commented on MOJO-1430:
--------------------------------------
Seems to be. I seem to be getting maven-jetty instead of maven-http-lightweight
which is what I though maven3 is supposed to be providing by default (m2eclipse
probably introduces it). Nevertheless started to work with explicit declaration
of correct wagon extension.
Caused by: java.lang.UnsupportedOperationException
at
org.apache.maven.wagon.providers.http.JettyClientHttpWagon.getFileList(JettyClientHttpWagon.java:614)
at
org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scandir(WagonDirectoryScanner.java:283)
at
org.codehaus.mojo.wagon.shared.WagonDirectoryScanner.scan(WagonDirectoryScanner.java:245)
at
org.codehaus.mojo.wagon.shared.DefaultWagonDownload.getFileList(DefaultWagonDownload.java:51)
at
org.codehaus.mojo.wagon.shared.DefaultWagonDownload.download(DefaultWagonDownload.java:59)
at org.codehaus.mojo.wagon.DownloadMojo.execute(DownloadMojo.java:48)
In any case I consider the issue to be resolved from wagon mojo part.
> r746285 commit removed WagonManager.getAuthentaticationInfo causing
> WagonUtils to fail with LinkageError when using m2eclipse
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MOJO-1430
> URL: http://jira.codehaus.org/browse/MOJO-1430
> Project: Mojo
> Issue Type: Bug
> Components: wagon
> Environment: wagon-maven-plugin:1.0-beta-1
> maven embedder
> Reporter: Tuomas Kiviaho
> Priority: Blocker
>
> http://svn.apache.org/viewvc/maven/components/trunk/maven-compat/compatibility.cfl?revision=796329
> states that
> (1) In r746285 various methods have been removed from the WagonManager which
> breaks the maven-project-info-reports-plugin, the
> maven-site-plugin and the maven-stage-plugin, e.g. due to a linkage error on
> getAuthentaticationInfo().
> Using maven embedder for example with m2eclipse causes wagon-maven-plugin to
> crash when org.codehaus.mojo.wagon.shared.WagonUtils#createWagon tries to get
> authenticationinfo from wagon manager.
> Compatibility file states also that
> Maven Artifact will be entirely extricated from the core of Maven 3.x and
> replaced with Mercury, but we will make a best effort to
> ensure the compatibility of plugins that use Maven Artifact. There are,
> however, components and classes that are just so broken or conflict
> with standard ways of doing resolution and conflict reduction that we can't
> support them.
> Is there still a way to make this plugin maven-compat compatible as well
> while supporting backwards compatibility.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
