From the user list. Emails pasted below:
Please ignore my previous email. This does appear to be a breaking
When one of our many inline plugins has this occur, it causes that
particular plugin's dependencies to not get picked up by the build
system. As this particular plugin is the one that pulls in various
outside libs like javax.jms, etc. it causes a build failure on other
inline plugins that depend on this one.
inline plugin A has dependencies on javax.jms, etc.
inline plugin B has dependency on plugin A
When A has this issue occur plugin B will fail to find A's dependencies
and the build will break.
I will open a JIRA and take a look this weekend at the Grails code to
see if I can figure out how this breaks. It appears to be random and the
plugin failure message hits all of our inline plugins although any
particular plugin fails randomly. No pattern I can see.
From: Stokes, Chris
Sent: Monday, February 22, 2010 3:04 PM
Subject: RE: [grails-user] Intermittent dependency resolution failures
We see this a lot here during our continuous integration and developer
We cannot pin down the cause and so far it does not appear to be a
From: Robert Fletcher
Sent: Monday, February 22, 2010 9:52 AM
Subject: [grails-user] Intermittent dependency resolution failures
Does anyone else see this? Every once in a while when running a Grails
command I see the message:
WARNING: Dependencies cannot be resolved for plugin
[selenium-rc-1.0-SNAPSHOT] due to error: null
The plugin varies, but the result is often that compilation or
execution fails because a class is not found. If I just re-run the
command it works fine.