Hi Andrew,
Andrew Savory wrote:
Some feedback on Hippo ECM ... Part One :-O
Nice! :)
First of all - it was quite hard to track down where to start, etc.
Lots of blank pages, dead ends .... but you didn't manage to stop me!
You picked an unfortunate moment as we just had a "docathon" session, in
which a lot of changes were committed to the documentation. This
sometimes leads to errors and inconsistencies. I am currently reviewing
and editing.
Even if http://www.hippo-ecm.org/ is just a holding space for now, it
might be less confusing to add some temporary content "Hippo ECM -
docs coming soon" instead of just serving up all the other hippocms
stuff. Or point to http://www.hippo-ecm.org/display/HIPPOECM/Home
http://repodocs.hippocms.org/ is perhaps incorrectly named, since ECM
is more than just the repo?
Agreed. This is only a working location. Once the software reaches a
certain level of usefulness we will relocate the docs and announce their
presence.
"Run Hippo ECM" links to an unhelpful blank page.
"Building with Maven" links to an unhelpful blank page.
These were caused by invalid XML, I fixed them, site deploy is running
at this moment.
Your building with eclipse page [1] could be re-ordered to do all the
eclipse updates in one go, rather than installing subversive, jetty
plugin, jpox, etc as multiple steps? It's quicker and prevents
multiple restarts of Eclipse.
Also, watch out for Window -> Preferences : the Preferences are in
different places depending on platform (on the Mac, it's under the
"Eclipse" menu, Option ','.
From [1], step 9 of installing Eclipse JPOX Plugin, "Add the jars for
jpox-core, jpox-enhancer and bcel to the classpath. Currently the
version 1.2.0-beta-2 is used for JPOX and 5.1 for BCEL; to maintain
consistency with the maven build, check these values in the
jpox-maven-plugin pom file." -- I don't have JPOX jars on my machine,
but I suspect I will after maven does it's thing. Perhaps you could
explain where they should come from? (The jpox site [2] has a wealth
of content, it's not easy to see where to start.)
Good points. We'll take them into account in the next docathon.
The whole process of getting everything working within Eclipse is at
least cumbersome at the moment. We hope to find a better solution soon.
Netbeans seems to be better as it has native Maven integration, but we
still want to support Eclipse as it is widely used within the open
source communities.
That's all for now ...
Thanks for your comments, much appreciated!
Kind regards
Niels
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
