On Monday, March 3, 2003, at 04:13 PM, Bill Burton wrote:
Hello,
Nathan Bubna wrote:Ok, here's where things stand so far as i can see: Commiters: +1 nathan +1 gabe -? geir (sounded like a -1)
It did.
Yeah, it was - sorry about that.
Contributors:
+1 anthony +? tim (not sure where you ended up) -? bill (sounded like -0)
-1 for the way you've proposed it.
What I am in favor of, is keeping the current or similar package structure with tools (generic non servlet), view (servlet specific) and struts. One of my reasons for posting a list of possible tools is to show that there is or will be a need for a generic tools package so it shouldn't be removed.
BUT, that doesn't need to imply multiple jars are required for deployment. The build.xml could still build three jars but the view jar would also include tools; struts jar would include both view and tools. The tools jar would just be generic tools. So no matter what your use, there's still only one jar to deploy. It should be rather easy to fix the build.xml to do this.
Sure - we did it in Vel, having a jar build with all dependencies, and one without.
In this case, I assume most people would use the combination jar, and that should be the build default.
However, having separate build targets to allow those with no interest in servlet stuff to still do it would be easy and convenient.
geir
-Bill
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Geir Magnusson Jr 203-956-2604(w) Adeptra, Inc. 203-247-1713(m) [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
