[daisy] MySQL classpath after 1.5->2.0 upgrade

[Bruno Dumon]

On Fri, 2007-04-06 at 12:25 +0200, Robert Kindl wrote:
> > ${daisy.home} is correct.
> 
> OK - i will try
> 
> > Similarly, you might want to check if the paths of the blobstore and
> > indexstore are still absolute. You can make them relative by using the
> > ${daisy.datadir} variable.
> 
> Already OK
> 
> > Once this is done, you can move around the datadirectory on your system,
> > just specify the new location as argument when starting the repository
> > (while the repository is not running of course).
> > All this is the by default the case for fresh Daisy 1.5-and-up
> > installations.
> 
> I don't agree.
> I first install (tow month ago) fresh 1.5.1
> (daisy-1.5.1-installer-bundled-with-java-jai-mysql.exe).
> Now you release version 2.0 and I decide to upgrade.
> 

I see, this seems to be a Windows-installer specific issue. Maybe
Andreas can address this.

It's interesting that you performed the upgrade from a Windows-installer
based installation. Did you experience any other issues besides the ones
mentioned up to now?

> So fresh installation of 1.5.1 does not contain this as variable
> ${daisy.home} but still as hardcoded path.
> 
> > It was covered by the 1.4->1.5 upgrade instructions
> > http://cocoondev.org/daisydocs-1_5/13-cd/328-cd.html
> > though it might not have been clear that one could actually leave the
> > ${daisy.home} in there.
> 
> You are right - it's written here.
> But this is still issue for fresh installation of 1.5 when upgrading 2.0
> 
> Rob

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno at outerthought.org                          bruno at apache.org