...
The ExampleMavenProject module contains the following Maven files, all of which should be included in a new Maven project.
No Format |
---|
build.sh
maven.xml
project.properties
project.xml
|
buildThe project.sh is a helper script for building the project with a set of maven commands.maven.xml sets-up some project build defaultsxml file is the primary Maven configuration file that lists all the project's meta-information and its dependencies.
The project.properties file is used to set named variables (properties) that determine certain project behavior, such as whether deprecation warnings are shown or the tests are skipped. You can put any custom
maven settings into this file.
...
No Format |
---|
#maven.compile.deprecation=on |
The project.xml file is the primary Maven configuration file that lists all the project's meta-information and its dependencies.
There are two additional test files.
...
maven.xml sets-up some project build defaults.
build.sh is a non-essential helper script demonstrating a project build with a set of maven commands.
Example Code
Two Java files are included within the sample project.
The src/ExampleMavenProject.java is a simple example of a Java source file.
The file test/ExampleMavenProjectTest.java is a very basic test case example that runs the main of a project class with some dummy arguments.
Building
This is the simplest way to build a Maven project.
No Format |
---|
cd ExampleMavenProject
maven
|
(It doesn't get much easier than that.)
The maven.xml file sets the default build target to create a jar in the target directory.
No Format |
---|
ExampleMavenProject-1.0.jar
|
The "1.0" version number comes from the project.xml file.
ExampleMavenProject also includes a bash build scriptTo build the project from the command-line on Linux, Cygwin, etc.
No Format |
---|
cd ExampleMavenProject ./build.sh |
Or you can use Maven directlyThis executes the following command.
No Format |
---|
maven -Drun.install=$(pwd) -Dmaven.test.skip=true clean jar:install jas:install run:install |
Note |
This command builds the jar file, skipping tests, and installs the run script into the current directory. It also makes the jar available to JAS3.
This would be the step-by-step build procedure (leaving out the skipping of tests).
- Build the jar file.
No Format maven
- Create the project run script.
No Format maven -Drun.install=$(pwd) run:install
- Install the jar into the ~/.JAS3/extensions directory, so that JAS3 will automatically load a plugin when it starts up.
No Format maven jas:install
Testing
Now, test the run script.
...
Simply rerun the build command given above to compile any classes that you add.
Using as a Template
To use ExampleMavenProject as a template First, create a directory for your own new project, replace the "ExampleMavenProject" string with the actual name of your own project in project.xml.
The CVS directories should all be removed.
No Format |
---|
find . -name "CVS" -exec rm -rf '{}' \; &> /dev/null
|
Then add to your CVS project all the files listed under the Anatomy section using CVS's import and add commands.
No Format |
---|
cvs import -m "Initial commit of MyProject" myProjectDir vendor initial
|
The above is an example only.
project at the same level as the ExampleMavenProject directory.
No Format |
---|
mkdir MyProject
cd MyProject
|
Then you can copy all the files from ExampleMavenProject into your area, excluding CVS files, with a command like this.
No Format |
---|
bash
for f in $(find ../ExampleMavenProject -print | grep -v CVS); do cp $f .; done
|
Tip | ||
---|---|---|
| ||
Contact your system administrator about adding a project to your local source code repository. Or mail Contact Tony Johnson if you want to use the LCD CVS at SLAC. |