#: Fabrizio Giustina changed the world a bit at a time by saying on  9/27/2005 
12:29 PM :#
Hi Alexandru

On 9/25/05, Alexandru Popescu <dev-list@magnolia.info> wrote:
Sorry to enter this in-house discussion but I would like to say that:
1/ having to manage multiple projects is usually a harder job
2/ separating packages is indeed a very good refactoring step
3/ everything that is actually in magnolia can be organized into the same 
project with the same
sourcebase or at most some separate contrib where some of 'modules' to reside.

This is because I cannot see a Magnolia distribution based on separate modules 
for the moment (but
here I may be completely wrong).

the purpose of this refactoring is exactly moving to a more modular
structure: magnolia already supports modules but we have no way
actually to build them indipendently from the main webapp (since all
the core classes are there).
Another important point is splitting the admin interface stuff, since
we plan to start changing some parts of the framework soon and we need
to break any core dependency... replacing things will be easier in
that way.

Managing and developing multi-modules projects is made pretty easy
with maven and eclipse/wtp... probably the only thing that really
become harder is creating a good site layout (you have a separate tree
for each module, and navigation -out of the box- is pretty confusing)

sorry again for entering this proposal,
we need comments and suggestions from everyone! Thanks for entering
the discussion

fabrizio


Fabrizio I really wouldn't like to sound harsh, but:

1/ as Michael already pointed some other developers have already seen the 
disadvantage of this

2/ the only project building successfully submodules from its source trunk is Spring, but they keep their sourcecode together.

I fully agree that package dependencies should be solved; it is very important.

But I can start writting some simple Ant builds to trigger different modules builds from the same source base. I definitely don't see a reason for multi-projects. In this way we may be able to use maven for all tasks (including building modules), but also keep everything together.

Please let me know what do you think, and we can both start working on the builds. I am not a Maven wizard, but I can say the opposite about Ant ;-).

./alex
--
.the_mindstorm.


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to