|
Hi all,
I just added the spring-security-ui plugin (1.0.2) to my project. It depends on the mail plugin (this is released as 1.0-SNAPSHOT) . Now, when I let Hudson run 'test-app', the build fails completely. When I run test-app locally, the exact same warning appear, but grails seems happy to ignore it and continues. That is hardly reassuring :) Here's the output: Installing zip /var/lib/hudson/.ivy2/cache/org.grails.plugins/mail/zips/mail-1.0-SNAPSHOT.zip... ... [mkdir] Created dir: /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT [unzip] Expanding: /var/lib/hudson/.ivy2/cache/org.grails.plugins/mail/zips/mail-1.0-SNAPSHOT.zip into /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT Installed plugin mail-1.0-SNAPSHOT to location /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT. ... Resolving plugin JAR dependencies ... :: problems summary :: :::: WARNINGS :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: org.springframework#org.springframework.test;3.0.5.RELEASE: configuration not found in org.springframework#org.springframework.test;3.0.5.RELEASE: 'master'. It was required from org.grails.internal#surfsesh;0.29 test :::::::::::::::::::::::::::::::::::::::::::::: Failed to install plugin [mail-1.0-SNAPSHOT]. Plugin has missing JAR dependencies. [delete] Deleting directory /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT ---------- I think there is no way I can make Hudson ignore the warning, and I think I shouldn't even want to. What can be causing this issue? I see that the grails mail plugin specifies the following: dependencies { compile "javax.mail:mail:1.4.1" runtime "org.springframework:org.springframework.test:3.0.3.RELEASE" } I am surprised to see that the mail plugin requires the spring-test jar in runtime scope. Shouldn't that be 'test'? Does it have anything to do with the problem I am facing? Regards, Hans --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
I'm receiving this exact same error.
My plugin has three dependencies outlined in BuildConfig.groovy as follows: plugins { compile ':spring-security-core:1.1'
compile ':spring-security-ldap:1.0.2' compile ':spring-security-ui:0.1.2' } I run "grails package-plugin" and then install it locally into a newly generate grails app.
Plugin dependency resolution pukes because the mail-1.0-SNAPSHOT plugin is missing the spring-test jar. Anyone know how to work around this? Here's the error: Installed plugin mail-1.0-SNAPSHOT to location C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins/mail-1.0-SNAPSHOT. ... Resolving plugin JAR dependencies ...
:: problems summary :: :::: WARNINGS module not found: org.springframework#spring-test;latest.release ==== grailsHome: tried
C:\grails\grails-1.3.6\lib/spring-test-[revision].xml -- artifact org.springframework#spring-test;latest.release!spring-test.jar:
C:\grails\grails-1.3.6\lib/spring-test-[revision].jar ==== grailsHome: tried
C:\grails\grails-1.3.6\dist/spring-test-[revision].xml -- artifact org.springframework#spring-test;latest.release!spring-test.jar:
C:\grails\grails-1.3.6\dist/spring-test-[revision].jar ==== grailsHome: tried
-- artifact org.springframework#spring-test;latest.release!spring-test.jar: C:\grails\grails-1.3.6/plugins/grails-spring-test-[revision].jar
==== grailsCentral: tried -- artifact org.springframework#spring-test;latest.release!spring-test.jar:
<a href="http://svn.codehaus.org/grails-plugins/grails-spring-test/tags/RELEASE_latest_release/grails-spring-test-[revision].jar">http://svn.codehaus.org/grails-plugins/grails-spring-test/tags/RELEASE_latest_release/grails-spring-test-[revision].jar
==== grailsCore: tried -- artifact org.springframework#spring-test;latest.release!spring-test.jar:
<a href="http://svn.codehaus.org/grails/trunk/grails-plugins/grails-spring-test/tags/RELEASE_latest_release/grails-spring-test-[revision].jar">http://svn.codehaus.org/grails/trunk/grails-plugins/grails-spring-test/tags/RELEASE_latest_release/grails-spring-test-[revision].jar
==== ebrRelease: tried <a href="http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].pom">http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].pom
-- artifact org.springframework#spring-test;latest.release!spring-test.jar: <a href="http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].jar">http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].jar
==== ebrExternal: tried <a href="http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].pom">http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].pom
-- artifact org.springframework#spring-test;latest.release!spring-test.jar: <a href="http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].jar">http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].jar
==== ebrRelease: tried <a href="http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].pom">http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].pom
-- artifact org.springframework#spring-test;latest.release!spring-test.jar: <a href="http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].jar">http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].jar
==== ebrExternal: tried <a href="http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].pom">http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].pom
-- artifact org.springframework#spring-test;latest.release!spring-test.jar: <a href="http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].jar">http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].jar
==== http://download.java.net/maven/2/: tried <a href="http://download.java.net/maven/2/org/springframework/spring-test/[revision]/spring-test-[revision].pom">http://download.java.net/maven/2/org/springframework/spring-test/[revision]/spring-test-[revision].pom
-- artifact org.springframework#spring-test;latest.release!spring-test.jar: <a href="http://download.java.net/maven/2/org/springframework/spring-test/[revision]/spring-test-[revision].jar">http://download.java.net/maven/2/org/springframework/spring-test/[revision]/spring-test-[revision].jar
==== grailsPlugins: tried -- artifact org.springframework#spring-test;latest.release!spring-test.jar:
C:\code\PluginTesUtilizationApp/lib/spring-test-[revision].jar C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\my-plugin-0.1/lib/spring-test-[revision].jar
C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\mail-1.0-SNAPSHOT/lib/spring-test-[revision].jar
C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\spring-security-core-1.1/lib/spring-test-[revision].jar
C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\spring-security-ldap-1.0.2/lib/spring-test-[revision].jar
C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\spring-security-ui-0.1.2/lib/spring-test-[revision].jar
:::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES ::
:::::::::::::::::::::::::::::::::::::::::::::: :: org.springframework#spring-test;latest.release: not found
:::::::::::::::::::::::::::::::::::::::::::::: Failed to install plugin [mail-1.0-SNAPSHOT]. Plugin has missing JAR dependencies.
[delete] Deleting directory C:\Documents and Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\mail-1.0-SNAPSHOT On Wed, Jan 26, 2011 at 11:03 AM, Hans Westerbeek <[hidden email]> wrote: Hi all, |
|
org.springframework#spring-test;latest.release should be found in Maven Central repository.
Try uncomment mavenCentral() in BuildConfig.groovy Ronny On Feb 21, 2011, at 5:36 PM, Dean Del Ponte wrote: I'm receiving this exact same error. |
|
Thanks Ronny,
That helped a lot, now I'm just trying to figure out why the spring-security-ui plugin's dependencies aren't resolved automatically. I'm getting so close! My plugin defines the following dependencies in BuildConfig.groovy: plugins { compile ':spring-security-core:1.1' compile ':spring-security-ldap:1.0.2'
compile ':spring-security-ui:0.1.2' } Yet, when this plugin is installed into a grails app, and I then try to run the app, the following messages are received:
Error: The following plugins failed to load due to missing dependencies: [myPlugin, springSecurityUi] - Plugin: myPlugin - Dependencies: - springSecurityCore (Required: * > 1.1, Found: 1.1)
- springSecurityLdap (Required: * > 1.0.2, Found: 1.0.2) ! springSecurityUi (Required: * > 0.1.2, Found: Not Installed) [INVALID] - Plugin: springSecurityUi - Dependencies:
- springSecurityCore (Required: 0.4 > *, Found: 1.1) ! mail (Required: 0.9 > *, Found: Not Installed) [INVALID] ! jquery (Required: 1.4.2.5 > *, Found: Not Installed) [INVALID]
! jqueryUi (Required: 1.8.2.3 > *, Found: Not Installed) [INVALID] ! famfamfam (Required: 1.0 > *, Found: Not Installed) [INVALID] Do I need to explicitly list the springSecurityUi plugin dependencies in my plugins BuildConfig.groovy.
I was hoping they would be automatically resolved. Thanks everyone! Dean Del Ponte On Mon, Feb 21, 2011 at 11:10 AM, Ronny Løvtangen <[hidden email]> wrote:
|
|
They should be automatically resolved. It's not a 100% good solution at the moment IMHO, as the transitive plugin dependencies are actually added to application.properties.
My workflow at the moment is to add the plugins I use to BuildConfig.groovy, and just accept whatever the plugins wants to add to application.properties. That way I know that the plugins listed in BuildConfig.groovy are my direct dependencies, and the ones in application.properties are just transitive dependencies. This works well, as long as I make sure to read the prompts during 'grails war' with care; when adding plugins that has transitive plugin, the install process will actually ask me to _remove_ the plugins it installed just a second ago (during the same run). I don't know about plugin development, but for regular grails apps, when adding plugin dependencies, I run 'grails war' once to get the plugin installed. Not sure if 'grails run-app' is sufficient or not. Ronny On Feb 21, 2011, at 6:28 PM, Dean Del Ponte wrote: Thanks Ronny, |
|
I started fresh be deleting all projects in my ".grails" directory and then created a new app to test installation of my plugin.
All dependencies were properly resolved.
Thanks for your help! Dean Del Ponte
On Mon, Feb 21, 2011 at 11:47 AM, Ronny Løvtangen <[hidden email]> wrote:
|
|
In reply to this post by Ronny Løvtangen
Ok, I see this relates to a mail I sent a little earlier. My question
is why would spring-test be a runtime dependency? Is it ok to have it included in the production app? Thanks -- biz: http://www.linkedin.com/in/vincentstoessel/ personal: http://xaymaca.tumblr.com/ On Mon, Feb 21, 2011 at 12:10 PM, Ronny Løvtangen <[hidden email]> wrote: > org.springframework#spring-test;latest.release should be found in Maven > Central repository. > Try uncomment mavenCentral() in BuildConfig.groovy > Ronny > > On Feb 21, 2011, at 5:36 PM, Dean Del Ponte wrote: > > I'm receiving this exact same error. > My plugin has three dependencies outlined in BuildConfig.groovy as follows: > plugins { > compile ':spring-security-core:1.1' > compile ':spring-security-ldap:1.0.2' > compile ':spring-security-ui:0.1.2' > } > I run "grails package-plugin" and then install it locally into a newly > generate grails app. > Plugin dependency resolution pukes because the mail-1.0-SNAPSHOT plugin is > missing the spring-test jar. > Anyone know how to work around this? Here's the error: > Installed plugin mail-1.0-SNAPSHOT to location C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins/mail-1.0-SNAPSHOT. > ... > Resolving plugin JAR dependencies ... > :: problems summary :: > :::: WARNINGS > module not found: org.springframework#spring-test;latest.release > ==== grailsHome: tried > C:\grails\grails-1.3.6\lib/spring-test-[revision].xml > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > C:\grails\grails-1.3.6\lib/spring-test-[revision].jar > ==== grailsHome: tried > C:\grails\grails-1.3.6\dist/spring-test-[revision].xml > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > C:\grails\grails-1.3.6\dist/spring-test-[revision].jar > ==== grailsHome: tried > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > C:\grails\grails-1.3.6/plugins/grails-spring-test-[revision].jar > ==== grailsCentral: tried > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://svn.codehaus.org/grails-plugins/grails-spring-test/tags/RELEASE_latest_release/grails-spring-test-[revision].jar > ==== grailsCore: tried > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://svn.codehaus.org/grails/trunk/grails-plugins/grails-spring-test/tags/RELEASE_latest_release/grails-spring-test-[revision].jar > ==== ebrRelease: tried > http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].pom > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].jar > ==== ebrExternal: tried > http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].pom > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].jar > ==== ebrRelease: tried > http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].pom > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://repository.springsource.com/maven/bundles/release/org/springframework/spring-test/[revision]/spring-test-[revision].jar > ==== ebrExternal: tried > http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].pom > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://repository.springsource.com/maven/bundles/external/org/springframework/spring-test/[revision]/spring-test-[revision].jar > ==== http://download.java.net/maven/2/: tried > http://download.java.net/maven/2/org/springframework/spring-test/[revision]/spring-test-[revision].pom > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > http://download.java.net/maven/2/org/springframework/spring-test/[revision]/spring-test-[revision].jar > ==== grailsPlugins: tried > -- artifact org.springframework#spring-test;latest.release!spring-test.jar: > C:\code\PluginTesUtilizationApp/lib/spring-test-[revision].jar > C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\my-plugin-0.1/lib/spring-test-[revision].jar > C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\mail-1.0-SNAPSHOT/lib/spring-test-[revision].jar > C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\spring-security-core-1.1/lib/spring-test-[revision].jar > C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\spring-security-ldap-1.0.2/lib/spring-test-[revision].jar > C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\spring-security-ui-0.1.2/lib/spring-test-[revision].jar > :::::::::::::::::::::::::::::::::::::::::::::: > :: UNRESOLVED DEPENDENCIES :: > :::::::::::::::::::::::::::::::::::::::::::::: > :: org.springframework#spring-test;latest.release: not found > :::::::::::::::::::::::::::::::::::::::::::::: > > Failed to install plugin [mail-1.0-SNAPSHOT]. Plugin has missing JAR > dependencies. > [delete] Deleting directory C:\Documents and > Settings\user\.grails\1.3.6\projects\PluginTesUtilizationApp\plugins\mail-1.0-SNAPSHOT > > On Wed, Jan 26, 2011 at 11:03 AM, Hans Westerbeek <[hidden email]> > wrote: >> >> Hi all, >> >> I just added the spring-security-ui plugin (1.0.2) to my project. It >> depends on the mail plugin (this is released as 1.0-SNAPSHOT) . Now, >> when I let Hudson run 'test-app', the build fails completely. When I >> run test-app locally, the exact same warning appear, but grails seems >> happy to ignore it and continues. That is hardly reassuring :) >> >> Here's the output: >> >> Installing zip >> /var/lib/hudson/.ivy2/cache/org.grails.plugins/mail/zips/mail-1.0-SNAPSHOT.zip... >> ... >> [mkdir] Created dir: >> /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT >> [unzip] Expanding: >> >> /var/lib/hudson/.ivy2/cache/org.grails.plugins/mail/zips/mail-1.0-SNAPSHOT.zip >> into >> /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT >> Installed plugin mail-1.0-SNAPSHOT to location >> >> /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT. >> ... >> Resolving plugin JAR dependencies ... >> :: problems summary :: >> :::: WARNINGS >> :::::::::::::::::::::::::::::::::::::::::::::: >> >> :: UNRESOLVED DEPENDENCIES :: >> >> :::::::::::::::::::::::::::::::::::::::::::::: >> >> :: >> org.springframework#org.springframework.test;3.0.5.RELEASE: >> configuration not found in >> org.springframework#org.springframework.test;3.0.5.RELEASE: 'master'. >> It was required from org.grails.internal#surfsesh;0.29 test >> >> :::::::::::::::::::::::::::::::::::::::::::::: >> >> >> Failed to install plugin [mail-1.0-SNAPSHOT]. Plugin has missing JAR >> dependencies. >> [delete] Deleting directory >> /var/lib/hudson/.grails/1.3.6/projects/workspace/plugins/mail-1.0-SNAPSHOT >> >> >> ---------- >> >> I think there is no way I can make Hudson ignore the warning, and I >> think I shouldn't even want to. >> >> What can be causing this issue? I see that the grails mail plugin >> specifies the following: >> >> dependencies { >> compile "javax.mail:mail:1.4.1" >> runtime >> "org.springframework:org.springframework.test:3.0.3.RELEASE" >> } >> >> I am surprised to see that the mail plugin requires the spring-test >> jar in runtime scope. Shouldn't that be 'test'? Does it have anything >> to do with the problem I am facing? >> >> Regards, >> Hans >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
On 03/03/2011 16:31, Vinny wrote:
> Ok, I see this relates to a mail I sent a little earlier. My question > is why would spring-test be a runtime dependency? > Is it ok to have it included in the production app? The grails template engine (which is used when you pass a model and view to sendMail) requires an HttpServletRequest to pass to the GSP. If there isn't an active request (e.g. in a background thread or anywhere else other than in the scope of a controller action) then it uses MockHttpServletRequest from spring-test. Ian -- Ian Roberts | Department of Computer Science [hidden email] | University of Sheffield, UK --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Ah, thanks for the explanation!
-- biz: http://www.linkedin.com/in/vincentstoessel/ personal: http://xaymaca.tumblr.com/ On Thu, Mar 3, 2011 at 11:38 AM, Ian Roberts <[hidden email]> wrote: > On 03/03/2011 16:31, Vinny wrote: >> Ok, I see this relates to a mail I sent a little earlier. My question >> is why would spring-test be a runtime dependency? >> Is it ok to have it included in the production app? > > The grails template engine (which is used when you pass a model and view > to sendMail) requires an HttpServletRequest to pass to the GSP. If > there isn't an active request (e.g. in a background thread or anywhere > else other than in the scope of a controller action) then it uses > MockHttpServletRequest from spring-test. > > Ian > > -- > Ian Roberts | Department of Computer Science > [hidden email] | University of Sheffield, UK > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Powered by Nabble | See how NAML generates this page |
