The Web Semantic

This post describes how to make a maven repo for your google code project.  I’m a big fan of google code.  It’s a tremendous service for those looking for a place to host their open source code.  The only thing I lacked was a maven repo.  I have to be honest here, while I use maven, it’s still a big mystery to me how things end up in the main maven repo.  If Google were to add one new feature, I’d prefer it be a maven repo and hudson build that autodiscovers maven projects and builds them…but we’re not there yet, so the question I’m going to answer is how you can provide a maven repo for your open source customers hosted on google code.   » Read the rest of this entry «

Recently on the Jena news group there was a question regarding classpath and how frustrating it can be to properly configure that aspect of a new project. I began to answer the question and realized I haven’t touched a classpath for years simply because the tools I use make that unnecessary. Eclipse is free and has very good maven integration. At the same time, the Jena team is providing jena as a Maven asset indexed on the main maven repo. The consequences are that you can have eclipse create a new project for you, and add your library dependencies for you by simply declaring that your project “uses” jena.  Here is a quick screentoaster demo to get you going…