2009-07-14T19:42:33Z
3868
Home
11
4904
= NetBeans Platform Wrapper Repository =
The NetBeans Platform Wapper Repository (NB PoWeR) is an experimental approach to creare a Maven repository of NBM wrapper modules for some commonly used open source libraries. The idea is to have artifacts that are ready to be included in a custom platform by just declaring their dependencies in a Maven pom.
The project is '''still experimental''' and not yet open to third parties' contributions (while feedback is always welcome). The idea is to move through this sequence of phases:
# The project is being lead by Fabrizio Giudici, who's got a number of Platform based projects. In Phase One, all the existing wrappers from these projects are being moved to NB PoWeR. For the sake of continuity, the currently used version are being imported (they are not necessarily the latest version of each library) and existing incongruousness in the naming schemata are '''not''' being corrected. This first phase is being performed mostly manually and will terminate when all the wrappers have been imported and the applications that use them work correctly.
# In Phase Two, a review of name schemata and other related issues will be performed, probably with the intervention of other people. A number of issues about the effective capability of reusing a .NBM will be addressed in this phase.
# In Phase Three, if everything goes fine, the project will be opened and become useful for people.
== Current status ==
Currently, we are running Phase One. At this stage, it's unlikely that the repository will be scratched (as it happened at the very beginning) so you can (experimentally) depend on it. You can put this configuration in your POM for accessing artifacts at NBPWR:
<repositories>
<repository>
<id>maven2-release-repository.nbpwr.kenai.com</id>
<name>NBPWR Maven Release Repository</name>
<url>http://nbpwr.kenai.com/maven-repository/releases</url>
</repository>
</repositories>
All the available artifacts have a groupId set to '''com.kenai.nbpwr'''; the artifactId is usually the same of the original artifact with dashes in place of dots; the version number has got an additional digit that represents the NBPWR version (e.g. because of a bug in declaring public packages it might be necessary to release a new wrapper of the same original artifact).
This is an example of how to refer a few of the existing artifacts from a POM:
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-jdesktop-beansbinding</artifactId>
<version>1.2.1.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-apache-commons-dbcp</artifactId>
<version>1.2.2.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-apache-commons-pool</artifactId>
<version>1.4.3</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>com-eaio-uuid</artifactId>
<version>2.1.5.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>gov-nasa-worldwind</artifactId>
<version>0.5.4</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>net-java-nativelibsupport</artifactId>
<version>0.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-xml-bind</artifactId>
<version>2.1.7</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-annotation</artifactId>
<version>1.3.7.3</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-persistence</artifactId>
<version>1.0.30</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javassist</artifactId>
<version>3.7.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-slf4j</artifactId>
<version>1.5.0.4</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>com-sun-gluegen</artifactId>
<version>1.0.6</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-media-opengl</artifactId>
<version>1.1.1.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-swinglabs-swingx</artifactId>
<version>1.6.0.0</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-swinglabs-swingx-ws</artifactId>
<version>0.20091104.1</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-openrdf</artifactId>
<version>2.2.3.6</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-openrdf-elmo</artifactId>
<version>1.4.7</version>
</dependency>
<h1><a name='NetBeans_Platform_Wrapper_Repository'></a> NetBeans Platform Wrapper Repository </h1>
<p>
The NetBeans Platform Wapper Repository (NB PoWeR) is an experimental approach to creare a Maven repository of NBM wrapper modules for some commonly used open source libraries. The idea is to have artifacts that are ready to be included in a custom platform by just declaring their dependencies in a Maven pom.
</p><p>The project is <b>still experimental</b> and not yet open to third parties' contributions (while feedback is always welcome). The idea is to move through this sequence of phases:
</p><ol><li> The project is being lead by Fabrizio Giudici, who's got a number of Platform based projects. In Phase One, all the existing wrappers from these projects are being moved to NB PoWeR. For the sake of continuity, the currently used version are being imported (they are not necessarily the latest version of each library) and existing incongruousness in the naming schemata are <b>not</b> being corrected. This first phase is being performed mostly manually and will terminate when all the wrappers have been imported and the applications that use them work correctly.
</li></ol><ol><li> In Phase Two, a review of name schemata and other related issues will be performed, probably with the intervention of other people. A number of issues about the effective capability of reusing a .NBM will be addressed in this phase.
</li></ol><ol><li> In Phase Three, if everything goes fine, the project will be opened and become useful for people.
</li></ol><h2><a name='Current_status'></a> Current status </h2>
<p>
Currently, we are running Phase One. At this stage, it's unlikely that the repository will be scratched (as it happened at the very beginning) so you can (experimentally) depend on it. You can put this configuration in your POM for accessing artifacts at NBPWR:
</p><pre> <repositories>
<repository>
<id>maven2-release-repository.nbpwr.kenai.com</id>
<name>NBPWR Maven Release Repository</name>
<url><a class='external' href="http://nbpwr.kenai.com/maven-repository/releases">http://nbpwr.kenai.com/maven-repository/releases</a></url>
</repository>
</repositories>
</pre><p>
All the available artifacts have a groupId set to <b>com.kenai.nbpwr</b>; the artifactId is usually the same of the original artifact with dashes in place of dots; the version number has got an additional digit that represents the NBPWR version (e.g. because of a bug in declaring public packages it might be necessary to release a new wrapper of the same original artifact).
</p><p>This is an example of how to refer a few of the existing artifacts from a POM:
</p><pre> <dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-jdesktop-beansbinding</artifactId>
<version>1.2.1.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-apache-commons-dbcp</artifactId>
<version>1.2.2.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-apache-commons-pool</artifactId>
<version>1.4.3</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>com-eaio-uuid</artifactId>
<version>2.1.5.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>gov-nasa-worldwind</artifactId>
<version>0.5.4</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>net-java-nativelibsupport</artifactId>
<version>0.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-xml-bind</artifactId>
<version>2.1.7</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-annotation</artifactId>
<version>1.3.7.3</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-persistence</artifactId>
<version>1.0.30</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javassist</artifactId>
<version>3.7.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-slf4j</artifactId>
<version>1.5.0.4</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>com-sun-gluegen</artifactId>
<version>1.0.6</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>javax-media-opengl</artifactId>
<version>1.1.1.5</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-swinglabs-swingx</artifactId>
<version>1.6.0.0</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-swinglabs-swingx-ws</artifactId>
<version>0.20091104.1</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-openrdf</artifactId>
<version>2.2.3.6</version>
</dependency>
<dependency>
<groupId>com.kenai.nbpwr</groupId>
<artifactId>org-openrdf-elmo</artifactId>
<version>1.4.7</version>
</dependency>
</pre>
2009-11-22T10:38:39Z
21384