Re: Dev. tools

Thu, 26 Aug 2004 09:55:30 -0700 

Hi,

Please be sure to work with the correct Jahia branch:
http://cvspub.jahia.org/cvstags.html
If you have Pluto and Jetspeed 2, this means that you are working in the dev branch (future major release - under heavy dev - unstable branch). If you want to work on the 4.0, be sure to use the right branch of the CVS.

Cheers
St�phane

At 17:44 26/08/2004, you wrote: 
Thank's for your answer...

I try to build an "industrial" and "high quality" developpement environment (My dev teams are usually working with Eclipse/CVS/Struts). But the problem seems to be a little bit more complicated :-(

I've just synchronized with the CVS repository.
The directory architecture is mostly different as yours, see :

dist
   /core
      /lib
         /jetspeed2
      /src
         /conf
         /java
            /components
            /compressionFilters
            /jahiatemplates
            /org
            /upgrade
         /scripts
         /test
         /webapp
   /patched-slide
   /pluto
      /dispatchee
      /dispatcher
   /torque
      /src
         /schema
         /template

I use Eclipse 3.0 with the MyEclipse J2EE plug-in.
So I've :

   * imported all /core/src/java/org/* in my Eclipse source folder.
   * imported all /core/src/webapp in my Eclipse webRoot folder.
   * imported all /core/lib/* in my Eclipse webRoot/WEB-INF/lib folder.

Of course the are a lot of project compilation problems. I've imported all jars from the directory /webapps/jahia/WEB-INF/lib/ of the binary distribution into my Eclipse webRoot/WEB-INF/lib folder. I've done the same with the pluto directory. But not better...

Any advice ?

[EMAIL PROTECTED] wrote:


We are developing with the WSAD extension of the Eclipse Java IDE. We have imported the Jahia 4.0.4 release into an own Web project.

First we downloaded the sources for Jahia 4.0.4 from the Jahia CVS repository.

Jahia came with the structure:

build
docs
etc
lib
metadata
src/java
src/script
src/views
test
var


In Eclipse/WSAD we have the directories:

source/java
source/script
webModule


So we had to reorganize:

build -> we didn't import as it will be created by Eclipse in webModule/WEB-INF/classes
docs -> ignored
etc -> moved to webModule/WEB-INF/etc
lib -> moved to webModule/WEB-INF/lib
metadata -> ignored as this data is created with Eclipse/WSAD
src/java -> moved to source/java
src/script -> moved to source/script
src/views -> moved to webModule
test -> ignored
var -> moved to webModule/WEB-INF/var


There was a major restructuring after Jahia 4.0.4. We haven't imported the latest sources (with jetspeed-integration) yet, so there are some differences.

Furthermore we are developing our own TEMPLATES in a separate Eclipse/WSAD project and we are synchronising (with our own Eclipse plugin) this TEMPLATES project into the Jahia project.

Greetings,
Benjamin Papez



*S�bastien LANDEAU <[EMAIL PROTECTED]>*

25.08.2004 17:54
Please respond to
<[EMAIL PROTECTED]>



To
        "dev_list Jahia.org" <[EMAIL PROTECTED]>
cc

Subject
        Dev. tools










Does some people developping Jahia with the Eclipse Java IDE ?
If yes, how is organized your workspaces ?


Thank's a lot.

Reply via email to