You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Donald <pe...@apache.org> on 2002/03/14 10:18:17 UTC
The great excalibur adventure!
Hi,
Ages ago we decided that it would be nice if excalibur also offered the
possibility of individual bite-sized chunks. I have finally got the time to
do it now and want to start doing it tomorrow if all is still good.
The idea is to end up with excalibur-cli.jar, excalibur-i18n.jar,
excalibur-naming.jar etc and also one excalibur-all.jar (or whatever we want
to call it).
Each of the components that could be separated would be separated out into
little sub-hierarchies and all would be good. We could also locate
documentation and examples in the same little project hierarchy.
Originally I intended to create a new hierarchy and place all products in
there. SO it would look like
jakarta-avalon-excalibur/aut/cli/**
jakarta-avalon-excalibur/aut/naming/**
etc.
However thinking about it again I believe a better approach would be to do
something like
jakarta-avalon-excalibur/cli/**
jakarta-avalon-excalibur/naming/**
...
This however will require a significant amount of hand surgery on CVS
repositories (because I want to keep the revision history).
So I propose the second approach will be used. My first move will be to move
everything in jakarta-avalon-excalibur/ into jakarta-avalon-excalibur/all
and then gradually copy across history as needed into new subproducts.
Each subproject will look very similar to current avalon project
directoriues. Basically it will be like
cli/README
cli/ant.properties.sample
cli/build.xml
cli/src/java
cli/src/manifest
cli/src/xdocs
cli/examples
If you desire any reorgs of this structure now is the time to speak. I will
also start to gumpify these individual products as required and hook them to
various projects who require them.
Anyways I plan to do this 16 hours from now unless someone throws up a red
flag. So commit anything that is pending or else you may have to do a little
bit of work to commit it later. After the initial reorg feel free to exrtact
other bits out overtime aswell.
If all is good I will send out a mail indicating everyone should stop working
on repo and it may be down for an hour or two but after that we should be
good to go.
--
Cheers,
Pete
*------------------------------------------------------*
| "Computers are useless. They can only give you |
| answers." - Pablo Picasso |
*------------------------------------------------------*
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: The great excalibur adventure!
Posted by Stephen McConnell <mc...@apache.org>.
I prefer to see seperation. Currently the build procedures
for the service management stuff is maintained over on
apps/enterprise because its so much easier to keep control
over under a single dedicated build environment - attempting
to maintain this in excalibur general build (currently
version 110) isn't viable.
Cheers, Steve.
> -----Original Message-----
> From: Eung-ju Park [mailto:colus@apache.org]
> Sent: Thursday, 14 March, 2002 11:21
> To: Avalon Developers List
> Subject: Re: The great excalibur adventure!
>
>
> ----- Original Message -----
> From: "Paul Hammant" <Pa...@yahoo.com>
> To: "Avalon Developers List" <av...@jakarta.apache.org>
> Sent: Thursday, March 14, 2002 6:44 PM
> Subject: Re: The great excalibur adventure!
>
>
> > Peter,
> >
> > My own view is that *no changes* to the source tree are needed.
> I think
> > it is only an issue for jaring.
>
> I agree with Paul's opinion.
>
> >
> > excalibur-logger-4.1.2.jar etc.
> >
> > Each time I see a disparate source tree, when one could have done, then
> > my heart breaks a little. (Don't beat me with apps/ ;-)
> >
> > - PAul
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: The great excalibur adventure!
Posted by Eung-ju Park <co...@apache.org>.
----- Original Message -----
From: "Paul Hammant" <Pa...@yahoo.com>
To: "Avalon Developers List" <av...@jakarta.apache.org>
Sent: Thursday, March 14, 2002 6:44 PM
Subject: Re: The great excalibur adventure!
> Peter,
>
> My own view is that *no changes* to the source tree are needed. I think
> it is only an issue for jaring.
I agree with Paul's opinion.
>
> excalibur-logger-4.1.2.jar etc.
>
> Each time I see a disparate source tree, when one could have done, then
> my heart breaks a little. (Don't beat me with apps/ ;-)
>
> - PAul
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: The great excalibur adventure!
Posted by Stephen McConnell <mc...@apache.org>.
This is compounded by the fact that Excalibur is somewhat mixed
in terms of "integrity" of what's there. Its very difficult to
know what the status is of different packages in Excalibur. Some
packages in scratchpad are preferential to the main source tree,
however other scratchpad packages appear to be historical
artefacts - and its really only possible to find this out by
emailing original contributors.
Exalibur today is not the sword that the name implies. It is
much more a bunch a daggers, take what you need and do with it
what you will. Excalibur has the potential to be a sword of
legend, but its not there yet - and recognising the difference
between a sword and a dagger is important.
Cheers, Steve.
> -----Original Message-----
> From: Peter Donald [mailto:peter@apache.org]
> Sent: Thursday, 14 March, 2002 12:56
> To: Avalon Developers List
> Subject: Re: The great excalibur adventure!
>
>
> On Thu, 14 Mar 2002 20:44, Paul Hammant wrote:
> > Peter,
> >
> > My own view is that *no changes* to the source tree are needed. I think
> > it is only an issue for jaring.
> >
> > excalibur-logger-4.1.2.jar etc.
> >
> > Each time I see a disparate source tree, when one could have done, then
> > my heart breaks a little. (Don't beat me with apps/ ;-)
>
> The problem is then it is massively harder for people to come and look at
> things and adopt them. I have tried to get people to adopt stuff from
> excalibur inside my company but they looked at size of excalibur and
> basically said no.
>
> Breaking them down into source tree makes it much easier for
> people to take
> the little bits piecemeal if they want to and need to. Separate
> sourfce trees
> also makes it much easier to develope and track inter-package
> dependencies.
>
> --
> Cheers,
>
> Pete
>
> ---------------------------------------------------
> "Wise men don't need advice. Fools don't take it."
> -Benjamin Franklin
> ---------------------------------------------------
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: The great excalibur adventure!
Posted by Peter Donald <pe...@apache.org>.
On Thu, 14 Mar 2002 20:44, Paul Hammant wrote:
> Peter,
>
> My own view is that *no changes* to the source tree are needed. I think
> it is only an issue for jaring.
>
> excalibur-logger-4.1.2.jar etc.
>
> Each time I see a disparate source tree, when one could have done, then
> my heart breaks a little. (Don't beat me with apps/ ;-)
The problem is then it is massively harder for people to come and look at
things and adopt them. I have tried to get people to adopt stuff from
excalibur inside my company but they looked at size of excalibur and
basically said no.
Breaking them down into source tree makes it much easier for people to take
the little bits piecemeal if they want to and need to. Separate sourfce trees
also makes it much easier to develope and track inter-package dependencies.
--
Cheers,
Pete
---------------------------------------------------
"Wise men don't need advice. Fools don't take it."
-Benjamin Franklin
---------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: The great excalibur adventure!
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter,
My own view is that *no changes* to the source tree are needed. I think
it is only an issue for jaring.
excalibur-logger-4.1.2.jar etc.
Each time I see a disparate source tree, when one could have done, then
my heart breaks a little. (Don't beat me with apps/ ;-)
- PAul
>Hi,
>
>Ages ago we decided that it would be nice if excalibur also offered the
>possibility of individual bite-sized chunks. I have finally got the time to
>do it now and want to start doing it tomorrow if all is still good.
>
>The idea is to end up with excalibur-cli.jar, excalibur-i18n.jar,
>excalibur-naming.jar etc and also one excalibur-all.jar (or whatever we want
>to call it).
>
>Each of the components that could be separated would be separated out into
>little sub-hierarchies and all would be good. We could also locate
>documentation and examples in the same little project hierarchy.
>
>Originally I intended to create a new hierarchy and place all products in
>there. SO it would look like
>
>jakarta-avalon-excalibur/aut/cli/**
>jakarta-avalon-excalibur/aut/naming/**
>etc.
>
>However thinking about it again I believe a better approach would be to do
>something like
>
>jakarta-avalon-excalibur/cli/**
>jakarta-avalon-excalibur/naming/**
>...
>
>This however will require a significant amount of hand surgery on CVS
>repositories (because I want to keep the revision history).
>
>So I propose the second approach will be used. My first move will be to move
>everything in jakarta-avalon-excalibur/ into jakarta-avalon-excalibur/all
>and then gradually copy across history as needed into new subproducts.
>
>Each subproject will look very similar to current avalon project
>directoriues. Basically it will be like
>
>cli/README
>cli/ant.properties.sample
>cli/build.xml
>cli/src/java
>cli/src/manifest
>cli/src/xdocs
>cli/examples
>
>If you desire any reorgs of this structure now is the time to speak. I will
>also start to gumpify these individual products as required and hook them to
>various projects who require them.
>
>Anyways I plan to do this 16 hours from now unless someone throws up a red
>flag. So commit anything that is pending or else you may have to do a little
>bit of work to commit it later. After the initial reorg feel free to exrtact
>other bits out overtime aswell.
>
>If all is good I will send out a mail indicating everyone should stop working
>on repo and it may be down for an hour or two but after that we should be
>good to go.
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>