Talk:ReadMe
From JQuantLib
This is a list of some issues and their solutions
Diagnostic
When running Maven, you may get "org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-1:create: Mojo execution failed."
Solution
You may have forgotten to install subversion, even if the eclipse subversive plugin is installed. See also the next issue before proceeding with the installation recommended here.
apt-get install subversion
Diagnostic
When running a Maven task, you may get an error like this: "Provider message: The svn command failed. Command output: svn: This client is too old to work with working copy '.'".
Solution
In this case the version of subversion embedded in your Subversive plugin is higher than the version of the svn command installed in your command line environment, which is used by the maven command. The easiest thing to do is upgrade your subversion installation. In the specific case of Debian, this can be accomplished by installing subversion from Backports, like this:
apt-get -t lenny-backports install subversion
Make sure you have configured access to Debian Backports configured in your /etc/apt/sources.list. Please follow this link.
Diagnostic
You may receive this error message in Eclipse: "javac: invalid target release: 1.6".
Solution
Check that your project compiler compliance level is the same version as the JRE configured in maven launch configuration.
Diagnostic
When checking out the source code using the eclipse subversive plugin, you may get some strange errors like "Get repository folder children operation failed. svn: Broken pipe svn: PROPFIND request failed on ...".
Solution
The only thing you have to do is to refresh the folder where the error occurs (a few times ;-))
Diagnostic
When trying to run the test cases using the Eclipse Emma plug-in you may get an error like: "Class not found ... URLClassLoader...".
Solution
This is usually the case when the project has been built by Maven and you try to run the testcases from from eclipse. You can change the export order (in the preference settings) and make sure the maven dependencies appear before the jre. Another workaround is to clean and built the sources with eclipse before running the testcases.
Diagnostic
When trying to commit a change you get a Subversive message like "svn: authentication cancelled".
Solution
The reason therefore as well as a workaround is illustrated here. However if this does not work, consider creating a new repository location, check out the project and avoid saving the password.
