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.
Pluto is already doing this and I think we should use one standard solution
for all of portals.
And then all committers can update/release new artifacts when needed, especially
to the apache repo like when the maven plugin is updated.
The Bluesunrise repo as generously provided by David has been very valuable, and
I'd expect it to remain so for things like patched or non-ACL supported
artifacts,
but providing our main artifacts through the apache and ibiblio repositories
will
lessen the burden on David to constantly update his and also the load on his
server.
With the new way of building a portal using the maven plugin, downloading of the
artifacts from the remote repositories will increase (a lot) more and more.
Ate
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
