hepabolu wrote:
Reinhard Poetz said the following on 10/5/07 09:33:
[moving over a discussion from [EMAIL PROTECTED] to [EMAIL PROTECTED]
Bruno Dumon wrote:
Which also makes me think of it: the Cocoon zone is still running Daisy
1.5. I could do the upgrade, but I'm not sure on the impact this might
have. The maven plugin should be easy to upgrade, but I think the
forrest plugin is also still in use? It could be that it works without
changes but I'm not sure.
I was thinking about an upgrade too but I'd prefer to wait until we
have published the new documentation because I want to concentrate on
that first.
WDYT?
IMO: Best to do the upgrade now. I've done it here with a small site and
it was done in 3 hours (including figuring out the best way to upgrade a
Suse machine to java 1.5).
Daisy 2.0.X changes the name of the document in the url (1.html ->
1-NS.html with NS = a namespacecode), which means you have to redo the
publishing all over again because the link to the Daisy page breaks
after the upgrade.
I don't see a reason why we need the namespace in our published URLs at all. The
Daisy plugin could cut them off.
Basically I'm not against the upgrade but I would like to invest my time rather
in cleaning up and adding docs instead of upgrading the Daisy plugin. In theory
the upgrade shouldn't cause any problems but I learned by experience that
upgrades aren't that smooth as expected most of the time.
Anyway, maybe I find some time over the weekend but I can't promise it ...
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
