Ok so that sounds more like tuscany/java/sca/extensions/axis2 and tuscany/java/sca/extensions/script etc, and within that:
tuscany/java/sca/extensions/axis2/binding tuscany/java/sca/extensions/axis2/databinding tuscany/java/sca/extensions/axis2/itests/... tuscany/java/sca/extensions/axis2/samples/... tuscany/java/sca/extensions/axis2/tools I'll start on doing this. ...ant On 1/24/07, Jim Marino <[EMAIL PROTECTED]> wrote:
On Jan 24, 2007, at 4:31 AM, ant elder wrote: > On 1/24/07, Jim Marino <[EMAIL PROTECTED]> wrote: >> >> I've converted most of the binding and container extensions to >> reference the 0.1-pre-spec-SNAPSHOT kernel. Also, I started to >> convert the samples under java/samples/sca/ specifically: >> >> - calculator >> - echo.binding >> - inner.composite >> - loanappconversation >> - simplecallback >> - spring >> - spring.simple >> - supplychain >> >> I *did not* convert any of the web app, binding or container >> extension samples (with the exception of Spring). As part of the >> reorganized build tree outlined by Jeremy, these samples will be >> grouped with their respective extensions. It would be helpful if >> people working in those extension areas can take this move on as well >> as change the samples to refer to the kernel 0.1-pre-spec-SNAPSHOT. >> This will allow the extensions to be developed and released >> individually. > > > So if I was to go ahead and do this for things like Axis2 and the > various > dynamic language containers then what is the expected structure? Do > they > stay under services or move to new folder, and do they include > things like > the itests as well? > > For example: > > tuscany/java/sca/axis2/binding > tuscany/java/sca/axis2/databinding > tuscany/java/sca/axis2/itests > tuscany/java/sca/axis2/samples > tuscany/java/sca/axis2/tools > > Another question, so far the only things changed to use > 0.1-pre-spec-SNAPSHOT are the containers, bindings, databindings, and > samples, everything else, like other things in the services or the > runtime > folders haven't changed over. Is this just a point in time thing or > is it > not the intention to change them? I guess I'm not clear about if > the kernel > release is just the things in sca/kernel or if its also other > things, and if > so should there be some more restructuring of the folders? > > ...ant There were a few emails outlining this in detail a while back to the list. If you cannot find them, let me know and I will try and dig them up. Basically, the following: 1. Extensions will be grouped by how they are distributed. For example, Axis and the WSDL2Java tool will be grouped together. The JTA extension would be grouped by itself since it is released independently. We had planned to flatten the /services tree by renaming it to /extensions and including the extensions directly under it as opposed to grouping by binding or container. 2. Samples would be moved under their extensions. Where they specifically go is up to the extension. For example, samples could be their own separate distribution or they could be bundled directly with the extension. The would be housed under the extension, though. 3. For iTests, it depends on what they are. If they are integration tests for the extension, they should be under the respective extension directory. If not, I would just leave them where they are. Thanks for helping out. Jim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
