Hi Magnolia Team / Company
That is not going to work with me and so I am going to replace Magnolia
with another open-source project or use plain old JSP pages because I
cannot afford to buy a $10,000 license or to waste a huge amount of time
upgrading it. Upgrading within 2.x was bad enough but that is too much.
This is what I had to say on my blog (madplanet.com/weblog):
As a former contributor to JBoss and XDoclet I know how much work goes
into an open-source project and I do not mind if a company does support
an open-source project and sell an advanced version for profit. An
open-source project can be good for companies as well as the community
and can give us all many opportunities. If a company starts to change
the application in a way so that it is incompatible with previous
versions and does not provide any migration path then it starts to trade
in the community for a few paying customer then it is killing the fabric
of the future success of its open-source project which eventually
hampering the success of its for-profit version.
That happened to me with Magnolia, a JSR-170 based (Web) Content
Management System, I started to use two years ago. Even within the major
release 2 an upgrade was difficult and time consuming but I was
successful at the end. Now with the new major release 3 I was told that
there is no migration path except writing my own tool or buying a tool.
This is the straw that finally broke the camel's back. How can I trust
that this is not happening in the next release and that the upgrading
tool is still working. I finally had to pull the plug because I cannot
afford the time to deal with the upgrade especially when there is no
trivial migration because Magnolia use JSR-170 in a non transparent way.
My companies website is too simple to warrant a $10,000 license or
wasting a lot of time with it. I can do it with JSP, a little bit of
HTML and SSH to copy the files around. At the end I probably do not safe
any time but I will spend the effort when I am going to change the web
site and not when I have to upgrade the underlying software. Upgrading
JBoss with Tomcat and a JSP application takes minutes rather than days.
The point that upgrading Magnolia was hardly discussed on their user
mailing list is an indication that they lost touch with the community.
Today they lost another one, me.
Signing off - Andy
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
