On 9/29/10 12:59, [email protected] wrote:
All, When attempting to deploy dom4j as part of a Hibernate 3 feature, I get the following error: Error executing command: Could not start bundle mvn:org.dom4j/com.springsource.org.dom4j/1.6.1 in feature(s): Unresolved constraint in bundle com.springsource.org.dom4j [59]. Unable to acquire global lock for resolve. When attempting to deploy the feature a second time it resolves. However, in another feature for jdbc, no matter how many times I attempt to deploy the feature, the global lock never resolves. Can anyone give me feedback about why this is happening?
This is a recent change to try to deal with potential deadlocks. Typically, this situation arises when people are trying to do refreshes and resolves at the same time. It shouldn't occur if you are just trying to resolve bundles.
If you have a reproducible scenario, open up a JIRA issue and describe the precise steps to reproduce and I can take a closer look.
-> richard
v/r, Mike Van
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
