Hello bd,
To start the the admin console, you can do the following:
- unzip the jppf-full-src-.....zip
- go to the jppf-x.y/demo folder
- you can use the build.xml script in this folder: ant run.ui
The console requires the following jars:
- all jppf-*.jar files
- jppf-x.y/JPPF/lib/ApacheCommons/commons-io-1.2.jar
- jppf-x.y/JPPF/lib/ApacheCommons/commons-logging-1.1.jar
- jppf-x.y/JPPF/lib/JDesktop/swingx.jar
- jppf-x.y/JPPF/lib/JFreeChart/jcommon-1.0.6.jar
- jppf-x.y/JPPF/lib/JFreeChart/jfreechart-1.0.3.jar
- jppf-x.y/JPPF/lib/log4j/log4j-1.2.9.jar
- jppf-x.y/JPPF/lib/Rhino/js.jar
- jppf-x.y/JPPF/lib/Substance/substance-3.1.jar
If you wish to build JPPF, there is a build.xml in
jppf-x.y/JPPF/bin. This is the script I use to generate a distribution. The main targets of interest are:
- compile: compile all modules (e.g. client, node, etc...)
- build: compile and generate all the jppf-*.jar
- rebuild: same as build, but doing a clean beforehand
- deploy: generate the whole distribution, including the zip files you can dowload from SourceForge
- javadoc: generate the complete javadoc
You are right, we do use Eclipse as our development environment. There's a number of projects each associated with a CVS module. Each project has the following base structure:
---module_name (project root)
------src
---------java (java sources and javadoc artifacts)
---------resources (xml files, pictures, icons, etc...)
------classes (compiled sources + resources)
The module JPPF contains all the 3rd-party libraries in its /lib folder.
I'm not sure why you need to recompile with Java 1.6, is it a requirement for the version of NetBeans you're using?
Let me know if this helps.
-Laurent