Hi All!
We are almost ready to start a new big project using Magnolia for
reengineering a lot of existing website.
We are going to set up an SVN in order to keep tracks of our source code
and modules.
As newbie to Magnolia (and Maven too, we have only a short course and
read docs and docs alone), we are wondering on bestpractices to work and
develope with Magnolia, SVN and Maven.
We are a team with around 6/8 people involved into the project.
Eclipse will be our IDE.
This is our initial proposal:
- Windows XP as OS
- Eclipse 3.4
- SubEclipse
- Maven as external tool (for generating empty modules)
- Magnolia 3.5.8 EE until first release of webapp, then maybe upgrade..
Folders:
- C:\dev as main dev folder
- C:\dev\workspaces\ as Eclipse ws folder
- C:\dev\lib as external lib folder
- C:\dev\magnolia as magnolia running webapp (tomcat bundle) for local
testing
In Eclipse we are going to create "dynamic web projects" and develope
eahc module as "stand-alone" project. At the end we want to release
modules in a separate common instance of magnolia, where everyone can
test interactions between modules.
Q1) Are there common bestpractices to develop modules with magnolia, svn
and eclipse?
Q2) Our proposal can be a good solution? How can it be improved?
Q3) We need maybe to manage a maven central repository?
Q4) Any suggestions? (Really appreciated!!!)
Thanks in advance..
Matteo
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
