Gary Keim wrote: > We still do scanning but there was a place where it was scanning the entire > repo instead of filtering by the groupId. I'm fixing that. I think proper > scanning, based on groupId, is appropriate to allow for relaxed tie between > the bundle version and filename. I don't see when it would be necessary unless we'll allow inexplicit versions or version ranges, but it is been decided against that. > There's some desire to allow OSGi bundle > foo version 1.0.0.SNAPHOT to have archive file form foo-1.0-SNAPSHOT.jar. > That is an explicit mapping and there won't be 1.0.SNAPSHOT.jar in the repository, so it can be remapped directly.
By the way, For some reason BundleSpec.getVersion() can return strings like "1.0.0-SNAPSHOT" (with the quotes around). For example, they are passed to the Resolver.resolveBundle(BundleSpec spec) I added some code to strip those quotes in the maven plugin, but I saw complains that people are getting such errors when running kit: ERROR - Unable to locate bundle dependency: 'modules_common', version '"1.0.0.SNAPSHOT"', group-id 'org.terracotta.modules'; Tried to resolve the location using the following repositories: 'file:/Users/jeffgenender/Projects/geronimo/assemblies/geronimo-tomcat6-javaee5/target/geronimo-tomcat6-javaee5-2.1-SNAPSHOT/var/terracotta/modules;file:/Users/jeffgenender/Projects/geronimo/assemblies/geronimo-tomcat6-javaee5/target/geronimo-tomcat6-javaee5-2.1- regards, Eugene _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
