While we are packaging up Stardust for Eclipse, you can get free access to the Infinity Process Platform - the product Stardust originates from.&nbsp;After you followed the instructions on how to [http://www.eclipse.org/stardust/download/download.php 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, Java.net and Jboss public. To access these repositories from Maven make sure they are configured in your Maven settings.xml as shown below.

+

For Stardust builds add the following repositories to your settings.xml:

Other helpful repositories could be ibiblio [http://www.ibiblio.org/maven http://www.ibiblio.org/maven] or the Nuxeo Apache repository [http://maven.nuxeo.org/nexus/content/groups/public http://maven.nuxeo.org/nexus/content/groups/public].<br>

+

+

== Maven Archetypes ==

+

+

==== Stardust Archetypes ====

+

+

'''Runtime'''

+

+

*tc6-ipp-portal-war - Stardust Spring WAR deploment for Tomcat<br>

+

+

'''Commandline Tools'''

+

+

*console-client - creates a Spring based console environment.

+

*sysconsole-client - creates a sysconsole client environment.

+

+

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:

While we are working on providing all available archetypes for Stardust, you can get free access to the Infinity Process Platform - the product Stardust originates from.&nbsp;After you followed the instructions on how to [http://www.eclipse.org/stardust/download/download.php gain access] to the IPP Maven Repository, you can authenticate against the ''ipp-libs'' repository with the username and password you picked when registering. Further repositories builds may require are: Maven Central, Java.net and JBoss public. To access these repositories from Maven make sure they are configured in your Maven settings.xml as follows.

+

+

<u>'''Repositories'''</u>

<source lang="XML">

<source lang="XML">

Line 45:

Line 116:

#Copy the username and password section into your settings.xml as shown above

#Copy the username and password section into your settings.xml as shown above

*ipp-archetype-jb51-ipp-portal-war - prepares a WAR deployment for JBoss 5.1.

+

*ipp-archetype-jb51-reporting-war - prepares a Reporting WAR deployment for JBoss 5.1.

−

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.<br>

+

'''Tomcat 6'''

−

It is important to execute the goal '''''dependency:unpack'''''&nbsp; after the project has been created. This can be automated by using the '''''-Dgoals''''' parameter when the project is created.<br>

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.

+

+

'''Websphere 7'''

+

+

*ipp-archetype-was7-ipp-ear - prepares an EAR deployment for WebSphere 7 and provides a console environment for EJB.

+

*ipp-archetype-was7-ipp-portal-war - prepares a WAR deployment for WebSphere 7.

+

*ipp-archetype-was7-reporting-war - prepares a Reporting WAR deployment for WebSphere 7.

+

+

'''Websphere 8'''

+

+

*ipp-archetype-was8-ipp-ear - prepares an EAR deployment for WebSphere 8 and provides a console environment for EJB.

+

*ipp-archetype-was8-ipp-portal-war - prepares a WAR deployment for WebSphere 8.

+

*ipp-archetype-was8-reporting-war - prepares a Reporting WAR deployment for WebSphere 8.

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.<br>

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

+

==== Introduction<br> ====

−

*allows you to create and import Maven projects

+

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

−

*includes a form-based POM Editor

+

−

*manages dependencies and integrates them with the Eclipse classpath

+

*allows you to create and import Maven projects

−

*automatically downloads and updates dependencies

+

*includes a form-based POM Editor

−

*resolves artifact Javadoc and source<br>

+

*manages dependencies and integrates them with the Eclipse classpath

−

*creates projects based on Maven archetypes

+

*automatically downloads and updates dependencies

−

*supports browsing and searching of remote and local Maven repositories

+

*resolves artefact Javadoc and source<br>

−

*manages POMs with automatic updates to the dependency list<br>

+

*creates projects based on Maven archetypes

−

*adapts nested multi-module Maven projects to the Eclipse IDE

+

*supports browsing and searching of remote and local Maven repositories

−

*provides integration with the Web Tools Project (WTP)

+

*manages POMs with automatic updates to the dependency list<br>

−

*integrates with Subclipse and Mylyn<br>

+

*adapts nested multi-module Maven projects to the Eclipse IDE

−

*generates graphical displays of the dependency graph<br>

+

*provides integration with the Web Tools Project (WTP)

−

*allows to run maven goals from the IDE

+

*integrates with Subclipse and Mylyn<br>

+

*generates graphical displays of the dependency graph<br>

+

*allows to run maven goals from the IDE

*...

*...

−

You can learn more about the plugin here:&nbsp;[http://www.sonatype.com/books/m2eclipse-book/reference/ http://www.sonatype.com/books/m2eclipse-book/reference/]. 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: [http://www.sonatype.com/books/m2eclipse-book/reference/install-sect-marketplace.html http://www.sonatype.com/books/m2eclipse-book/reference/install-sect-marketplace.html]

+

You can learn more about the plugin here:&nbsp;[http://www.sonatype.com/books/m2eclipse-book/reference/ http://www.sonatype.com/books/m2eclipse-book/reference/].<br>

+

+

==== Installation ====

+

+

In Eclipse Kepler and higher versions the plugin can be installed via the Eclipse marketplace.

+

+

Installation instructions for Eclipse helios can be found here: [http://www.sonatype.com/books/m2eclipse-book/reference/install-sect-marketplace.html http://www.sonatype.com/books/m2eclipse-book/reference/install-sect-marketplace.html]<br>

+

+

Apart from the required M2E plugin it is recommended to additionally install the optional "Maven Integration for WTP" plugin from the M2E Extras section.

+

+

The following update sites have been proven to work well with Eclipse Helios 3.6:

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

+

+

'''Remote Archetype Catalog'''<br>

+

+

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.

+

+

*Click the ''Configure ''button next to the catalog selection box.<br>

+

*Use the ''Add Remote Catalog ''button to add a catalog from a location on the web.<br>

*Configure a local catalog as illustrated in the screenshots below.<br>

+

+

[[Image:M2EclipseCreateLocalCatalog.gif|Creating a local Stardust Archetype Catalog in M2 Eclipse]]<br>

+

+

<br>

+

+

[[Image:M2EclipseBrowseLocalStardustCatalog.jpg|Browsing the local Stardust Archetype Catalog in M2 Eclipse]]<br>

+

+

<br>

+

+

== Troubleshooting ==

+

+

*'''Add wagon-http Jar if you are using Maven 3.0.4 behind a Proxy '''<br>

+

+

Maven 3.0.<u>4</u> has a [http://jira.codehaus.org/browse/MNG-5237 bug] preventing it from downloading dependencies from behind a proxy. An error starting with ''"Failed to retrieve plugin descriptor …''" will appear. Either switch to Maven 3.0.<u>3</u> or download [[Repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-lightweight/2.2/wagon-http-lightweight-2.2.jar|repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-lightweight/2.2/wagon-http-lightweight-2.2.jar]] and add it to Maven's ''\lib\ext'' sub folder.<br>

+

+

*'''Check if the repository password or password hash in your setting.xml is up-to-date'''<br>

+

+

If your password hash is outdated then Maven unfortunately won't display an meaningful error message. It will simply not download the artifacts from the repository. Instead Maven will try to fetch the artifacts from the other configured repositories. Finally the build will fail with an error message indicating that the artifact could not be downloaded. Log into the repository web app, click on your name and generate a new password hash. Then update the password hash in your settings.xml with the new value.

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.<br>

+

+

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

+

+

*'''Make sure you are using the right Maven installation / settings.xml and have configured the credentials properly'''<br>

+

+

If you experience any problems in using the Stardust archetype catalog or in building maven projects using M2 Eclipse, then this may be due to 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.<br>

+

+

[[Image:M2EclipseCouldNotFindArchetype.gif]]

+

+

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).

The goalsdependency: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:

Other Archetypes

While we are working on providing all available archetypes for Stardust, 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 IPP Maven Repository, you can authenticate against the ipp-libs repository with the username and password you picked when registering. Further repositories builds may require are: Maven Central, Java.net and JBoss public. To access these repositories from Maven make sure they are configured in your Maven settings.xml as follows.

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.

Websphere 7

ipp-archetype-was7-ipp-ear - prepares an EAR deployment for WebSphere 7 and provides a console environment for EJB.

ipp-archetype-was7-ipp-portal-war - prepares a WAR deployment for WebSphere 7.

ipp-archetype-was7-reporting-war - prepares a Reporting WAR deployment for WebSphere 7.

Websphere 8

ipp-archetype-was8-ipp-ear - prepares an EAR deployment for WebSphere 8 and provides a console environment for EJB.

ipp-archetype-was8-ipp-portal-war - prepares a WAR deployment for WebSphere 8.

ipp-archetype-was8-reporting-war - prepares a Reporting WAR deployment for WebSphere 8.

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.

M2 Eclipse Plugin

Introduction

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 artefact Javadoc and source

creates projects based on Maven archetypes

supports browsing and searching of remote and local Maven repositories

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.

Click the Configure button next to the catalog selection box.

Use the Add Remote Catalog button to add a catalog from a location on the web.

Check if the repository password or password hash in your setting.xml is up-to-date

If your password hash is outdated then Maven unfortunately won't display an meaningful error message. It will simply not download the artifacts from the repository. Instead Maven will try to fetch the artifacts from the other configured repositories. Finally the build will fail with an error message indicating that the artifact could not be downloaded. Log into the repository web app, click on your name and generate a new password hash. Then update the password hash in your settings.xml with the new value.

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 sysconsole 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 due to 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).