Paul Hammant wrote:
Leo,IMHO it is. We are moving to a single container. A single Component spec. We have united mailing lists. Now it's time to start with CVS repositories.
I don't think there is enough merit to a copy/symlink solution, on the basis that it is only a move not a real rationalisation.
The proposal of Avalon Components comprises a commit access *and* vote possibility to committers of that project, that are not all from core Avalon. Cocoon would want to partecipate in excalibur, James in Cornerstone... let's just unite them and make that a single space to be.
So? I don't think anybody really cares what the package names are. We will be changing them with eventual backward-incompatible components or new ones.We will be left with some comps using ...org.apache.avalon.excalibur.* org.apache.excalibur.* org.apache.avalon.cornerstone.* ... packaging.
I know, I know. We're always striving to find the best solution though.Seems like we move depots forever......
When Fortress will be released, I'll work to reposition Avalon as
- Avalon Framework
- Avalon Container
- Avalon Components
AF and AC will be in a single repository, with same committers with same access and voting rights. Core Avalon that is.
Avalon Components with also other committers and voters that use Avalon. It will be our link to our user world.
I think it's a worthy goal.
- PaulOk, here is how I thought we could do Avalon Components:
1 - rename jakarta-avalon-excalibur CVS module to avalon-components
1-b - symlink so that you can checkout it as jakarta-avalon-excalibur
for some time
2 - move the cornerstone component dirs under that repo (simple cp)
3 - add them in the "excalibur" build
This would make us almost instantly have a common repo for all components that we can open to the James committers as you say.
The only real work would be to add them to the build of "excalibur", which is not a big feat.
This would be a first step; in the meantime we can still migrate package per package of non-Avalon stuff to JC, and decide about the others as we proceed. But in the meantime this would mean that we have taken a step towards a single component system, and towards a tighter relationship with our users.
Deal?
+0 (ie yes but I have different priorities :)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
