On Friday 04 February 2005 21:42, Leon Rosenberg wrote: Well, actually my IDE (Oracle JDev 10g) supports multiple kinds of projects within one WorkSpace, the web tier being just one of them. Taglibs may be another issue, business and backend tiers, too. All those are strictly seperate things. But for the web part, I just like things being laid out in the project structure exactly like they'll end up in the war file. What's the exact benefit of handling things otherwise? Is there really no difference between things underneath WEB-INF and other resources, 'yet another possible environment'? That may be true, but still, I want to control what lands here and what there in the build. In fact, before the build, anytime. Not only on Fridays. Just a matter of taste, I guess, but still.
-- Chris And yes, I know Ant. 'They came from the Desert'. Remember that old Amiga game? > This is actually the moment i expect Jack Dakota to jump out of the > bushes > > :-) > > What do you do, if you habe more than one build target? > How you separate the libs for the stand-alone application or scriplet > from those > you need only for taglibs? > Tell me your jsps aren't packaged as the rest of the code... > You are probably 'implementing' constant interfaces? > > Forgive me, it's Friday... > > > But to be serious again: > <snip> > I like the idea of having all the files related to a project in > the same parent folder. > </snip> > > I think WEB-INF doesn't belong to the project, since it's neither a > source nor a configuration file/requirement. It's just part of > specification of one of possible environments. And by the way, > hitting ant button in eclipse or a key-shortcut is as fast as hitting > ctrl-s :-) > > Regards > Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
