Differences between revisions 11 and 12
|Deletions are marked like this.||Additions are marked like this.|
|Line 5:||Line 5:|
|* Download ["Using GIT and Gerrit"]|
For developers working with the code there are essentially three ways of building from source:
For the person making the release, the scripts used use the Ant build. Once the release process is moved to Maven, the "Using Ant"-alternative will be abandoned. There is still a lot of work left.
The nightly build uses the ant build. The continuous integration jobs (on the same host as the nightly build) uses Maven.
The build Using Maven is also possible from within Eclipse if you have the m2eclipse plugin.
Old wiki page
Building ArgoUML from source requires around 350MB of free disk space depending on what modules you want to build and if you want to build the documentation or not. The ambition is to provide a way to download and build that is as simple and straight-forward as possible.
Currently there are two ways to do this, either the traditional way, resulting in a file structure called the repository layout because the directories are located as they are in the repository, or a file structure called the Eclipse layout because it works with Eclipse's project structure.
In the Cookbook this had the following subsections:
2.1. Quick Start
2.2. Source layout
- 2.3.1. What do I need to build ArgoUML?
- 2.3.2. Configuring Subversion
- 2.4.1. Which tools are part of the ArgoUML development environment?
- 2.4.2. What libraries are needed and used by ArgoUML?
2.6. Build Process
- 2.6.1. How Ant is run from the ArgoUML development environment
- 2.6.2. Developing in a subproject
- 2.6.3. Troubleshooting the development build
2.7. The JUnit test cases
- 2.7.1. About the Test case Class
- 2.7.2. Naming JUnit tests classes
- 2.7.3. About the Test case Methods
- 2.7.4. Improving a test case
- 2.8.1. Building documentation
2.9. Setting up Eclipse 3
- 2.9.1. Eclipse installation instructions
- 2.9.2. Basic ideas of the set up
- 2.9.3. Checking out through Eclipse
- 2.9.4. Eclipse to help with the ArgoUML coding style
- 2.9.5. Eclipse to automatically find problems in the code
- 2.9.6. Settings for Checkclipse
- 2.9.7. Running JUnit test cases from within Eclipse
- 2.9.8. How to work with the modules
2.10. Settings for NetBeans
2.11. Settings for Emacs
2.12. Making a release
- 2.12.1. The release did not work