On 11 July 2012 12:05, Holger Knublauch <[email protected]> wrote: > Hi Jerven, > > our team is working on the Jena upgrade for TopBraid as we speak. I had made > the SPIN related stuff compile a few days ago, and now that the rest of our > system compiles I am continuing with the upgrade. > > One detail I noticed is that Jena has removed the system vocabulary > rdf-schema.rdf which we reference in the SystemTriples class. This may or > may not affect you, but I have moved that file into the SPIN API for the > next release. > > > On 7/10/2012 22:23, Jerven Bolleman wrote: >> >> Hi Holger, Peter, >> >> I was investigating the possibility to upgrade SPIN-API 1.2.0 to depend on >> Jena 2.7.2. And wanted to share my results. Holger, are you interested in >> working more publicly on the spin opensource part? (Copyright assignments >> are possibility etc...) and if so how would you like to proceed? > > > In general I appreciate your feedback and offer to help, and will do my best > to publish a working release soon. My hands are tied by the fact that the > SPIN API is part of the TopBraid code base on our private git repository. > This means I cannot simply decouple it easily. I am not a git power user, > but I guess one thing we could do together is to set up a clone of the SPIN > part of our library, and then I could synchronize changes to the public > version and you guys could contribute your changes into the public version > from where I could copy stuff over to the private one etc. But this sounds > hard and I am not in a position to spend a lot of time setting up the > infrastructure to make such a project layout possible. Note that our > org.topbraid.spin folder is not a top-level github project, but a folder > within a larger one. Not sure if this is a show stopper though. It would > certainly be useful to have a public open source project there with multiple > committers, also to build up a solid test case library. Right now the tests > that I have are mostly tied to the TopBraid infrastructure.
To extract the full history for the spin-api folder to a new repository you can use this guide that I have used successfully before [1]. Once you have extracted the tree to a new repository you can put it back into the original git repository as a submodule [2], which works roughly the same way as svn externals work if you are familiar with those. Cheers, Peter [1] https://help.github.com/articles/splitting-a-subpath-out-into-a-new-repo [2] http://git-scm.com/book/en/Git-Tools-Submodules -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
