Santiago Gala wrote:
El mié, 19-10-2005 a las 13:43 +0200, Ate Douma escribió:
David Sean Taylor wrote:
Santiago Gala wrote:
In following steps, we could try to have a repository where complex
webapps could be maintained, starting with the admin portlets
themselves
(security, pam, palm)
When you say repository, you mean a remote maven repo?
It is not clear to me either what Santiago meant by this, but I
definitely would
like to see us going to use the apache maven repo at
http:/cvs.apache.org/repository
for the -SNAPSHOT and/or -dev builds and the ibiblio repo for
Milestone, RC and FINAL
releases for both bridges and J2 itself.
I was meaning either the local maven repositoy (if you are developing a
war and build it) or a remote repository for the builds that include
them.
Basically a war will be a build artifact produced in the Apache Portals
project, which can be released as such. README, LICENSE and NOTICE files
can be inside WEB-INF, and docs can be served as static content.
Binary releases can bundle wars or not, depending on what we want to
release. My only concerns is that PSML pages are in synchrony with the
actual portlets they reference.
Santiago, do we need a vote on this?
If so, cross posting is confusing me as to what list to vote on.
Maybe it requires voting on both lists since its a cross project move.
I'd like to formally agree with your proposal on moving all the portlet
applications to their respective bridges projects, and additionally
combining the security, pam and palm applications into one
jetspeed-admin.war. The demo app is pretty much testing stuff, not sure
if there's much useful there anyway.
The initial first-time startup time for the application server, is a bad
user experience. We could consider bundling all the common stuff across
Jetspeed's distribution in the shared/lib. This will take some testing
as we have had class loader issues before with this approach.
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
