Setting up a new project - Development

TODO

Modidy this to reflect the current procedure.

For each project:

Determine an appropriate parent project, e.g.

Create an archetype using "info.aduna" or "org.openrdf" as group ID and "aduna-<project>" as archetype ID. For example:

mvn archetype:create -DgroupId=info.aduna -DartifactId=aduna-myproject

Remove the default class and unit test.

Create a project folder in the SVN repository, e.g. "aduna-myproject" in "info/aduna". The repository URL to use is https://src.aduna-software.org/svn/info.aduna

Create a project space in Confluence, e.g. space name = aduna-myproject, space key = AMP. Make this space viewable for anonymous users.

Create a project in Jira using the name and key from the Confluence space.

Add source and resource files to your local tree (in src/main and src/test).

TODO

We should create an Aduna project archetype that takes care of the next two or three steps.

Add a LICENSE.txt and README.txt, you can copy these from any other Aduna Maven project.

Add a .settings dir in the root with the Eclipse settings files. These files are attached to this page.

Adapt the automatically created pom.xml file. Look at the other pom.xml files for examples. Let the pom.xml file refer to the created repository folder and project space. It's best to take the pom.xml file from the [aduna-util] project as a starting point as it is the most minimal one.

Test whether everything works ok by doing "mvn install" in the root dir.

Perform a "mvn eclipse:eclipse" to create the initial Eclipse .project and .classpath settings.

Perform a "mvn clean".

Commit these files (e.g. use TortoiseSVN's SVN import, you can safely import the entire tree when you've cleaned up in the previous step). Commit it to a URL of the following form: https://src.aduna-software.org/svn/info.aduna/aduna-util (i.e., include the project name).

Import the project in Eclipse using the [Subclipse plugin].

For projects that have dependencies on other Aduna projects, we recommend removing the dependency on the corresponding JAR in M2_REPO and instead adding a dependency on the project in Eclipse.