Details
-
Type:
Bug
-
Status:
Resolved
-
Resolution: Fixed
-
Affects Version/s: 1.0-milestone-9
-
Fix Version/s: 1.1-rc-1
Description
Jetty has a dependency of type "orbit", which fails with gradle (and also ivy), but works with maven.
This is pretty much the same as GRADLE-2076, and is described in a comment to that issues (http://issues.gradle.org/browse/GRADLE-2076?focusedCommentId=14942&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14942). The solution applied to types "eclipse-plugin" should also apply to type "orbit" – or maybe the solution in the comment above should be used ("I might be wrong, but Maven seems to default to jar if <type></type> isn't specified in the dependency declaration. Would defaulting to jar for unknown packaging types cause problems with Gradle (or Ivy for that matter)?").
Issue Links
- Duplicated by
-
GRADLE-2285
Dependency with package type 'orbit' should be interpreted as a jar
-
Activity
I had a friendly email conversation with Daz DeBoer, who fixed the related bug GRADLE-2076. The most relevant part was this:
Our current behaviour is just the ivy default behaviour, with the fix for handling types 'maven-plugin' and 'eclipse-plugin'. You're certainly right about needing a more general solution: probably just map "known" package types to their extensions, and everything else to 'jar'. We want to work the same as Maven when dealing with pom files.
A pull-request with the fix is probably the best way to get this bug prioritised
.
I sympathize with the desire for a pull-request, but I'm just not familiar enough with the gradle codebase to even get started.
Our current behaviour is just the ivy default behaviour, with the fix for handling types 'maven-plugin' and 'eclipse-plugin'. You're certainly right about needing a more general solution: probably just map "known" package types to their extensions, and everything else to 'jar'. We want to work the same as Maven when dealing with pom files. A pull-request with the fix is probably the best way to get this bug prioritisedI sympathize with the desire for a pull-request, but I'm just not familiar enough with the gradle codebase to even get started.
I've also discovered Jetty has a set of aggregate JARs that work a bit better for embedding. I've been using org.eclipse.jetty.aggregate:jetty-servlet:8.1.3.v20120416 for a couple days and the packaging seems to be a little more sane.