Hello,
I'm trying to migrate a project from maven 2 to gradle.
The problem is we use a custom packaging with maven (call it customPack)
So when I run compileJava in my project with dependency A in a maven repo,
gradle finds A's pom file and understands <packaging> customPack
</packaging> as the extension. The result is a compile error as
"A.customPack" doesn exists in the repo.
Well I can tell to gradle
dependencies{
compile "A@jar"
}
This way it will correctly download "A.jar", but when gradle resolves A
dependencies (A depends on B) it will again try to download B.customPack
instead of jar.
So my question is: Is there a way to tell gradle a default artifact
extension (jar) and ignore the pom's field "packaging"?
Thanks
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Gradle-default-Dependency-extension-tp5142126p5142126.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
