portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Ruttimann <roger.ruttim...@earthlink.net>
Subject Re: Reorganizing Jetspeed repository
Date Tue, 03 Jan 2006 19:30:32 GMT
David Sean Taylor wrote:

> Ate Douma wrote:
>
>>>>
>>>> I don't want to restart the discussion we had about this subject last
>>>> month on
>>>> the general@ list, but I'd like to see a more architectural discussion
>>>> first which
>>>> components are to be considered not j2-specific or portals generic
>>>> before we
>>>> start moving things around.
>>>>
>>>
> Why don't we move ALL components out to the jetspeed components project?
> Yes, this does mean everything.... but if that makes it easier to 
> build the system, and to reuse the components to build different 
> configurations of jetspeed, then isnt that a good thing?

Would the configuration drive which components to build?

>
> Im going to give this a try...
>
> /portals
>     /jetspeed-components
>     /jetspeed-api
>     /applications       
>     /bridges
>     /docs
>     /installers
>     /configuration
>         /j2ee-geronimo
>         /j2ee-tomcat
>         /j2ee-jetty
>         /j2ee-jboss
>         /j2me-geronimo
>         /j2me-tomcat
>         /j2me-jetty
>         ....
>        
>
> Here are the top level directories currently in J2:
>
> app-servers    - move to configurations
> applications    - move to applications
> archives    - do we need this?
> commons        - move to jetspeed-components/commons
> components    - move to components
> content-server  - drop
> design-docs    - move to docs
> docs            - move to docs
> etc        - move to configuration
> graphic_design  - move to docs
> installer    - move to installers
> installer2    - move to installers
> jetspeed-api    - move to jetspeed-api
> layout-portlets -
> maven-plugin    - move to configuration
> patched-jars    - ?
> portlet-api    - drop
> src        - move to configurations
> taglibs        - move to applications
> xdocs        - move to docs
>
> Basically we are breaking Jetspeed apart.
> There will be nothing left but configurations!
> We are victims of our own component architecture :)
> Thats why Im leaving the jetspeed name on both the api and components.
> We could also call these portals-api or portals-components or just 
> plain components or api...but I think anything other than the jetspeed 
> name seems a bit destructive. I mean do we want to kill the jetspeed 
> name just after our final release? :)
> Or is jetspeed now nothing more than just another configuration of 
> "components". I think the jetspeed team is in a funny situation. We 
> want others to use our api and components, but we don't want to give 
> up the ownership.
>
> I also think we need to make a pass over the components
> All of the components found under components/portals should be moved 
> to top level components
>
> Are any of the components "jetspeed" specific?
> You could argue that the engine or the pipeline is
>
> As for the build, we need to switch over to Maven-2
> This refactoring and build conversion seems like a lot of work
> Using a branch to do so might be the best solution
> Its either that or we all stop developing against the trunk for a few 
> days and work together to migrate

We should work against the trunk since creating a branch and then merge 
it back to the trunk seems like a big overhead.
Once we are clear on the structure we could just split the work of 
moving components and have it done quickly.

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message