Martin Cooper wrote:
On the other hand, creating the project in the Struts sandbox means that it
is immediately open to any Struts committer, all of the resources are
already set up, and getting a release out is dependent only upon a vote to
move the code from the sandbox to the main code line. I'd say that path will
be a whole lot less hassle - unless, that is, you expect the Dojo 1.x plugin
to be a major project that requires additional committers and spans an
extended period of time to get into shape equivalent to that of today's Dojo
plugin.
--
Martin Cooper
I agree transition from googlecode back into Apache is an important
consideration and a googlecode decision should be made only after we
understand the level of effort involved.
My gut feeling is that a complete Dojo 1.x plugin requires significant
effort and additional committers. Others would know better than me
though. Do you have a contact over at the Dojo that :
- is familiar with the current Struts Dojo capabilities and can give
an indication of the effort to migrate to 1.x; or
- more importantly, confirm whether recreating custom tags is a
sensible approach at all.
It may be better for both projects that we make a concerted effort to
demonstrate dojo + struts integration rather than creating another
plugin that encapsulates Dojo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
