I think I have gotten around that issue by moving directly to m7
instead of trying to go incrementally.
But now I get classloader isolation issues:
Nested exception:
java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast
to org.dom4j.DocumentFactory
at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97)
at org.dom4j.io.SAXReader.getDocumentFactory(SAXReader.java:645)
at org.dom4j.io.SAXReader.createContentHandler(SAXReader.java:969)
at org.dom4j.io.SAXReader.read(SAXReader.java:449)
...
On Mon 16 Jan 2012 01:39:10 PM CST, Steve Ebersole wrote:
The gradle-upload-auth-plugin
(https://github.com/sebersole/gradle-upload-auth-plugin) is currently
stuck at m2/m3. I have been putting off upgrading it because initially
i was promised that a "Publication API" that would solidify how to
interact with repositories and deployers was "on its way soon".
To the best of my knowledge that API has never been done. So I guess
its time to just do the upgrade. But, apparently changes have been
done that now cause my plugin code to fail.
Here is the error I am getting:
Caused by: java.lang.NoSuchMethodError:
org.gradle.api.artifacts.maven.MavenDeployer.getRepository()Lorg/apache/maven/artifact/ant/RemoteRepository;
at
org.hibernate.build.gradle.upload.AuthenticationHandler$1.execute(AuthenticationHandler.java:56)
...
org.gradle.api.artifacts.maven.MavenDeployer.getRepository is
certainly still there in m7. So why am I getting this error?
P.S. Also, what are the chance of this getting sucked into the Maven
plugin codebase? That is really where this belongs. Changes are if I
am pulling in that plugin I am deploying to Maven repositories and
have ~/.m2/settings.xml set up.
--
[email protected]
http://hibernate.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
