Apache Wiki wrote:
Please do not edit comments into this text: please use the CharterForWebCommonsRequestForComments
> or post to [http://jakarta.apache.org/site/mail.html General At
Jakarta].
OK, here I am posting :-)
I'd like to suggest 2 things:
1.We prefereably use Maven for the builds, as it helps a lot handling
the dependencies (if we stick to Ant, we should at least use Ivy or M2
Ant stuff for dependency management). For instance, I haven't applied
some patches to the Jakarta Taglibs because my computers are not set for
building them anymore (and I don't have the time/patience to fix it).
2.Regarding the Jakarta Taglibs, we should create the new taglibs from
scratch. I mean, of course we should reuse the code, but we better do
some refactoring first (for instance, eliminating redundant taglibs,
defining a role for TLD names, etc...) - the current Jakarta Taglibs
would then be "frozen in time".
3.What about the Standard Taglibs? Should it be part of this new project
or should it be a separate project. The reasoning here is that, because
that sub-project provide the codebase for JSTL's implementation (and
maybe other JSR taglibs in the future as well, such as the Web Services
taglib), its development activities/cycles might be different from the
"non-standard" ones (we could even try to apply the TCK on such projects
in the future, for instance).
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
