Dashboard > dcm4chee-2.x > Home > Building dcm4chee
Building dcm4chee Log In | Sign Up   View a printable version of the current page.

Added by Damien Evans , last edited by Damien Evans on Jun 14, 2008  (view change)
Labels: 
(None)

Build Requirements

In order to build the components of the dcm4chee archive application you will need to download and install:

In addition, you'll need the dcm4chee source code. In order to create the dcm4chee source directories, check out dcm4jboss-all from SVN:

svn co https://dcm4che.svn.sourceforge.net/svnroot/dcm4che/dcm4che14/trunk dcm4che14
svn co https://dcm4che.svn.sourceforge.net/svnroot/dcm4che/dcm4chee/dcm4chee-arr/trunk dcm4chee-arr
svn co https://dcm4che.svn.sourceforge.net/svnroot/dcm4che/dcm4chee/dcm4chee-audit/trunk dcm4chee-audit
svn co https://dcm4che.svn.sourceforge.net/svnroot/dcm4che/dcm4chee/dcm4chee-arc/trunk dcm4jboss-all

Build Dcm4che14

cd to the dcm4che14 checkout directory
ant

Build Dcm4chee-arr

cd to the dcm4chee-arr checkout directory
mvn install

Build Dcm4chee-audit

cd to the dcm4chee-audit checkout directory
mvn install

Build Instructions

Create an environment variable pointing to the Ant home directory (ANT_HOME) and add the $ANT_HOME/bin directory to your PATH.

The build scripts dcm4jboss-all/dcm4jboss-xxx/build.xml assumes following locations of XDoclet, JBoss, Apache FOP, Jakarta Cactus and dcm4che14:

xdoclet.home=${user.home}/xdoclet-1.2.3

jboss.home=${user.home}/jboss-4.2.2.GA

fop.home=${user.home}/fop-0.20.5

cactus.home=${user.home}/jakarta-cactus-13-1.7

m2.repos=${user.home}/.m2/repository

dcm4che14.home=${user.home}/dcm4che14/build/dcm4che-1.4.18

3rd Party Dependency Paths

Each of the dcm4chee projects contains a file called build.properties.default in its root directory. These files contain the paths to dependencies to third party libraries that the projects need in order to compile. Copy each build.properties.default file to build.properties in the same directory. Edit these files and put in the necessary path information so that the compilation process can find the dependencies. The build scripts will automatically look for the build.properties files.

Alternatively, you may combine all of the build.properties entries into a single build.properties file in the root dcm4jboss-all directory in order to avoid editing so many files.

Change to the working build directory:

cd dcm4jboss-all/dcm4jboss-build

and invoke:

ant dist

to build all components and pack them in binary distribution packages:

target/dcm4chee-db2-%version%.zip

target/dcm4chee-firebird-%version%.zip

target/dcm4chee-hsql-%version%.zip

target/dcm4chee-mssql-%version%.zip

target/dcm4chee-mysql-%version%.zip

target/dcm4chee-oracle-%version%.zip

target/dcm4chee-psql-%version%.zip

in kubuntu 6.10 edgy I had ant 1.6.5 and it did not work now I updated it to 1.7 and ant is working but xdoclet gives error.

can you provide some eclipse and build tutorial ?

thanks.

I fixed a couple of errors in these instructions, and responded to your mailing list post.  Respond there if you have further issues.  Thanks!

 -- Damien

Did I miss something - or is the info at this page no longer true ? ( svn checkout today - 2007.09.21 - checks out Version 5037)

  • ant dist produces now "target/ dcm4chee-xxx-2.12.0.zip" and so on, and no longer "target/dcm4chee-standalone-xxx.zip"

Found out, that this means, that jboss is not included in the zip anymore. But in the /bin directory there is "install_jboss.sh",

that copies jboss components into the dcm4chee installation. Trying this (with jboss-4.2.1.GA as mentioned in the script) and

running ./run.sh gives at some point:

14:07:09,231 ERROR [MainDeployer] Could not create deployment: file:/home/pl/work/dcm4chee/FROM_SOURCE/final/dcm4chee-mysql-2.12.0/server/default/deploy/dcm4chee-auditlog-service.xml
org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.dcm4chee.audit.logger.AuditLogger; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.dcm4chee.audit.logger.AuditLogger)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)

and a lot of unresolved deploiment dependencies:

14:07:39,529 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@ca640876
deployer: org.jboss.deployment.SARDeployer@e64686
status: Deployment FAILED reason: No ClassLoaders found for: org.dcm4chee.audit.logger.AuditLogger; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.dcm4chee.audit.logger.AuditLogger)
state: FAILED
watch: file:/home/pl/work/dcm4chee/FROM_SOURCE/final/dcm4chee-mysql-2.12.0/server/default/deploy/dcm4chee-auditlog-service.xml
altDD: null
lastDeployed: 1190376429219
lastModified: 1190376429000
mbeans:
....
Till dcm4chee-standalone-xx-2.11.1 everything (svn checkout, build, ...) worked like a charm !

Powered by a free Atlassian Confluence Open Source Project License granted to dcm4che. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators