Build Troubleshooting

Name Undefined Error (Old Ant Version)

As of JasperReports Server 6.1, we recommend Apache Ant version 1.9.4 or higher. JasperReports Server 6.1 is compatible with Apache Ant 1.8.1 or higher.

If you're not using the version of Apache Ant included with the JasperReports Server source code package, you could get the following error when running the buildomatic scripts:

c:\js-builds\jasperserver\buildomatic\install.xml:6: Problem: failed to create task or type if
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.


The buildomatic scripts require Ant version 1.8.1 or higher, and the ant-contrib.jar file needs to be included in your ant/lib directory. We recommend Ant version 1.9.4. If you're running with your own Ant version, you can copy this jar to your <ant-home>/lib directory:







(General example)


(Windows example)


(Linux example)


(Mac example)

Database Troubleshooting

The most common errors encountered when building JasperReports Server involve the database connection. For information about database connection problems, see the Troubleshooting Appendix of the JasperReports Server Installation Guide.

Maven Troubleshooting

Maven Error on Linux or Mac

If Maven is installed on Linux via rpm, apt-get, or yum (or on Mac), the Maven binary and the Maven libraries are probably in separate locations. This can potentially cause a problem with the source build.

/usr/boot Does Not Exist Error

When building under Linux or Mac, you may get an error similar to the following:

/usr/boot does not exist

The Buildomatic scripts attempt to find the MAVEN_HOME setting and can be unsuccessful when the maven binary is installed in the /usr/bin/mvn location. The workaround is to update your file:

cd <js-src>/jasperserver/buildomatic


Uncomment the maven.home line so that it looks like this:

maven.home = /usr/share/maven2 (Linux)

For Mac, the location of the Maven library files is typically slightly different:

maven.home = /usr/share/maven (Mac)

Clear JasperReports Server Artifacts in Maven Local Repository

If you add new code to an existing source build environment, such as a bug fix source patch update, you can clear the JasperReports Server artifacts in your Maven local repository to ensure that the newly built artifacts contain the necessary new content. Maven updates the artifacts automatically, but if you have trouble building or pulling in the modified code, you can try deleting these artifact trees.

To clear existing JasperReports Server artifacts:

1. Go to the repository directory:

cd <home-dir-path>/.m2/repository

2. Remove the old versions by deleting the following directories and their contents:


Community Project artifact tree


Commercial version artifact tree

Clear Entire Local Repository

If you want to completely rebuild everything, remove all of the cached jars in your Maven local repository. To do this you can delete (or rename) the entire local repository.

Then when you build JasperServer, all dependencies are re-downloaded.

cd <home-dir-path>/.m2

rm -rf repository

Maven Warnings

Maven generates verbose warnings during the artifact validation process. For example, the following warning was generated, even though the required JAR file was downloaded successfully:

[WARNING] Unable to get resource from repository jasperServer (file://C:/svn/js-buildlds/jasperserver-repo
163b downloaded

Old Maven Binary

In general, it's best to use the most current stable version of the Maven tool. We recommend Maven version 3.0.4.

Other Build Troubleshooting

Error When Building Database Scripts

When compiling in the jasperserver-repository-hibernate/build-db directory, you might see an error containing the following message:

[INFO] ------------------------------------------------------------------------
[INFO] Error executing ant tasks
Embedded error: Source file does not exist!

The most likely problem is that your .m2/settings.xml file doesn’t point to the correct source location, and the build step didn't find the Quartz scripts. The settings.xml file should contain the path to the quartz script corresponding to your database, for example:


If you use the buildomatic scripts you shouldn't get this kind of error.