I do have groovy-all-1.7.5.jar in my maven2 repository under /home/ariskk/.m2/repository/org/codehaus/groovy/groovy-all/1 .7.5 and ofcourse I've configured virgo to scan the repository for bundles (this works because it finds other bundles)
Any ideas what might be wrong?
manifest.mf of groovy-all-1.7.5.jar:
The error msg:
Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundl eDependenciesException: Unable to satisfy dependencies of bundle 'com.rits.groovy' at ver
sion '1.0.0': Import-Bundle with symbolic name 'groovy-all' in version range '[1.7.5, 2.0.0)' could not be satisfied
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.getBundlePackageImports(ImportExpans ionHandler.java:271)
at org.eclipse.virgo.kernel.userregion.internal.importexpansion .ImportExpansionHandler.getAdditionalPackageImports(ImportEx pansionHandler.java:236)
require-bundle has several semantic "rough edges" compared to import-bundle (which is really syntactic sugar for a bundle of package imports). So it *might* be something do so with that difference.
But this seems very odd and may be a bug.
Please could you raise a bugzilla against Virgo and ideally attach a simple testcase which reproduces the problem. groovy-all is probably too large to attach, so a URL will do fine. If you can eliminate all extraneous dependencies and make this fail with groovy-all in repository/usr, that will simplify analysis of the bug considerably.
Often we find that in doing that kind of simplification, users find the source of the problem themselves, often in application code, so I would be grateful if you could have a go.