[#GRAILS-6427] Non-jar dependencies cannot be resolved - Grails JIRA

Details

Type: Bug
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: 1.3.2, 1.3.3
Fix Version/s: 1.3.4
Component/s: Project infrastructure
Labels:
None

Description

Since Grails 1.3.2 any Ivy dependencies with a packaging other than "jar" do not resolve correctly. For example the Jetty plugin depends on JSP 2.0 (http://mirrors.ibiblio.org/pub/mirrors/maven2/org/mortbay/jetty/jsp-2.0/6.1.11/jsp-2.0-6.1.11.pom) which has packaging "pom". When Grails attempts to resolve the dependency it tries to look for a jar file. Something must be defaulting the expected packaging rather than reading it from the downloaded pom file.

Issue Links

This issue duplicates:
GRAILS-6420	Installing plugins from maven

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Ryan Vanderwerf added a comment - 23/Jun/10 1:06 PM

I'm having a similar issue. I created my own plugin, added it to Artifactory (I was trying to follow the article by Peter Ledbrook at http://blog.springsource.com/2010/05/18/managing-plugins-with-grails-1-3/), and trying to make a Grails 1.3.2 project depend on it in BuildConfig.groovy:

plugins { build 'org.grails.plugins:mdp-core:0.1' runtime 'org.grails.plugins:mdp-core:0.1' compile 'org.grails.plugins:mdp-core:0.1' test 'org.grails.plugins:mdp-core:0.1' provided 'org.grails.plugins:mdp-core:0.1' }

When I run any task in my app, it says it can't resolve the plugin. However I have the POM and ZIP located at one of the urls it tries - it just never actually seems to try and connect. When I try the urls by hand in a browser its complaining about, they work (files download).

==== http://hudson.blah.com:8080/artifactory/plugins-releases-local: tried

http://hudson.blah.com:8080/artifactory/plugins-releases-local/org/grails/plugins/mdp-core/0.1/mdp-core-0.1-jar.pom

– artifact org.grails.plugins#mdp-core;0.1!mdp-core.zip:

http://hudson.blah.com:8080/artifactory/plugins-releases-local/org/grails/plugins/mdp-core/0.1/mdp-core-0.1-jar.zip

::::::::::::::::::::::::::::::::::::::::::::::

:: UNRESOLVED DEPENDENCIES ::

::::::::::::::::::::::::::::::::::::::::::::::

:: org.grails.plugins#mdp-core;0.1: not found

::::::::::::::::::::::::::::::::::::::::::::::

I even installed tinyproxy and set up Grails to use the proxy. I got no hits while it's trying to resolve this (Yes I did verify my .grails/ProxyConfig.groovy is there and correct). It appears it doesn't even try.

While debugging in the grails source it never even gets to the method 'File resolvePluginZip(String pluginName, String pluginVersion, String scope = "", Map args = [:]) {' in PluginResolveEngine.java as far as I can tell.

It seems something deep down is triggering the error and setting that error report back with stuff it says it tried, but really didn't.

Show

Ryan Vanderwerf added a comment - 23/Jun/10 1:06 PM I'm having a similar issue. I created my own plugin, added it to Artifactory (I was trying to follow the article by Peter Ledbrook at http://blog.springsource.com/2010/05/18/managing-plugins-with-grails-1-3/), and trying to make a Grails 1.3.2 project depend on it in BuildConfig.groovy: plugins { build 'org.grails.plugins:mdp-core:0.1' runtime 'org.grails.plugins:mdp-core:0.1' compile 'org.grails.plugins:mdp-core:0.1' test 'org.grails.plugins:mdp-core:0.1' provided 'org.grails.plugins:mdp-core:0.1' } When I run any task in my app, it says it can't resolve the plugin. However I have the POM and ZIP located at one of the urls it tries - it just never actually seems to try and connect. When I try the urls by hand in a browser its complaining about, they work (files download). ==== http://hudson.blah.com:8080/artifactory/plugins-releases-local: tried http://hudson.blah.com:8080/artifactory/plugins-releases-local/org/grails/plugins/mdp-core/0.1/mdp-core-0.1-jar.pom – artifact org.grails.plugins#mdp-core;0.1!mdp-core.zip: http://hudson.blah.com:8080/artifactory/plugins-releases-local/org/grails/plugins/mdp-core/0.1/mdp-core-0.1-jar.zip :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: org.grails.plugins#mdp-core;0.1: not found :::::::::::::::::::::::::::::::::::::::::::::: I even installed tinyproxy and set up Grails to use the proxy. I got no hits while it's trying to resolve this (Yes I did verify my .grails/ProxyConfig.groovy is there and correct). It appears it doesn't even try. While debugging in the grails source it never even gets to the method 'File resolvePluginZip(String pluginName, String pluginVersion, String scope = "", Map args = [:]) {' in PluginResolveEngine.java as far as I can tell. It seems something deep down is triggering the error and setting that error report back with stuff it says it tried, but really didn't.

Hide

Permalink

Robert Fletcher added a comment - 08/Jul/10 11:44 PM

This is still affecting Grails 1.3.3. A simple way to reproduce it is to check out the jetty plugin code, update the grails version to 1.3.3 then try to run `grails dependency-report`

Show

Robert Fletcher added a comment - 08/Jul/10 11:44 PM This is still affecting Grails 1.3.3. A simple way to reproduce it is to check out the jetty plugin code, update the grails version to 1.3.3 then try to run `grails dependency-report`

Hide

Permalink

Markus Mueller added a comment - 12/Jul/10 5:21 AM

We're forced to use Jetty for now and this is really a Blocker, isn't there any workaround available?

Show

Markus Mueller added a comment - 12/Jul/10 5:21 AM We're forced to use Jetty for now and this is really a Blocker, isn't there any workaround available?

Hide

Permalink

Ryan Vanderwerf added a comment - 12/Jul/10 9:32 AM

Weird. I can't use jetty anymore in 1.3.3, I have to use tomcat. I get the can't find the jsp-2.0 jar error message.

Show

Ryan Vanderwerf added a comment - 12/Jul/10 9:32 AM Weird. I can't use jetty anymore in 1.3.3, I have to use tomcat. I get the can't find the jsp-2.0 jar error message.

Hide

Permalink

Robert Fletcher added a comment - 12/Jul/10 5:16 PM

This affects any app using the Springcache plugin as well as the ehcache dependency is packaged as pom.

Show

Robert Fletcher added a comment - 12/Jul/10 5:16 PM This affects any app using the Springcache plugin as well as the ehcache dependency is packaged as pom.

Hide

Permalink

Jean-Noël Rivasseau added a comment - 19/Jul/10 10:54 AM

This issue is also preventing me from updating to 1.2.x. I hope 1.3.4 comes soon and really resolves it

Show

Jean-Noël Rivasseau added a comment - 19/Jul/10 10:54 AM This issue is also preventing me from updating to 1.2.x. I hope 1.3.4 comes soon and really resolves it

Hide

Permalink

Graeme Rocher added a comment - 23/Jul/10 5:22 AM

Fixed by: http://github.com/grails/grails-core/commit/b532585fa8704db2204d37ea9cd0f00d075c276e

Causes a regression of ~~GRAILS-6315~~ which I will reopen and fix shortly

Functional tests found here: http://github.com/grails/grails-functional-tests/commit/25662527deaa68b6b1e235efd695ffbe2117ab7e

Show

Graeme Rocher added a comment - 23/Jul/10 5:22 AM Fixed by: http://github.com/grails/grails-core/commit/b532585fa8704db2204d37ea9cd0f00d075c276e Causes a regression of ~~GRAILS-6315~~ which I will reopen and fix shortly Functional tests found here: http://github.com/grails/grails-functional-tests/commit/25662527deaa68b6b1e235efd695ffbe2117ab7e

Hide

Permalink

Feroz Panwaskar added a comment - 30/Jul/10 5:18 AM

As a workaround I found you can simply reinstall the plugins that cannot be resolved. Remove from plugin reference from application.properties and run install-plugin command.

Show

Feroz Panwaskar added a comment - 30/Jul/10 5:18 AM As a workaround I found you can simply reinstall the plugins that cannot be resolved. Remove from plugin reference from application.properties and run install-plugin command.

People

Assignee:

Graeme Rocher

Reporter:

Robert Fletcher

Vote (11)

Watch (13)

Dates

Created:

21/Jun/10 3:05 AM

Updated:

30/Jul/10 5:18 AM

Resolved:

23/Jul/10 5:22 AM