If you respin a package for this today, I will be able to test another installation (today).
ERROR 2011-05-06 07:47:07,550 JPAMediaFileManagerImpl:upgradeFileStorage -
ERROR upgrading
java.io.FileNotFoundException:
/home/gangolli/roller_data/uploads/migration-status.properties (No such file or 
directory)
        at java.io.FileOutputStream.open(Native Method)
org.apache.roller.weblogger.business.jpa.JPAMediaFileManagerImpl.upgradeFileStorage(JPAMediaFileManagerImpl.java:713)
org.apache.roller.weblogger.business.jpa.JPAMediaFileManagerImpl.initialize(JPAMediaFileManagerImpl.java:83)

I'm expecting this was just caught and ignored in the from-scratch
installation case?  I tried a post with a simple image to exercise the media
file upload, and it seemed to go just fine.
That problem will only happen if the uploads.dir property is set and
it should not be set unless you are migrating from Roller 4.0.

However, we still have the property in the roller.properties file. So,
the last fix I will make before release is to:
1) remove uploads.dir from the roller.properties file
2) clarify the text in the Install Guide that explains the need for
uploads.dir at migration time

Then, I'll upload new release files and start the release process,
getting them on mirrors and etc.

I'll hold the JBoss and Websphere files back, and make them available
only in at

    http://people.apache.org/~snoopdave/apache-roller-5.0-experimental
  (dir does not exist yet)

Thanks,
- Dave


Reply via email to