Running JParam
Source related Issues
All you have to do is d/l the latest version of JParam from the download page, d/l the appropriate antlr version (currently the version is 2.7.2, it is possible that 2.7.4 will also work, but it wasn't verified). Put both jar files in your class-path and there you go.
There are several ways to build JParam, the first thing you have to do is checkout JParam module from SF (look at the Source Code Repository for instructions).
No you have several options, the best one would be to install maven and use it on JParam (no change is needed), but you can use the simple ant (or even comp.bat) that will create a "dist" directory with the antlr and jparam jar files.
If for some reason you need a different version of antlr then the one JParam was compiled with (for instance you are using another library that also needs a specific version of antlr), in this case you could first check if JParam is working with your version of antlr (a good starting point would be to run all the test cases), if not then you can simply checkout the project from SF, change the antlr jar file to the version you need, compile the lexer/parser files and recompile jparam.
Absolutly nothing, JParam is an eclipse project right out of SF, all you have to do is define a repository for JParam (host: cvs.sourceforge.net, repository location: /cvsroot/jparam) and the checkout the version you like, a project will be created for JParam and everything will be configured there.
If you need to compile the parsers again, you can either use maven (it will recompile the parsers anyway), or run the batch file cp.bat from the meta_sources directory.
Eclipse has defined several compiler warnings as errors, the project definition of JParam should disable those if for some reason they are not disabled (you have a newer version of eclise, or you changed the compiler settings to workspace default).
Because antlr is generating code with some violations, the following violations from the "Unused Code" tab of the "Java Compiler" settings of the project or workspace needs to be disabled:
JParam is using StringBufferInputStream in order to parse value from a given String, this class was deprectaed since JDK1.1 but there is no real alternative to it, so the following error needs also be converted to a warning:
Some 'ignore' staements were inserted into the code in order to overcome the "Parameter is never read" error. Constructs like the following could appear in several baseclasses that implements a given interface but don't really needs its parameters, for example the ParentConverter class cannot change due to any update, but it still implements the update method, it could be possible to define updateable and not updateable converters, this could be considered as an enhancement:
// ignore updatedConverter
if (updatedConverter == null){
}