Take a look at the analysis earlier in the thread, it already explains
some of it.
In particular:
- plexus-utils, plexus-component-api and plexus-spring need to keep
being used (they'll be kept in Plexus SVN though)
- plexus-container is still used in XmlRpc before it can be removed
completely (classworlds is with it)
- plexus-interactivity shouldn't be needed :) It's probably via the
release stuff.
- the mail sender was replaced in Continuum, but still used in redback
- the rest is all used - but some are unique to C listed below and
should be the first ones imported directly into the tree (eg, the
notification stuff).
Thanks,
Brett
On 05/08/2008, at 9:40 AM, Olivier Lamy wrote:
If I look in the directory WEB-INF/lib
plexus-action-1.0-alpha-6.jar
plexus-cache-api-1.0-alpha-2.jar
plexus-cache-ehcache-1.0-alpha-2.jar
plexus-classworlds-1.2-alpha-7.jar
plexus-command-line-1.0-alpha-2.jar (not sure it's needed)
plexus-component-api-1.0-alpha-20.jar (not sure it's needed)
plexus-container-default-1.0-alpha-20.jar (not sure it's needed)
plexus-digest-1.0.jar
plexus-ehcache-1.0-alpha-2.jar
plexus-expression-evaluator-1.0-alpha-1.jar (not sure it's needed)
plexus-formica-1.0-beta-13.jar
plexus-i18n-1.0-beta-6.jar (not sure it's needed)
plexus-interactivity-api-1.0-alpha-4.jar (not sure it's needed)
plexus-jabber-1.0-alpha-4.jar
plexus-jdo2-1.0-alpha-8.jar
plexus-mail-sender-api-1.0-alpha-7.jar (can be replace with using
spring)
plexus-mail-sender-javamail-1.0-alpha-7.jar (can be replace with
using spring)
plexus-msn-1.0-alpha-2.jar
plexus-quartz-1.0-alpha-4.jar
plexus-registry-api-1.0-alpha-3.jar
plexus-registry-commons-1.0-alpha-3.jar
plexus-slf4j-logging-1.1-alpha-1.jar
plexus-spring-1.0.1.jar
plexus-taskqueue-1.0-alpha-8.jar
plexus-utils-1.5.4.jar
plexus-velocity-1.1.4.jar (can be replace with using spring)
plexus-xwork-integration-1.0-alpha-7.jar (not sure it's needed)
I will try to see If we can remove some.
--
Olivier
2008/8/4 Brett Porter <[EMAIL PROTECTED]>:
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/
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
