Ralph Goers wrote:
The reason I would prefer a separate project for "portal-commons" is
simple. I'm not a committer on Jetspeed. For that matter I've never
even used Jetspeed so it would be completely inappropriate for me to
be. However, I am somewhat familiar with Pluto and know the Cocoon
portal pretty well. So for those of us who want common components it
sounds like what you are proposing is that we should all tailor our
stuff around the existing Jetspeed components - take it or leave it.
Now this may not be the sentiment you meant to convey.
As for the light-weight portal, for me it simply a matter of looking at
the use cases. At the moment the only ones I am aware of are the
Geronimo Admin Console and Pluto's container. My concern with packaging
the light-weight portal in Jetspeed is that it might get lost in the
midst of all the stuff about its big brother, but I see no reason that a
maven based build of a light-weight portal couldn't have dependencies on
Jetspeed and/or common components.
Ralph
Regarding your concern about NOT being a Jetspeed committer, I don't see
that as a problem. If you join any of the Portals projects, you get
commit access to ALL Portals repos. So if, for example, Cocoon portal
was moved into the Portals project, then you would have commit access to
Pluto, Jetspeed, Bridges...
