Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

NB PoWeR: a repository of ready-to-use NetBeans Platform Wrapper libraries

DZone's Guide to

NB PoWeR: a repository of ready-to-use NetBeans Platform Wrapper libraries

· Java Zone ·
Free Resource

The CMS developers love. Open Source, API-first and Enterprise-grade. Try BloomReach CMS for free.

This is a very short post and it's mainly aimed in getting feedbacks from the NetBeans Platform Community. As part of a bigger move in refactoring my projects and having my code more easily reusable by others, I've created an *experimental* project, named the NetBeans Platform Wrapper Repository. As the name says, it's a (Maven) repository of pre-made wrappers for some common open source libraries around. It's experimental because it's primarily serving my own needs, but we could even create an officialy resource backed by the community. On that purpose, feedback is required since there is a lot of details to fix, and they depend on how people work with the Platform.

The project is hosted here: http://kenai.com/projects/nbpwr/ - I'm preparing a screencast to demonstrate how I'm using it, but it won't be ready before next week since I'm now focused on a talk at next saturday's JavaDay in Verona.

But let's talk of it? Do you think it would be useful? Would you use it in your projects, once it is completed? How do you use wrapper libraries in your project?

PS The thing is now focused on Maven, because it's one of the easiest ways to share artifacts, but can be used as well from Ant, by manually downloading .nbm files or even using Ivy.

BloomReach CMS: the API-first CMS of the future. Open-source & enterprise-grade. - As a Java developer, you will feel at home using Maven builds and your favorite IDE (e.g. Eclipse or IntelliJ) and continuous integration server (e.g. Jenkins). Manage your Java objects using Spring Framework, write your templates in JSP or Freemarker. Try for free.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}