[GRADLE-2188] Artifact not found resolving dependencies with packaging/type "orbit" Created: 20/Mar/12  Updated: 04/Jan/13  Resolved: 11/Jul/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-9
Fix Version/s: 1.1-rc-1

Type: Bug
Reporter: Eirik Lygre Assignee: Unassigned
Resolution: Fixed Votes: 3

Issue Links:
Duplicated by GRADLE-2285 Dependency with package type 'orbit' ... Resolved


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)?").

Comment by Ryan J [ 05/May/12 ]

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.

Comment by Niclas Hedhman [ 12/May/12 ]

Well, aggregate:jetty-webapp still wants to download @orbit. Jetty is such a central piece of most development, I think this is quite an important showstopper at the moment.

Comment by Eirik Lygre [ 14/May/12 ]

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.

Comment by Eirik Lygre [ 16/Jun/12 ]

A duplicate issue has been reported at GRADLE-2285. The reporter there has indicated that he will create the desired pull-request, so maybe that will sort things out.

Generated at Wed Jun 30 12:15:06 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.