[PROPOSAL] Mavenized Build.

[Jason Kary <jk...@cisco.com>]

Hi List,

I would like to propose the following structure for the 'mavenizing' the pluto 
build.

jakarta-pluto/src/dependencies/api  --> API sub-project.
jakarta-pluto/src/dependencies/container --> Container sub-project

This should make it clear Pluto relies on both the conatiner and api source. 
Within each of these directories I suggest we create a standard Maven 
proect.xml file.  (Sample files included.)

I know the Jetspeed-2 source includes components of the product at the top 
level (Jetspeed-2), however I think this can lead to a lot of clutter and 
confusion.

Thoughts?
Jason Kary

Re: [PROPOSAL] Mavenized Build.

[Santiago Gala <sg...@hisitech.com>]

El lunes, 13 octu, 2003, a las 21:53 Europe/Madrid, Jason Kary escribió:

> This should make it clear Pluto relies on both the conatiner and api 
> source.
> Within each of these directories I suggest we create a standard Maven
> proect.xml file.  (Sample files included.)
>
>

AFAIK, pluto *is* the container

portalImpl is just a kind of test driver. This was discussed today 
under "portal services" in the user list

the charter of the project makes it clear also, I think.

Let us try to keep the different scopes clear, or we get be mad very 
fast.