Skip to main content
Jump to: navigation, search

Stardust/Knowledge Base/Build and Change Management/Maven/Basic Setup

Maven Repository Configuration

While we are packaging up Stardust for Eclipse, you can get free access to the Infinity Process Platform - the product Stardust originates from. After you followed the instructions on how to gain access to the Maven Repository, you can authenticate against the ipp-libs repository with the username and password you picked when registering. Further repositories Stardust builds may require are Maven Central, and Jboss public. To access these repositories from Maven make sure they are configured in your Maven settings.xml as shown below.

Also configure the correct credentials for the ipp-libs repository as shown here:

If you don't want to specify your password in clear text, you can encode it in the repository web portal:

  1. Go to Repository and login using your credentials
  2. Go to your user profile (link behind user name in upper right corner)
  3. Enter your password and press the Unlock button
  4. Copy the username and password section into your settings.xml as shown above

Other helpfull repositories could be ibiblio or the Nuxeo Apache repository

Stardust Maven Archetypes

Available Archetypes

Starting from version 6.0.3 the ipp-libs Maven repository ( contains Maven archetypes

( that can be use to create the following Maven projects:

  • Engine runtime EAR project for JBOSS 5.1, EJB deplyoment, artefactId=ipp-archetype-jb51-ipp-ear
  • Engine runtime WAR project for JBOSS 5.1, Spring deplyoment, artefactId=ipp-archetype-jb51-ipp-portal-war
  • Reporting runtime WAR project for JBOSS 5.1, artefactId=ipp-archetype-jb51-reporting-war
  • Engine runtime WAR project for Tomcat 6, Spring deployment, artefactId=ipp-archetype-tc6-ipp-portal-war
  • Reporting runtime WAR project for Tomcat 6, artefactId=ipp-archetype-tc6-reporting-war
  • Console command line tool client environment project, Spring client, artefactId=ipp-archetype-console-spring-client
  • Sysconsole command lient tool client environment project (direct database access via JDBC), artefactId=ipp-archetype-sysconsole-client

For other application servers the example project coming closest to the target deployment can be adjusted. Additional archetypes for other deployment scenarios will be added soon.

  • The repository ipp-community-releases already contains a beta version of the Weblogic Spring WAR archetype. Due to the WLS license restrictions this archetype requires the property wlfullclient.dir to be supplied as a parameter. The value should be the WLS folder in which the JAR wlfullclient.jar can be found.

The goals dependency:unpack (for runtimes) / generate-resources (for console and sysconsole) have to be executed after the corresponding projects have been successfully created. However, project creation and goal execution can be combined in one command by appending a -Dgoals parameter as shown in the examples below.

Example Usage

If the repository is not configured in your settings.xml then you have to supply the repository URL as an additional parameter to the mvn command:



mvn archetype:generate 
-DarchetypeGroupId=com.infinity.bpm.archetypes -DarchetypeArtifactId=ipp-archetype-tc6-ipp-portal-war
-DarchetypeVersion=6.0.3 -DgroupId=org.eclipse.stardust.test -DartifactId=stardust-portal-war -Dversion=1.0-SNAPSHOT

Command Line

mvn archetype:generate
-DarchetypeGroupId=com.infinity.bpm.archetypes -DarchetypeArtifactId=ipp-archetype-console-spring-client
-DarchetypeVersion=6.0.3 -DgroupId=org.eclipse.stardust.test -DartifactId=stardust-console -Dversion=1.0-SNAPSHOT

M2 Eclipse Plugin


The Maven Eclipse plugin is extremely helpful when working with maven projects under eclipse. It

  • allows you to create and import Maven projects
  • includes a form-based POM Editor
  • manages dependencies and integrates them with the Eclipse classpath
  • automatically downloads and updates dependencies
  • resolves artifact Javadoc and source
  • creates projects based on Maven archetypes
  • supports browsing and searching of remote and local Maven repositories
  • manages POMs with automatic updates to the dependency list
  • adapts nested multi-module Maven projects to the Eclipse IDE
  • provides integration with the Web Tools Project (WTP)
  • integrates with Subclipse and Mylyn
  • generates graphical displays of the dependency graph
  • allows to run maven goals from the IDE
  • ...

You can learn more about the plugin here: In Eclipse Helios (3.6) the plugin is not yet part of the distribution, but you can install it from the Eclipse marketplace. Installation instructions can be found here:

Stardust Archetype Catalog Configuration

Please make sure your M2 Eclipse uses a properly configured Maven version as described in the Troubleshooting section.

Remote Archetype Catalog

Before you can use the Stardust Archetype Catalog with M2 Eclipse you need to configure the catalog initially. When creating a new Maven project with M2 Eclipse you will be present with the archetype selection dialog.


Local Archetype Catalog

You can also add the Stardust archetype catalog as a local catalog to M2Eclipse.

Creating a local Stardust Archetype Catalog in M2 Eclipse

Browsing the local Stardust Archetype Catalog in M2 Eclipse


  • Remember to run dependency:unpack / generate-resources goal

If you experience problems related to missing files like e.g. sun-jaxws.xml then you may have forgotten to run the goal dependency:unpack.

If you want to use the command line tools console or syconsole and cannot find the bat / sh files then you may have forgotten to run the goal generate-resources.

  • Make sure you are using the right Maven installation / settings.xml and have configured the credentials properly

If you experience any problems in using the Stardust archetype catalog or in building maven projects using M2 Eclipse, then this may be cause by the fact that your M2 Eclipse is  configured to use the embedded Maven version that ships with it. Unless you configured it accordingly this Maven version uses another settings.xml which does not contain the credentials and repositories required to access the archetype catalog and the artifacts in the repository.


An easy solution is to change the Maven version used by M2 Eclipse to a correctly configured Maven version (Probably you have a Maven version which you use outside Eclipse which is configured correctly).


Back to the top