Installation

These steps will quickly get JumpStart 7.0.n running and editable.

  1. Unzip the download.
    • Unzip the downloaded file, which will give you a directory called tapestry-jumpstart-7.0.n or similar.
    • Move it to your development area, eg. /devel/tapestry-jumpstart-7.0.n/ .
    • DO NOT choose a directory whose path contains any spaces, eg. do not use a directory whose path includes C:/Documents and Settings/.
  2. Open it in Eclipse.
    • Eclipse 4.6 ("Neon") or 4.5 ("Mars") is preferred. The Eclipse IDE for Java EE Developers package is good (JumpStart is developed with it).
    • In Eclipse, choose File > Import..., then choose General > Existing Projects into Workspace, click Next >, set the root directory to your tapestry-jumpstart directory eg. /devel/tapestry-jumpstart-7.0.n/, click Finish.
    • The project can't build just yet so it will show errors.
  3. Ensure the project is using Java 8.
    • In Eclipse, right-click on the project and choose Properties then Java Compiler and ensure Compiler compliance level is 1.8. You may have to turn on Enable project specific settings.
  4. Run get-dependent-files.
    The project has an Ant build file, build.xml, with a get-dependent-files target. To run it in Eclipse:
    • Open the Ant view and drag build.xml onto it.
    • If your internet connection is through a proxy then modify the setproxy tag in build.xml, eg.
        <setproxy proxyhost="proxy.mycompany.com" proxyport="8080"></setproxy>
      This may also be necessary in business/build.xml and web/build.xml.
    • Run the get-dependent-files target in the project's build.xml file (find the target in the Ant view and double-click on it). If Ant has problems due to the maven repository being slow or inaccessible, open the project's build.properties and choose a different maven.repo.root, then try running the target again.
    • The new files won't be visible in the project just yet.
  5. Refresh the project.
    • In Eclipse, right-click on the project and choose Refresh. This should build the project successfully and show no errors.
    • It also runs collapser.xml, which builds the collapsed/ directory containing a WAR in "collapsed EAR" format. You can see how has this been configured by displaying the project's properties and choosing Builders.
    • You can see now that the previous step, Run get-dependent-files, populated the following directories with JARS:
      	business/src/main/lib-compile/
      	business/src/main/lib-provided/
      	business/src/main/lib-runtime/
      	business/src/test/lib-test/
      	business/src/test/lib-test-hibernate/
      	tools/lib/
      	web/src/main/lib-compile/
      	web/src/main/lib-provided/
      	web/src/main/lib-runtime/
      	web/src/test/lib-test/
      	
  6. Set the collapsed directory to derived.
    • In Eclipse, right-click on the collapsed directory, choose Properties, and tick the derived checkbox. Then click OK.
  7. Get OpenEJB.
    OpenEJB will be your embedded EJB container during development.
    • Go to Apache TomEE Downloads and download OpenEJB Standalone 7.0.4.
    • Once downloaded, unzip it. Move it to a suitable location (eg. /devel/apache-openejb-7.0.4).
    • In Eclipse, choose Window > Preferences > Java > Build Path > User Libraries (or in OS X, choose Eclipse > Preferences... > Java > Build Path > User Libraries), and
    • Click New... and create a new user library called apache-openejb-7.0.4-lib, then
    • Click Add External Jars... and add every JAR in OpenEJB's lib/ directory to the new user library.
  8. Configure OpenEJB.
    • In the project, find /business/src/test/conf and copy file openejb-in-memory.xml.template to openejb-in-memory.xml.
    • Open openejb-in-memory.xml, and correct the Deployments dir path if it's wrong.
You now have the following environment available to Eclipse:

Web Server Business Server Persistence Database Server Logger
Jetty OpenEJB Hibernate HSQLDB Log4j
(As jars in project) (As a user library) (As jars in project) (Within OpenEJB) (As jars in project)

Here's how to use it:

Next steps.
Visit Orientation, Debugging, Tips, and Troubleshooting for more info.





©2006, 2012 Geoff Callender, Sydney, Australia