Providing a migration path (wiki page) fueled by a JDiff report
(http://javadiff.sourceforge.net/) should be pretty easy as well.
(http://maven.apache.org/reference/plugins/jdiff/)
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 13, 2005, at 10:12 AM, James Mitchell wrote:
I'm not 100% sure of this myself yet, but it may be a good idea at
this time to pull out the Tiles dependencies from core and provide
them via a separate plugin (see struts/current/plugins).
While this does add another jar to our applications, it would allow
a developer to use either classic Tiles or standalone Tiles for the
foreseeable future, or until classic is deprecated/removed. Core
shouldn't have to care one way or the other, and for the few people
who have extended Tiles, they can continue to use classic even if
1.3.x ships with standalone.
Your thoughts?
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 13, 2005, at 9:55 AM, Craig McClanahan wrote:
On 9/13/05, Ted Husted <[EMAIL PROTECTED]> wrote:
Right now, I'm in the middle of a documentation review. I'm through
Site, and the first part of Core. It's going well. I'm trying to
make
sure that the way we explain everything is consistent with the
subproject approach. I'll continue to work on it day-by-day (unless
there's a Falcon's game on!).
I'm also trying to review the new Chain code, before we ship the
first
cut. This would actually be a good time for a full code review,
but we
should probably resolve any outstanding patches first. (I don't
expect
we have outstanding patches for the new Chain stuff.)
One question is where do we stand on stand-alone Tiles? Are we
comfortable with bringing that up and making it part of Classic
1.3.0,
or do we want to let things perculate a bit first.
I would suggest *not* doing this at this point. When I stop having
to visit
three continents in six weeks, I'm going to have time to propose a
plan for
a pretty radical change to the internal APIs of Standalone Tiles,
to make it
much more friendly to a portlet environment. I would prefer to do
this
before any 1.0.0 of standalone Tiles is ever produced, so that we
have the
freedom to make this sort of adjustments.
Note that this won't affect the vast majority of *users* of Tiles
unless you
are defining your own Controller implementations -- and, for that,
it makes
sense to provide backwards compatible (but servlet specific)
implementations
to ease the transition.
-Ted.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
