Well, in a perfect world, Shale and TI they would depend on Core ;-) But
who wants to create dependencies for dependency sake?
You're correct, now of course we already have the struts-core
(requestprocessor) subproject living next to shale, without dependency.
So we don't really change much in that respect.
One reason why I personally like CORE is because it contains COR, of
course, so it's easy to explain and remember with that pattern. "I use
Struts CORE with XXX" just has a nice modern ring to it. But I repeat
myself...
Wolfgang Gehner
Michael Jouravlev wrote:
On 11/1/05, Ted Husted <[EMAIL PROTECTED]> wrote:
* Instead of having a Struts Classic distribution, we could have a
"struts-core-library" distribution instead, that could also include
other Core compatiblity extensions, like Struts Flow and Struts
Scripting. If we did, then "Struts Classic" would be relegated to a
codename we used to get the "seven dwarfs" ready to ship.
Struts Core sounds like a kernel for all Struts subprojects, while
AFAIK Shale and Ti do not depend on it. So, in a way this name is
misleading. Not that I can suggest something better ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
