When i deleted the work folder in virgo all together,restarted the server,and then tried to deploy the same bundle,I got the following error

Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'hello-world' at version '1.0.0': A library with the name 'org.springframework.spring' and a version within the range '[3.0.5.RELEASE, 3.0.5.RELEASE]' could not be found
at org.eclipse.virgo.kernel.userregion.internal.importexpansion.ImportExpansionHandler.createExceptionForMissingLibrary(ImportExpansionHandler.java:184)
at org.eclipse.virgo.kernel.userregion.internal.importexpansion.ImportExpansionHandler.getLibraryPackageImports(ImportExpansionHandler.java:451).

My LIBD file is present in the same location as it was (virgo/repository/ext).

I am puzzled by seeing this error.If I use Import-Bundle directly instead of library it worked properly.

at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpandingTransformer.expandImports(ImportExpandingTransformer.java:116)

at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpandingTransformer$ImportExpandingTreeVisitor.visit(ImportExpandingTransformer.java:80)

at org.eclipse.virgo.util.common.ThreadSafeArrayListTree.visit(ThreadSafeArrayListTree.java:165)

at org.eclipse.virgo.kernel.deployer.core.internal.ImportExpandingTransformer.transform(ImportExpandingTransformer.java:58)

at org.eclipse.virgo.kernel.install.pipeline.stage.transform.internal.TransformationStage.doProcessTree(TransformationStage.java:55)

at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)

at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessTree(StandardPipeline.java:62)

at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessTree(CompensatingPipeline.java:72)

at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)

at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessTree(StandardPipeline.java:62)

at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:285)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:164)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:136)

at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:203)

at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeploymentFileSystemListener.java:174)

at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.deployIfNotDeployed(HotDeploymentFileSystemListener.java:186)

at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeploymentFileSystemListener.java:87)

at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:245)

at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:166)

at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTask.java:58)

at java.lang.Thread.run(Thread.java:662)

Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'datasource' at version '1.0.0.SNAPSHOT': A library with the name 'org.springframework.spring' and a version within the range '[3.0.5.RELEASE, 3.0.5.RELEASE]' could not be found

at org.eclipse.virgo.kernel.userregion.internal.importexpansion.ImportExpansionHandler.createExceptionForMissingLibrary(ImportExpansionHandler.java:184)

This is strange and unexpected. I presume you can re-create this problem when starting Virgo from the command line with the -clean switch (rather than starting Virgo in Eclipse)? If so, I wonder if you could try to recreate the issue with a fresh install of Virgo and a trivial bundle which simply imports the Spring library. If the problem re-creates, you could then raise a bug which we could look at.

I was intrigued, so I tried to re-create the problem. I unzipped and started VTS 3.0.1.RELEASE, deployed a test bundle containing only the following manifest, stopped Virgo, deleted the work directory, and then re-started Virgo. The test bundle was successfully deployed, as expected. Perhaps you have modified the repository configuration?