Hi Mike,
As the author of the example web app Jukka mentioned, I wanted to ask
a few questions:
- What build systems other than Maven 1 would you like to see? I felt
one of the advantages of Maven 1 (when I wrote the example) is that
users needed to have it installed anyway to build Jackrabbit, and it
was dead easy to have it build a war. I think the release of
Jackrabbit 0.9 removes that restriction. Give me a list of other
build systems you'd like to see used and I'll try and incorporate them.
- When you say it should be easy to change the WAR to a DB
persistence mechanism, do you mean you'd like the sample to have
several different Jackrabbit configurations? Do you feel the
documentation for the configuration that is already in the website
could be improved to make this easier? Part of the problem I saw in
trying to put DB persistence into the example web app is that users
would have to configure the settings for their local database anyway.
- If there's anything else you can think of that would make the app
easier to use or a better "first repository" example, let me know.
Anyone else who has suggestions for improvements is also welcome to
chime in. Feel free to email me directly, but it might be preferable
to add comments to the JIRA page: http://issues.apache.org/jira/
browse/JCR-319
Mark
On Mar 13, 2006, at 10:46 AM, Michael Wilson wrote:
This is a great idea. As a new user to Jackrabbit who is looking to
implement a digital asset management system having a drop in WAR would
go a long way towards improving my chance of successes with your
project. Additionally, that WAR should allow the relatively easy
switching to a DB persistence mechanism (and I wanna Pony also).
Great job but a prebuilt WAR, better docs with up-to-date instructions
for installation, and/or a build system not based on maven 1, would
go a
good distance towards allowing me to try your software out. I've been
tinkering to get the darn thing installed as a WAR for the past two
weeks with little success.
Mike
-----Original Message-----
From: Jukka Zitting [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 10:29 AM
To: jackrabbit-dev@incubator.apache.org
Subject: Improving the first impressions
Hi,
With the graduation from the Incubator and the release of
Jackrabbit 1.0
getting closer, we can expect to receive a fair amount of external
interest in near future. This is a great chance to attract new
users and
contributors, and I'd like us to make the most of this opportunity.
The crucial time for attracting new users are the first few minutes
after a user arrives on the Jackrabbit web site or decides to try
using
Jackrabbit. I'll focus on these moments for the next few weeks and I'd
like to welcome all of you contribute in whatever way you like. Ideas,
comments, documentation, example applications, and bug reports or
fixes
are all welcome. What do you think are the main issues that negatively
affect the first impressions of a new user? Is there something that we
could do to make the first few minutes smoother?
I'm currently rewieving the First Hops document for improvements (see
JCR-348 and JCR-351), but there are also a lot of other opportunities
for improvement starting from editing the Jackrabbit front page.
Please reply with your ideas or file improvement requests to Jira!
One exciting opportunity is taking the example web application
contributed by Mark Slater and enhancing it to create a simple drop-in
war file that could serve as an easy-to-install and easy-to-play-with
introduction to Jackrabbit. This is by no means a trivial task, but a
team of a few contributors could well come up with great results. Any
volunteers? I'd be happy to help coordinate such a team.
BR,
Jukka Zitting
--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftsmanship,
JCR consulting, and Java development
