Prerequisites
You will have to successfully obtain the dcm4jboss-all collection of dcm4chee modules from CVS:
| No Format |
|---|
| Wiki Markup |
h3. Prerequisites You will have to successfully obtain the {{dcm4jboss-all}} collection of dcm4chee modules from CVS: {noformat} 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 {noformat} Once you have done that, you need to [build the software|Building dcm4chee]. At this point you're ready to |
...
Importing dcm4chee projects into Eclipse
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.
...
start setting things up Eclipse. h3. Importing dcm4chee projects into Eclipse h4. Workspace Notes 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|proj:Coding Standards] from this wiki. Download the Eclipse settings ({{java-conventions-without-tabs.xml}}) which are attached to the [Coding Standards page|proj:Coding Standards]. 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. |
...
To be continued...
Set up classpath variables
Import the dcm4chee projects
Adding the dcm4che2/dcm4chee audit modules
Running dcm4chee from within Eclipse
Option 1: Remote debugging of a local installation
...
h4. 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}}.|
h4. 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|Organization of the Source Code]. Click on the Finish button.
h4. Adding the dcm4che2/dcm4chee audit modules (do we need this, or should the dcm4chee modules reference the dcm4che-audit jar file?)
h3. Running dcm4chee from within Eclipse
h4. Option 1: Remote debugging of a local installation
h4. Option 2: Launch dcm4chee from within Eclipse
\\
\\
This page has been viewed {tracking-info:value=view count}zero{tracking-info} times. |