You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by Dave Johnson <da...@rollerweblogger.org> on 2005/11/22 22:40:55 UTC

Roller 2.0 upgrade guide ready for review

Here's the promised Roller 2.0 upgrade guide:
http://rollerweblogger.org/wiki/Wiki.jsp?page=UpgradeGuide_2.x

If you have a chance, please review and let me know what I've left out.

- Dave


Re: Roller 2.0 upgrade guide ready for review

Posted by Dave Johnson <da...@rollerweblogger.org>.
Thanks Matt.

Comments below...


On Nov 22, 2005, at 4:52 PM, Matt Raible wrote:
> 1. I typically have many custom files inside my roller directory.  For
> this reason, it's easier for me to copy the new install over the old
> one and look for duplicate JARs.

Me too and the copy-over approach always bites me, so I don't really
want to recommend it. There are lots of new jars in 2.0.


> 2. I usually edit roller.properties after a new install - is there an
> easier way to maintain custom properties?

Yes, check the configuration guide. I keep my dozen or so property
overrides in tomcat/conf/roller-custom.properties. You shouldn't need
to touch WEB-INF/classes/roller.properties.

http://rollerweblogger.org/wiki/Wiki.jsp?page=ConfigurationGuide_2.x


> 3. I wouldn't recommend the check script.  The last time I ran it, it
> deleted all the posts I'd added during OSCON (which were related to a
> new "Open Source" category I created).

I will remove references to it.


> 4. I'd recommend copying your production install locally to attempt an
> upgrade first.

Good idea, I'll recommend that.

- Dave


> On 11/22/05, Dave Johnson <da...@rollerweblogger.org> wrote:
>> Here's the promised Roller 2.0 upgrade guide:
>> http://rollerweblogger.org/wiki/Wiki.jsp?page=UpgradeGuide_2.x
>> If you have a chance, please review and let me know what I've left 
>> out.


Re: Roller 2.0 upgrade guide ready for review

Posted by Matt Raible <mr...@gmail.com>.
A couple of comments:

1. I typically have many custom files inside my roller directory.  For
this reason, it's easier for me to copy the new install over the old
one and look for duplicate JARs.

2. I usually edit roller.properties after a new install - is there an
easier way to maintain custom properties?

3. I wouldn't recommend the check script.  The last time I ran it, it
deleted all the posts I'd added during OSCON (which were related to a
new "Open Source" category I created).

4. I'd recommend copying your production install locally to attempt an
upgrade first.

Matt

On 11/22/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> Here's the promised Roller 2.0 upgrade guide:
> http://rollerweblogger.org/wiki/Wiki.jsp?page=UpgradeGuide_2.x
>
> If you have a chance, please review and let me know what I've left out.
>
> - Dave
>
>