Are you brave? Are you willing to live on the edge? Willing to try out a highly experimental to build Turbine with Eclipse? If yes, read on...
1) Get Eclipse. I did all my tests with Eclipse 2.1.1 on RedHat Linux 9 and J2SDK 1.4.1_02. YMMV. Install it. 2) Fetch the Turbine Source Tree cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout jakarta-turbine-2 3) Fetch the Eclipse Build enviroment from http://jakarta.apache.org/~henning/turbine/turbine-eclipse.tar.gz 4) Unpack it into the Turbine Source tree: cd jakarta-turbine-2 ; tar xzf turbine-eclipse.tar.gz 5) Start Eclipse. Select "File -> Import". Choose "Existing Project into Workspace" Browse to the checked out directory. Select it. You should now have Project Name: jakarta-turbine-2 Project Contents: ..../jakarta-turbine-2/ Choose "Finish" 6) Now you should have the jakarta-turbine-2 Tree in Eclipse with lots of errors. That's ok. Choose "Rebuild Project" 7) You should get "Build Problems" with "Problems occured building the selected resources". This is expected! Open the Details. It should display --- cut --- For a successful build, you must get the following jars from java.sun.com and copy them into target/lib: activation.jar, Version 1.0.2 as activation-1.0.2.jar mail.jar, Version 1.3 as javamail-1.3.jar jdbc.jar, Version 2.0 as jdbc-2.0.jar jndi.jar, Version 1.2.1 as jndi-1.2.1.jar One of these jars is missing. Please correct this error and rebuild. --- cut --- 8) Get the jars from java.sun.com and put them into the target/lib directory in your jakarta-turbine-2 directory. 9) Choose "Rebuild Project" again. This should run now for a while and the console should show the ant task fetching all the public jars from ibiblio. After a while, the build process should start and be successful (with quite a number of deprecation warnings depending on your default compiler settings). 10) If the rebuild still fails because of "missing jars", then Eclipse hasn't picked up the ant-fetched jars yet. Simply open "jakarta-turbine-2/target" in the tree view and select "Refresh" from the content menu on the target folder. This should kick the compilation immediately. The tree view should now show all the jars required for building Turbine. Have fun. This wants testing. If it works for Eclipse users, we might add this as an alternative way of building Turbine. Until then, consider this highly experimental (I'm not exactly a seasoned Eclipse user ;-) ) Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ Java, perl, Solaris, Linux, xSP Consulting, Web Services freelance consultant -- Jakarta Turbine Development -- hero for hire "You are being far too rational for this discussion." --- Scott Robert Ladd in <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
