THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- General Guide
- Getting Source code
- Setting up your development environment
- Importing SCA modules into your Development IDE
- Coding Guidelines
- Testing
- Client Applications
- Maven Build Structure
- Development Hints
...
Java SCA requires the following:
- JDK 5.0+ (J2SE 1.56.0+)
- Apache Maven (2.02.71+)
- Subversion (1.56+) or TortoiseSVN (1.56.x+)
- Eclipse PDE (Ganymede )
...
Folder Names: Please use all lowercases and dashes in folder names (like in the jar names)
- Maven artifact id = tuscany-<folder name>
Package names: Package names within modules should include the module name so that source code can be located in the source tree easily. So, for example, java/sca/module/implementation-java would be in package structure org.apache.tuscany.implementation.java.*
...
'work-in-progress' modules can be worked on in the same source tree and yet not break the top-down build. You can do this by not listing your module(s) in java/sca/modules/pom.xml.
Development Hints
| Anchor | ||||
|---|---|---|---|---|
|
This section has talked about how to get set up ready to develop Tuscany. If you need to import existing samples into Eclipse to work on there are some instructions here. These are instructions for 1.x but should work OK on 2.x.
| Anchor | ||||
|---|---|---|---|---|
|
...
The magic -Dwtpversion=1.5 option will add the WTP Web project nature to
all the Eclipse projects with <packaging>war</packaging> in their Maven
pom.xml. You'll then be able to add these projects to a WTP Tomcat or
Geronimo Server configuration, to publish and run them straight from
your Eclipse workspace.h3:
| Anchor | ||||
|---|---|---|---|---|
|
Figuring out the package dependency to include in Ant build.xml can be a pain. Here is a quick
script which works in Linux environment for war files.
...