Some more thoughts: - The probllem with having the identical version number as the wrapped jar is taht if we release the bundles we will (n+1)-SNAPSHOT versions in trunk that wrap the artifact versioned n. And it's going to be a mess is need to release a new bundle for the same wrapped version (say we forgot an export or so). I think this problem is solved by adding a _1 to the version number.
- I think the base of artifact ID should be the original groupId:Artifactid (unless the artifactId already contains the groupId) I hope it's OK that I committed this changes and added the new bundles to the launcher. Cheers, Reto On Sat, Sep 21, 2013 at 10:39 PM, Reto Bachmann-Gmür <[email protected]>wrote: > Hi Minto > > <dependency> >> <groupId>org.apache.servicemix.bundles</groupId> >> <artifactId>src-assembly</artifactId> >> <version>1.0</version> >> </dependency> >> >> I guess we want to get rid of this dependency as well, by creating our >> own. I will copy the src-assembly from service mix. >> > > There is no problem depending on some servicemix dependencies. Here I just > don't see what this is needed for, i.e. why a special source assembly is > needed for the ext-projects. > > Also I notice that the bundles parent was not part of the bundles reactor > and that it did not inherit from the clerezza parent. Hope it's OK that I > changed this (under your issue). > > Now the next step is to try the tdb launcher out with the new bundles.... > > Cheers, > Reto > > > On Fri, Sep 20, 2013 at 10:27 AM, Minto van der Sluis <[email protected]> > wrote: > > > >> Hi folks, > >> > >> I just committed my work on the lean Apache jena ext wrappers. Please > >> have a close look. The ext bundles can be found in the newly created ext > >> folder. > >> > >> Now I wonder how to continue with these new/ServiceMix style wrappers. I > >> have the following questions: > >> > >> 1. Wrapper hosting. > >> Do we want to host/own these wrappers our selves or donate it to > >> ServiceMix. From what I read ServiceMix bundles are open for others to > >> donate wrappers. See > >> http://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/ > >> > >> 2. Wrapper versioning > >> When we decide to host ext wrappers ourselves then we should decide on > >> versioning these wrappers as well. Do we need separate wrappers for > >> separate version like ServiceMix has. For instance jena-core-2.10.0, > >> jena-core-2.10.1, jena-core-2.11.0, ... Personally I think we do not > >> need this. Once a version is release it could be tagged or branched in > >> svn (requires a change to what's currently committed). Also I think that > >> within Clerezza we should stick to using a single version as much as > >> possible. > >> > >> 3. How to test within Clerezza > >> Since I only use part of Clerezza (rdf abstraction layer + jena > >> storage). I don't know how to test if these new wrappers work inside > >> clerezza as well. I could start with running all unittests. But I am > >> more concerned about the various launchers. How do I test if these still > >> work. > >> > >> What remains to be done: > >> - remove the old ext jena wrappers (jena and jena.tdb) > >> - preferably use the ServiceMix style for all other ext bundles as well. > >> - modify launchers/bundlelists to use the new ext wrappers (also add > >> required dependencies) > >> > >> Please let me know what you guys think. > >> > >> Regards, > >> > >> Minto > >> > > > -- >> ir. ing. Minto van der Sluis >> Software innovator / renovator >> Xup BV >> >> Mobiel: +31 (0) 626 014541 >> >> >
