Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Prerequisites

You will have to successfully obtain the dcm4jboss-all collection of dcm4chee modules from CVS:

cvs -d:pserver:anonymous@dcm4che.cvs.sourceforge.net:/cvsroot/dcm4che login
cvs -z3 -d:pserver:anonymous@dcm4che.cvs.sourceforge.net:/cvsroot/dcm4che co -P dcm4jboss-all

Once you have done that, you need to build the software. At this point you're ready to start setting things up Eclipse.

Importing dcm4chee projects into Eclipse

1: Prep the workspace

It is recommended that you have an Eclipse workspace dedicated to dcm4che, since dcm4che may have different JVM and code formatting settings, as well as different classpath variables than your other projects.

Assuming you are starting with a clean workspace, import the code formatting settings from this wiki. Download the Eclipse settings (java-conventions-without-tabs.xml) which are attached to the Coding Standards page. In Eclipse, click on Windows, Preferences, and then navigate to the Java/Code Style/Formatter section. Click on Import, and select the java-conventions-without-tabs.xml file. Click on OK to make these your active formatting settings.

2: Set up classpath variables

Set up the following classpath variables within Eclipse. Click on Windows, Preferences, and then navigate to the Java/Build Path/Classpath Variables section.

Variable Name

Path

JBOSS_HOME

The path to the root directory of your JBoss 4.0.5 GA installation. For example; C:/apps/jboss-4.0.5.GA

FOP_HOME

The path to the root directory of your FOP installation. For example; C:/apps/fop-0.20.5.

CACTUS_HOME

The path to the root directory of your Cactus (J2EE testing framework) installation. For example; C:/apps/jakarta-cactus-13-1.7.

3: Import the dcm4chee projects

Click on File, Import, select Existing Projects into Workspace, and then click Next. With the "Select root directory" radio button selected, click on Browse, and then navigate to your dcm4jboss-all directory. Select this directory, and click OK. You should see the list box populated with the nine core dcm4chee projects. Click on the Finish button.

4: Adding the dcm4che2 audit module

At this point, you'll probably notice that some of your projects have errors within them. This is because dcm4chee depends on the dcm4che-audit source code module which resides within the dcm4che2 code base. You'll need to get that from CVS as well:

cvs -d:pserver:anonymous@dcm4che.cvs.sourceforge.net:/cvsroot/dcm4che login
cvs -z3 -d:pserver:anonymous@dcm4che.cvs.sourceforge.net:/cvsroot/dcm4che co -P dcm4che2

The above command will get the entire dcm4che2 code base. You'll need this, as you need to be able to run the Maven build in order to obtain the project dependencies. Follow the instructions on the dcm4che2 build wiki page in order to do this.

You'll then need to install the Maven 2 plugin for Eclipse. Add a new update site to Eclipse (Help/Software Updates/Find and Install/Search for new features to install) with the name "Maven 2 Update Site" and a URL of http://m2eclipse.codehaus.org/, and install the plugin. Once you've installed the plugin, update your Local Repository Folder within the plugin settings (Window/Preferences/Maven2). The local Maven repository should be in your user home directory. For example, on Windows mine is set to C:\Documents and Settings\damien\.m2\repository.

Once you have the Maven 2 Eclipse plugin installed and configured, you'll be able to cleanly import the dcm4che-audit code. Click on File, Import, select Existing Projects into Workspace, and then click Next. With the "Select root directory" radio button selected, click on Browse, and then navigate to your dcm4che-audit directory. Select this directory, and click OK.

At this point, you should have 10 projects within your workspace, and no errors.

Running dcm4chee from within Eclipse

Option 1: Remote debugging of a local installation

Option 2: Launch dcm4chee from within Eclipse



This page has been viewed

Unknown macro: {tracking-info}

zero

times.

  • No labels