hehe... I wasn't trying to say it was the best way, just that it works for me. My projects tend to be small, self contained projects.

Leon Rosenberg wrote:
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?

I don't

How you separate the libs for the stand-alone application or scriplet from
those you need only for taglibs?

Doesn't apply to me.

Tell me your jsps aren't packaged as the rest of the code...

? I have JSPs inside the webroot folder.

You are probably 'implementing' constant interfaces?

Nope :-)

Forgive me, it's Friday...

Nothing to forgive. Honest debate going on, nothing to start a jihad over.

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 :-)

I'll try that sometime. For now, my method works for me. I'm pretty sure it works for others too. I was just trying to make the point that having the WEB-INF inside a project isn't as inconceivable as you made it sound like.


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



Reply via email to