Douglas Hurbon wrote:
On Nov 30, 2005, at 4:03 AM, Andreas Hartmann wrote:
Douglas Hurbon wrote:
[...]
The question is, should I just start using 1.4? Will headaches of
the alpha version outway the headaches of building already built
components myself?
And which version? 1.4 alpha1? I grabbed the trunk version the
other day, but haven't tried to compile it yet. (redhat
linux/java1.5/tomcat).
The major points when moving to (a future stable version of) 1.4 are
- content migration
- migration of custom functionality
IMO you should move to 1.4 only if you can answer all of these
questions with "yes":
- Can the editors continue to use 1.2 until 1.4 is released?
(the content storage is likely to change, so I'd not recommend
to store content in 1.4 unless you're willing to do migrations
after you update Lenya)
You mean 1.4's content storage (jcr yes?) will likely change between now
and its release? Obviously it has changed from 1.2 to 1.4.
Yes, there will probably be changes which require content migration
between 1.4-dev's current state and the release.
- Can I afford a content migration when 1.4 is released?
(we'll provide a content migration tool, but we can't promise
that your doctypes, site structure etc. will be supported to 100%)
From 1.2 to 1.4, or from 1.4dev to 1.4release?
Both, but we'll rather support migration from 1.2 to 1.4 than
from any state of 1.4-dev to 1.4.
- Can I afford to migrate my custom functionality to a new API,
or even to a new framework (Ant tasks -> usecase framework)?
I assume here you mean 1.2 task-based functionality to the new usecase
framework in 1.4.
Yes, exactly.
If I understand you correctly, and my own situation, I'm inclined to
think it makes more sense to keep building on 1.2, and then at some
point in the future, migrate from 1.2 to 1.4. It sounds like the
migration from 1.4dev to 1.4 release might be just as hard as from 1.2
to 1.4. Yes?
The API to build functionality on won't probably change very much.
Maybe the package and class names change, but the basic concepts
are quite stable. If you have unit tests for your components, it
will probably not be hard to migrate from the current 1.4-dev to 1.4.
Content migration will probably more complex, since the whole
JCR repo layout is being reworked.
HTH,
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
