Geert Bevin <[EMAIL PROTECTED]> writes: >>> It's thus not able to auto-compile them when hot swap fails to update >>> the class file, or when you're using annotation or continuations >>> (which aren't hot-swappable). >> There's nothing to auto-compile: > Of course there is: the element implementations. You just don't allow > RIFE to access the sources.
I'm doing RIFE seriously for 1,5 days so I don't know what you exactly mean by that and it's perfectly possible that I talk crap. If you'd be so nice: A RTFM-link about this? But again: Is there a way to tell RIFE where to find the sources? >>>> But I won't be able to convince you about IDEA anyway. ;) >>> I use IDEA when I need it, just as I use Eclipse and Netbeans. It's >>> not my favorite IDE though, and that's mainly because it's always >>> felt very inflexible about your project structure. >> That's the problem of most IDEs and the reason, why I use Emacs >> outside Java. Maybe I'll have another look at X-Develop when 2.0 is >> stable. The public betas weren't useable when I checked the last >> time. > Eclipse and Netbeans doesn't have that problem either. Imho IDEA > really seems the most restrictive of the bunch here. Soviet software. ;) IDEA helped me alot and felt way more natural than Eclipse when I got started with this stuff. -hs P.S. There's a way to avoid having the files two times in `exploded': Don't mark it as Sources and don't call it `resources' which is reserved for web resources as CSS etc. Add the directory in `Module Settings' -> `Web Module Settings' -> `Web Resource Directories' with `/WEB-INF/classes' as `Path Relative to Deployment Root'. Works. :) _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
