Combined reponse to several messages:
On Dec 23, 2008, at 3:24 PM, Philippe Marschall wrote:
Is there a possibility that Magnolia 4.0 will ship with Jackrabbit
1.5?
Hmmm. A possibility, yes. But I wouldn't bet on it; we probably won't
have time to ensure everything works perfectly to afford delivering by
default. As Jan suggested, if there's anything specific you'd need,
let us know, that might convince us ;)
Also, if we wouldn't *deliver* Magnolia with Jackrabbit 1.5 does not
mean in any way that it wouldn't work with it; it probably will work
flawlessly. Replace the jars, or update/specify the dependencies if
you use Maven, and presto. I haven't checked yet, but I don't think
there's been an api change that would prevent it to work with the
current Magnolia code.
On Dec 23, 2008, at 10:41 PM, Ruben Reusser wrote:
I am honestly kind of concerned about magnolia 4.
You do realize the difference between a milestone and a release
candidate, right ? This one is close-ish to being feature complete,
but definitely not ready for prime time just yet.
The approach to use freemarker as the base technology for
templating
About your comment on the release notes: if they don't say so, they
should: they're a *draft*. (the fact that they're on the wiki and not
on the documentation website should have been one hint, the fact that
Magnolia 4 isn't released another) If they insist on the FreeMarker
features, well, it's because they're new; why would *release* notes
mention something that's existed forever and hasn't changed ?
may be good for magnolia as a company but is it
really good for magnolia as a product?
Hmm, care to explain what you meant here ? How does that differ ?
It feels wrong to use
JSP now for templating but that is what the customers expect
- they are afraid of a not so well known technology where
they can not find any resources for in their local market.
Two things: FreeMarker is in many respect superior, BUT most of all,
we are NOT dropping JSP support AT ALL. Where this idea comes from I
don't know. With 4.0, one can mix and match JSP and FreeMarker page
and paragraph templates at will. So if you'd fancy having a particular
paragraph in FreeMarker in an existing jsp-based project, you can. But
you don't have to.
On Dec 24, 2008, at 9:03 PM, Andreas Schaefer wrote:
Well, I gave Magnolia 4 m2 a shot but more or less all sample pages
fail to render (searchResultFTL), containing illegal characters
(sample-jsp) and other issues.
The current new dev-oriented samples are far from mature and
thoroughly tested. We wanted to get them even as-is in m2 for the sake
of putting the idea out.
As always, reports on Jira (against the trunk though in this case) or
patches are always welcome, if you want this fixed faster ;)
I downloaded the Tomcat Bundle for Java 1.5, running this on Mac OS
X 10.5.5 with Java 1.6.
BTW even for Magnolia 3.x but now also for 4 the rendering of
Magnolia on Safari fails.
Same as for Ruben - care to explain? I am not saying Magnolia is
flawless on Safari, but it'd be nice if, if something indeed doesn't
work as it should, you'd take the extra second it'd take to say what
and how stuff doesn't work and what you'd expect. I use Safari (almost
exclusively unless I need firebug...) and at least since 3.6 (or some
update of Safari) haven't had any noticeable problems ... ?
Cheers and thanks for the feedback,
-greg
ps: Happy new year from Magnolia ! :)
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
