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 14:00:34 GMT
   Date: 2004-12-28T06:00:34
   Editor: TorstenSchlabach
   Wiki: Cocoon Wiki
   Page: LoadInEclipse
   URL: http://wiki.apache.org/cocoon/LoadInEclipse

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -67,13 +67,25 @@
 attachment:eclipse-cocoon-import-01.jpg
 
  * In Eclipse, choose File -> New -> Project and select "Java Project". (This is not
very logical as we already have an Eclipse Java project, don't we?)
+
+attachment:eclipse-cocoon-import-02.jpg
+attachment:eclipse-cocoon-import-03.jpg
+
+
  * On the dialogue that comes up, make sure the option "Create Project in Workspace" is selected
and enter the project name '''exactly''' as the name of the directory, for example {{{cocoon-2.1.6}}}.
 
+attachment:eclipse-cocoon-import-04.jpg
+
 Once you do that, note the information that shows up in the bottom of the dialogue. (It will
only show up if you name the project identical to the folder!) Hit finish and you are done.
Cocoon is now a project in your Eclipse Workbench using the correct settings from the .classpath
and .project files.
 
 ''Note'': Eclipse considers it a feature that the project's name in the workspace can be
different from the name on the file system. You can then refer to the project name instead
of the filesystem name, for example when building project dependencies. But in Cocoon land
this is causing more trouble than doing any good, therefore it is recommended to keep the
project's name in the workspace and the directory name on the filesystem in sync.
 
-At this point, depending on your hardware, you might notice a lot of activity going on. This
is because of Eclipse's habit to compile a .java file as soon as it sees one. This is the
default setting for a new project and we did not yet have a chance to chance this. So either
wait for it to finish (and ignore and warnings or errors) or interrupt the build process and
then:
+At this point, depending on your hardware, you might notice a lot of activity going on. This
is because of Eclipse's habit to compile a .java file as soon as it sees one. This is the
default setting for a new project and we did not yet have a chance to change this. So either
wait for it to finish (and ignore and warnings or errors) or interrupt the build process:
+
+attachment:eclipse-cocoon-import-05.jpg
+attachment:eclipse-cocoon-import-06.jpg
+
+Then:
 
  * make sure the Option ''Build Automatically'' from the ''Project'' menu is not marked.
  * Chosse Project -> Clean (make sure you clean only your project and you do not run a
build straight afterwards) to get rid of the classes that Eclipse just built.

Mime
View raw message