Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Reply-To: <reinhard@apache.org>
From: =?iso-8859-1?Q?Reinhard_P=F6tz?= <reinhard_poetz@gmx.net>
To: <dev@cocoon.apache.org>
Subject: RE: eclipse classpath
Date: Tue, 15 Jul 2003 08:47:28 +0200
Message-ID: <001301c34a9c$f5b52970$1e01a8c0@WRPO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3F136576.7020808@leverageweb.com>
Importance: Normal


From: Geoff Howard [mailto:cocoon@leverageweb.com] 

> Joerg Heinicke wrote:
> > Why exactly? I only found out - when setting output path to
> > WEB-INF/classes - that Eclipse kicked the complete content 
> and replaces 
> > the xpatch'ed cocoon.roles. 
> 
> Maybe that is the smarter way to go.  I've been wanting to 
> set the output path to the same as the build before 
> prepare-webapp (i.e., 
> build/cocoon-2.1rc1dev/classes, 
> build/cocoon-2.1rc1dev/scratchpad/dest, 
> and so on for each source path) so I could let eclipse do the 
> compiling (since it usually already has anyway) but still use 
> the regular build. I don't know that eclipse's compiling is 
> orders of magnitude better, but 
> it does it incrementally.
> 
> But compiling/copying straight to WEB-INF would save even 
> more time in 
> some situations.  Well, I'll start experimenting and see what 
> I learn. 
> Anything to improve:
> BUILD SUCCESSFUL
> Total time: 14 minutes 29 seconds

Therefore I added the paramter 

   ide.eclipse.outputdir 

to build.properties. Here you can set your WEB-INF/classes
directory and compile directly into your servlet container. This
works pretty good for me. If you need more fine grained output
directories this should be possible but I haven't needed it yet.

HTH
Reinhard