Home › groups › Proparse Group

Using proparse.jar with Java or JVM scripting

Thu, 2008-07-31 23:36 — john

Download
You can find a pre-built proparse.jar on Joanju's Proparse page at
joanju.com/proparse/.

Configuration for Project Settings
See Project Config. Dump for a script which creates a prorefactor project settings directory.

Disc Space
Proparse may write very large amounts of data to into the 'prorefactor' sub-directory of your working directory. If your application is very large, then this could be as much as a few GB. See PUB Files for more information.

Setting Up Scripting

This section assumes you will be using Groovy for scripting, but other JVM scripting languages will be similar.

  1. Install the latest version of Groovy (assuming you have Java installed): groovy.codehaus.org
  2. Open a command line prompt. Change to your working directory (the one that contains the 'prorefactor' subdirectory). Test that groovy runs OK with: groovy --version
  3. Make sure your CLASSPATH environment variable contains proparse.jar. For example, on Windows you might use:

    set CLASSPATH=src;bin;proparse.jar

    assuming proparse.jar is in the working directory. (On Linux or unix, use ':' instead of ';' to separate classpath entries.)


‹ Using proparse.jar as a ServerupNew AST ›

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Sat, 2008-08-02 20:26 — admin.jurjen

proparse.jar needs prorefactor directories?

Maybe I don't understand your instructions, but if I want to use Proparse without Prorefactor, for example just to drive Prolint, do I still need to make Prorefactor project settings and will Proparse still dump output to a Prorefactor sub-directory?


Sat, 2008-08-02 20:52 — john
john's picture

Re: proparse.jar needs prorefactor directories?

I have a bit more work to do. :) Right now proparse.jar does have the same requirements and output as ProRefactor.

I have to add a couple of minor things to proparse.jar so that the new socket/blob API is more suitable for Prolint:
- allow configuration through the socket, rather than require an up-front dump of the project settings
- make it optional whether anything is stored in a 'prorefactor' subdirectory

But in terms of using proparse.jar for jvm scripting, yes, it's the same as ProRefactor.