Sylvain,

Is there any documentation on how to use/build Cocoon in Eclipse. I've
checked the mailing list archives and the Wiki but nothing there.

I managed to get the CVS of Cocoon in Eclipse, but I just can't get it to
compile. I get an error indicating that the javac compiler can't be found,
probably because JAVA_HOME isn't set. But how do I set this environment
variable in Eclipse? And, do I really need to set it?

Litrik De Roy
www.litrik.com


----- Original Message -----
From: "Sylvain Wallez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 23, 2002 5:44 PM
Subject: [Proposal] reconsidering external libraries management


> Hi team,
>
> I've been using Eclipse for some months and it's now my preferred IDE.
> However, creating a Cocoon project under Eclipse isn't a piece of cake :
> all source files depending on optional libraries fail to compile,
> preventing Eclipse to properly build the project.
>
> So, following Nicola Ken's idea, I wrote mock classes for libraries that
> aren't included in Cocoon's CVS. So far so good, the Cocoon Eclipse
> project now builds smoothly. But this reveals something that I'm not
> comfortable with, even if I have lived with it for years : the Cocoon
> build system does not compile all source files, depending on which
> libraries that are actually present in the classpath.
>
> This has several consequences :
> - some source files are never compiled (how many of you have
> phpservlet.jar in their classpath ?)
> - uncompiled source files aren't included in the binary distribution
> (neither in the jar nor in the javadoc), and are therefore totally
> hidden to average users
> - worst of all : we may release an official version that contains files
> that don't even compile !
>
> So I propose that we _remove all the conditional compilation stuff_ and
> write mock classes where needed to ensure that _all_ source files are
> always compiled.
>
> Note that mock classes don't prevent the use of the real libraries :
> jars in lib/local are placed before the mock classes in the classpath
> and are therefore used, if present, to compile the source code.
>
> I have most of this ready on my hard drive, but since this is a change
> in the way we handle external dependencies, I'd like to have your
> opinion before committing anything.
>
> Thoughts ?
>
> Sylvain
>
> --
> Sylvain Wallez                                  Anyware Technologies
> http://www.apache.org/~sylvain           http://www.anyware-tech.com
> { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to