This page is intended for developers who want to contribute to Weasis and it is a recommendation for developers who want to create their own plug-ins, see also How to build and install a plug-in.
We recommend the use of Eclipse IDE, because all the following instructions are based on it and some settings and the coding conventions can be imported directly into Eclipse. Nevertheless, for having a better Maven integration, it is possible to use IntelliJ IDEA or Netbeans by configuring weasis-launcher with similar instructions described in Debug or Run from Eclipse.
It is recommended to create a new Workspace for keeping a specific Weasis configuration.
Weasis adheres to the Java Language Specification. Here are some code style specifications:
Code style specifications can be imported into Eclipse:
Building Weasis plug-ins
Getting errors on the projects. Try the following instructions:
If you have Maven installed on your system or TM terminal Eclipse plugin, it is sometimes easier to type the maven commands directly in a console.
Building Weasis Distributions
The distribution files are located in the target/dist folder of the project.
See Building Weasis from source for more advanced options.
For debugging Weasis, you need to create a Debug configuration:
$dicom:get -l \"D:\images test\dicom\"
Some command interpreters need to escape the quotes or double quotes required for paths or URLs. This is the case with Eclipse.
For more commands at startup see also Weasis commands.
In Eclipse launcher parameters, ‘&’ within URLs needs to be escaped with a backslash.
-Xms64m -Xmx768m -Dgosh.args="-sc telnetd -p 17179 start"
Meaning of the properties (see also Preferences):
felix.config.properties defines the location of config.properties (the OSGI configuration and the list of plug-ins to install/start)
felix.extended.config.properties defines the location of ext-config.properties (extends/overrides config.properties)