Date: 2005-03-06T10:52:24 Editor: DuncanMills Wiki: Apache Struts Wiki Page: BuildingShale URL: http://wiki.apache.org/struts/BuildingShale
no comment Change Log: ------------------------------------------------------------------------------ @@ -8,6 +8,29 @@ To get the Ant compile to run successfully in JDeveloper a some extra settings have to be added to the build.properties to override locations defined in the build.xml ''if'' you want to use the JSF RI as shipped with JDeveloper and the OC4J servlet API JARs rather than downloading a separate JSF RI and Tomcat. This assumes the use of JDeveloper 10.1.3 developer preview (J2EE edition). Note the versions of the various Jakarta Commons libraries shipped in the JDeveloper install are lower than those needed for Shale, so you should separately download ''beanutils'', ''chain'', ''digester'' and ''logging'' and update your build.properties with the appropriate locations. + === General JDeveloper Setup === +Set up JDeveloper to exclude the '''.svn''' sub-directories from the source view in the navigator. to do this: + 1. From the menu ''Tools'' > ''Properties'' + 1. Choose ''Global Ignore List'' in the properties tree + 1. Go to the ''New Filter'' field and add '''**/.svn''' + 1. Press ''Add'', then OK. + +Next, if you want to compile Shale through the normal workspace make/compile rather than Ant, create user libraries to point at the updated versions of the various commons libraries mentioned above. Use the ''Tools'' > ''Manage Libraries'' menu option. It's probably worth doing this in any case, even if you intend to use Ant for building, just so that code insight and so on will work correctly if you want to change the source. + + === Creating a Base Project for Shale === +JDeveloper 10.1.3 does not come with an SVN plugin yet so you'll have to pull the source tree from the command line or from a tool like TortoiseSVN. +Once you've done this, go ahead and do the following to create a project with the Shale core source. + 1. Create a new workspace. Call this something like '''Shale''' and put it in the root shale directory created by the svn checkout. + 1. Create a new project from source (call the project something like '''core-library''') and point it at /core-library/src/java for the source tree. Store the project file in the core-library subdirectory for convenience, although both it and the workspace (jws) file can live outside of the Shale directory structure if you want to keep the source directories cleaner. + 1. Once the project is created, open the project properties and select the ''Project Content'' node. Set the ''Output Directory'' field to the '''core-library/target/classes''' directory rather than the default ''/classes'' this will ensure that both the Ant compile target and a JDeveloper compile with both write to the same place and you'll not end up with two sets of class files. + 1. Also in the project properties be sure to add the various libraries required for Shale if you might want to edit the code and need code assistance. + * Servlet Runtime + * JSF + * Commons Logging 1.0.4 + * Commons Chain 1.0 + * Commons Digester 1.6 + * Commons Beanutils 1.7.0 + 1.#5 Finally copy the build.properties.sample file to build.properties and make the changes outlined in the next section. === Extra entries in build.properties === * The JSF RI jars are in %JDEV_HOME%/jsf-ri * The servet and JSP API jars are in %JDEV_HOME%/j2ee/home/lib and have different names from the Tomcat jars @@ -16,6 +39,11 @@ ||jsf-impl.jar||%JDEV_HOME%/jsf-ri/jsf-impl.jar|| ||jsp-api.jar||%JDEV_HOME%/j2ee/home/lib/ojsp.jar|| ||servlet-api.jar||%JDEV_HOME%/j2ee/home/lib/servlet.jar|| + === Building Shale in JDeveloper === +To build you can simply use the defined Ant targets. Select the build.xml and in the structure pane you'll see the various targets. Right mouse click on the required target (e.g. '''library''') and choose run. + + == Eclipse 3.0.1 == +<<Coming Soon>> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
