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…
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=0fed2dc6-4671-4072-ba8e-4c2e72b92b1f)
A little off topic, but I was surprised to hear you say Eclipse’s Maven integration is “very good”. We had to abandon the Maven plugin here because it was so buggy about a 9 months ago. We use “mvn eclipse:eclipse” exclusively (except for those using IntelliJ, which “just works”.)
One aspect that needs consideration is the project scope/size. often projects grow and are never pruned or curated into separate manageable builds. When our IDE tools begin to suffer (symptom) we blame them, ignoring the root cause (monolithic code base).
Could you let me know the plugin used for Maven Integration with Eclipse?
Sandy, it’s the sonatype maven integration for eclipse at http://m2eclipse.sonatype.org/update/index.html
I just started with maven.
How would you add Pellet to such a project?
see http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html