[
https://issues.apache.org/jira/browse/JSPWIKI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658408#action_12658408
]
Murray Altheim commented on JSPWIKI-38:
---------------------------------------
Janne,
I'm not going to be able to comment conclusively until I have a chance to
actually download and
try out the 3.0 code, but from what I can see I have a sneaking suspicion that
a large number of
plugins I've developed and perhaps the entire edifice of the Assertion
Framework will become
impossible to migrate forward. There seem to be so many radical changes to the
design, to the
API approach, and while all this is in mind of being improvements, the
complexity of JSPWiki 3.0
compared to previous versions for the developer is going to be either a real
turn-on for some
(who have enormous amounts of time to invest and love tinkering) and a complete
turn-off for
others. I'm frankly going to have to find a huge amount of *time* to simply
digest what has
happened, and as you may guess that's been short lately.
I know you think my comments in this regard are just sour grapes, but I'm
hoping (and I say
this sincerely) that 3.0 hasn't become impossible for me to use, both in terms
of breaking
compatibility with previous extensions I've developed, in terms of the
potential impossibility
of implementing things that used to be simple (JSPs are simple), and in terms
of the learning
curve of technologies now required to develop for JSPWiki. I'm not talking
here about renaming
classes.
Of course, there are separate issues for those migrating from previous versions
and those
coming new to 3.0. There's the changes in installation requirements for
deployers. I really
love the fact that JSPWiki is a really simple install, and I know that's been
an enormous
selling point for the project. By contrast, installing DSpace is a pain for a
lot of people because
it requires knowledge and installation of PostgresQL or MySQL. Not a big deal
for some but
an impenetrable wall for others. A lot of people are driven away by complexity.
Now, I also know that we've already committed to this course. It just seems
that the project is
heading down the road of becoming so complex that it loses the appeal of being
capable of
being hacked by anyone who doesn't understand some rather complex technologies.
What I'm
saying is that I fear you may have lost me with 3.0. That may be my own
failing, but you might
consider that there are others like me. Where the project can remain simple
(and I know some
of the changes you're considering are simplifications, by adding someone else's
complexity)
I'm all for it.
Thanks for listening.
Murray
> Rename packages to "org.apache.jspwiki"
> ---------------------------------------
>
> Key: JSPWIKI-38
> URL: https://issues.apache.org/jira/browse/JSPWIKI-38
> Project: JSPWiki
> Issue Type: Task
> Reporter: Janne Jalkanen
> Assignee: Janne Jalkanen
> Fix For: 3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
