Hi Ryan,
Thanks for the feedback. I'm personally waiting for 1.4.1, which
should make it possible to use the bundle persistence managers with
externalized datasource definitions (no more hardcoding of database
username/password in the webapp)
About the unit tests, I've been bothered about the RepositoryTestCase
before, esp since it won't run from my intellij config, but I've had
no problem from the command line, whether I ran them from the
toplevel project or from magnolia-core. Can you reproduce? What os/
java/maven ?
Cheers
-g
On Feb 8, 2008, at 07:27 , Ryan Gardner wrote:
I just updated my magnolia development setup to use Jackrabbit 1.4
- and it worked just fine with the derby repository.
I suppose I could have dropped in the 1.4 jars in, but instead - I
was was lazy and just modified the parent pom to use 1.4 instead of
1.3.3 for the version for Jackrabbit and its related dependencies...
I was worried at first because the unit tests failed when I built
from the top level, but when I looked at it closer it was because
it's trying to load files from the system and not the classpath so
it seems the tests will fail unless you run it from the magnolia-
core directory.
I haven't tested it more than just the basic level yet, so no
promises... but from the documentation it sounds like 1.4 should
not require any changes to config files to work for existing 1.3.3
installations. (Although it mentions you can add some settings to
enable some new 1.4 features)
I didn't notice any difference in performance - but I only ran it
for about 15 minutes so far :)
Ryan
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
