Hi Tom,
Thanks for the nice comments :)
Just a couple of quick remarks:
- Modules from the 3.0 era should still work, we added backwards
support for them.
- The archetype will hopefully be updated in the next 2 weeks to
match the 3.5 "style"
- We're about to try and define some guidelines for your question. We
realized we also need this for some internal projects.
- If we have the chance to do a "webapp" archetype, I'll be tempted
to say that you should really hop on the maven train, because it
would make a lots things smoother. OTOH, it's a tool for which you
need a minimal desire to learn it, otherwise it can become frustrating.
- You might to look at some of the modules under community on svn as
examples, although a bunch of them haven't been updated yet either.
Let me know if that helps and if you have more specific questions,
I'll be happy to reply.
Cheers
greg
On Nov 16, 2007, at 18:16 , TomJensen wrote:
First of all, congratulations to the Magnolia team for getting RC1 out
the door. I've been playing around with some of the things like the
filters and dropping in my own servlets and I like the way it is laid
out.
The question that I have in my mind, currently being a 2.1.6 user and
starting a new site in what will be 3.5, is what the recommended
practice is by the team for the custom code and templates? It looks
like everything is moving to modules, which is nice, but I haven't
seen
anywhere stating a best practice for implementing a site with
magnolia.
In the past we've just imported the magnolia war file into eclipse and
added our own code and other files into that project. We don't use
maven currently nor do we have anyone in house who is comfortable
using
it, and it appears that the maven archetype example on the wiki
http://www.magnolia.info/wiki/Wiki.jsp?page=ModuleQuickStart is for
3.0.
Does that still work properly for 3.5 then or are there new pieces
that
need to be put in place?
If the best practice is to create a module of our site implementation
that we put into the war should we just take the samples module jar
and
base our own module off of that?
Thanks,
Tom
----------------------------------------------------------------
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
----------------------------------------------------------------
