cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@cocoon.apache.org
Subject [Cocoon Wiki] Updated: LoadInEclipse
Date Tue, 28 Dec 2004 13:38:56 GMT
   Date: 2004-12-28T05:38:56
   Editor: TorstenSchlabach
   Wiki: Cocoon Wiki
   Page: LoadInEclipse
   URL: http://wiki.apache.org/cocoon/LoadInEclipse

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -8,19 +8,19 @@
 
 Eclipse comes with Ant built-in. This is commonly known as the "internal Ant". The Ant integration
in Eclipse provides some nice features, such as an outline for build.xml files from which
you can right-click on a target to build it. Unfortunately this does not work for building
Cocoon sources in Eclipse.
 
-The reson for that is that the Cocoon build process relies on external tasks in Ant (see:
[http://ant.apache.org/external.html]) which are compiled on-the-fly during the Cocoon build
process. So if you build Cocoon from the command line using either {{build.bat}} (Windows)
or {{build.sh}} (*ix) here is what is happening internally:
+The reson for that is that the Cocoon build process relies on external tasks in Ant (see:
[http://ant.apache.org/external.html]) which are compiled on-the-fly during the Cocoon build
process. So if you build Cocoon from the command line using either {{{build.bat}}} (Windows)
or {{{build.sh}}} (*ix) here is what is happening internally:
 
  * All existing ANT_HOME and CLASSPATH variables in the environment are put aside.
  * A new classpath is constructed consisting of all .jar files in $COCOON_SRC/lib/endorsed.
(and nothing else!)
- * The Ant in the $COCOON_SRC/tools tree is called with this newly constructed classpath
and the {{-Djava.endorsed.dirs=lib\endorsed}} option. The effect will be that Ant will run
using the Xalan and Xerces implementations provided in the endorsed directory which are presumably
newer and/or contain additional features over the corresponding API implemenations that come
with the JDK. For more information on the "endorsed" mechanism in Java is, have a look at
[http://java.sun.com/j2se/1.5.0/docs/guide/standards/index.html].
+ * The Ant in the $COCOON_SRC/tools tree is called with this newly constructed classpath
and the {{{-Djava.endorsed.dirs=lib\endorsed}}} option. The effect will be that Ant will run
using the Xalan and Xerces implementations provided in the endorsed directory which are presumably
newer and/or contain additional features over the corresponding API implemenations that come
with the JDK. For more information on the "endorsed" mechanism in Java is, have a look at
[http://java.sun.com/j2se/1.5.0/docs/guide/standards/index.html].
 
-One of the very first targets in the build process is the {{init-tasks}} target in the file
{{tools/targets/init-build.xml}}. This target will compile the external Ant tasks
+One of the very first targets in the build process is the {{{init-tasks}}} target in the
file {{{tools/targets/init-build.xml}}}. This target will compile the external Ant tasks
 
  * xpatch (what is says)
  * jing (RELAX NG validation)
  * sitemap-components
 
-from the sources in {{tools/src/anttasks}} to {{tools/anttasks}} and make these external
tasks known to Ant using {{<taskdef ...>}}.
+from the sources in {{{tools/src/anttasks}}} to {{{tools/anttasks}}} and make these external
tasks known to Ant using {{{<taskdef ...>}}}.
 
 Other targets further down the build process rely on these tasks obviously.
 
@@ -114,7 +114,7 @@
 
 ----
 
-I don't know where I should put that.
+^^^^ I don't know where I should put that. ^^^^
 
 TorstenSchlabach
 
@@ -126,6 +126,10 @@
  *  /pathtoworkspace/cocoon-2.1m3
 
 GerhardFroehlich
+
+Does this maybe relate to the section "Eclipse, its workspace ..."? Then it would on only
be applicable to WSAD but any flavour of Eclipse.
+
+TorstenSchlabach
 
 ----
 

Mime
View raw message