Geert Bevin <[EMAIL PROTECTED]> writes:

>>> The easiest way to setup a development environment for another
>>> servlet
>>> container is to just develop inside WEB-INF/classes. You will have to
>>> setup nothing then, not even the rife.webapp.path JVM property.
>> Right, I had that idea too.
>> That would mean however, that I'd do everything differently than
>> intended by the IDEA guys. :)
> ... so?

Is this a "so what?", or a "how so?"? :)

I'll assume the second one:

IDEA collects the relevant data and copies or compiles it into the
directory `exploded/' which contains the `WEB-INF/'. So `exploded/' is
practically the whole compiled application, ready to be wrapped into a
`.war'.

So I kindof fail to imagine a way to keep my `*.java' files under
`WEB-INF/classes' and stay somehow consistent with IDEA's intended use
patterns.

If you do, enlighten me please. :) Maybe I'm just grossly missing the
point...

>> I'd strongly prefer to just symlink my `exploded/' into
> Why?

It appears...cleaner to me. The "*.java" files are clearly seperated
from the result.

Anyway, if there'll ever anyone search a solution for this problem,
JetBrains already answered me:

--8<---------------cut here---------------start------------->8---
Create source directory e.g. 'resources', move your sub-directories in
that place.
--8<---------------cut here---------------end--------------->8---

The files are now twice inside (once next to WEB-INF and once where it
belongs to) but yet it works fine and I can do my symlink magic. :)
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users

Reply via email to