Peter Donald wrote:
I think we need to mark sandbox code clearly as being sandbox code. To do this we could require that components in this place are put in the package.-1
org.apache.avalon.sandbox.X
I liked the way things were in the old excalibur repository. Where everything was
under the all or sandbox directories. That is very similar to how we are breaking
it up now with the new avalon-sandbox repository. That in itself makes it very
clear that the code is in the sandbox. I liked the way packages and classes could
easily be promoted. The only thing that was confusing was when a given package
had classes both in the sandbox and released repositories. I think we should try
to avoid that in the future where possible...
If you really want to make it more clear that packages are in the sandbox, how about
doing that in the standard for the jar names? ie: excalibur-component-1.0.jar would
be excalibur-sandbox-component-1.0.jar while it was in the sandbox. That should
make it clear to users without requiring much work for them when the package is
finally promoted.
Cheers,
Leif
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
