I think we'll find more components we use (eg plexus-action) will get
the same treatment.
I think bringing them in (with IP Clearance) is ok in the short term,
since we have a plan to integrate/remove a lot of them.
I'm not sure a separate trunk is really needed - they could be under
continuum/trunk/components and released with the rest of Continuum to
avoid the separate unnecessary vote/release cycle.
- Brett
On 04/08/2008, at 5:40 PM, Olivier Lamy wrote:
Hi,
It looks some plexus components has been moved to the archive path in
the plexus repository.
My proposal is to take a copy of the trunk for this components (used
in continuum) :
- plexus-cache
- plexus-quartz
- plexus-registry
- plexus-taskqueue
In https://svn.apache.org/repos/asf/continuum/components/trunk ?
--
Olivier
2008/7/26 Brett Porter <[EMAIL PROTECTED]>:
On 26/07/2008, at 6:27 AM, Olivier Lamy wrote:
Hi,
Importing where in archiva or continuum svn or somewhere else ?
As I don't have commit access on archiva, I prefer in continuum ;-).
Agree too for plexus-action, formica, msn, jabber ....
Oh, I'm not suggesting any dependency on Archiva. If they are
reusable
enough to be in both we should look to keep them in Plexus. But
many of the
below are unique to Continuum anyway.
- Brett
Thanks
--
Olivier
2008/7/25 Brett Porter <[EMAIL PROTECTED]>:
For those not following plexus-dev, Plexus is being moved and a
lot of
the
components will be archived.
I'd like to suggest we review each and either remove them, bring
them
into
our source tree (after reviewing licensing), or ask that they be
kept
alive.
Here's what I see today, thanks to dependency-convergence:
* plexus-registry[-api|commons] +
* plexus-action
* plexus-command-line
* plexus-formica
* plexus-jabber
* plexus-jdo2 +
* plexus-mail-sender-[api|javamail|simple|test] +
* plexus-msn
* plexus-quartz
* plexus-slf4j-logging
* plexus-taskqueue
* plexus-velocity
* plexus-xwork-integration
+ are the ones that come from Redback as well
The following come uniquely from redback:
* plexus-cache[-api|ehcache]
* plexus-expression-evaluator
* plexus-digest
Is there any of these we want to push to have kept, remove
immediately,
or
attempt to bring in house?
I think maybe plexus-action, formica, msn, jabber and any other
notification
ones could be considered for importing. There was also a
discussion on
the
Archiva dev list related to this, and some suggestions for
replacing some
of
them.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
