Ant, I would like to understand more about what we mean by top down build here. We didn't use to build SCA and SDO in one go, even when we had a "top down" build. Now the SCA project is growing in complexity with better modularization, in terms of of how various functional areas are modularized and new extensions being added. We are having more abstractions in the SPI, and more than one pluggable implementations. For example, discovery in SPI currently have a JXTA and JMS implementation. Soon there will be a JINI one. Management in SPI has a JMX implementation, someone may want to add a WSDM one later.
I can understand having the ability to build related modules together. However, why would I want the top-down build to build everything, when for example, I am only interested in JMS binding and not Axis binding? When the project goes in complexity, IMHO, it would be easier to treat these functionally different areas separately, rather than building the whole thing together. However, if everyone else is finding this difficult, I am open to discussions on discussing other mechanisms like using different mvn profiles. For me, I haven't found the lack of a "mother of all build" an inhibiting factor. Thanks Meeraj -----Original Message----- From: ant elder [mailto:[EMAIL PROTECTED] Sent: Thursday, March 22, 2007 4:26 PM To: tuscany-dev@ws.apache.org Subject: Re: Compilation status On 3/22/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > > Hi, > > I hate to bring up this issue again, but I really share the pain that > Mario just went through. Don't we think we have room for improvements > to build the stuff in a much simpler fashion? To me, to have a build > for a bundle which consists of a set of the modules working together > at the same level would be really helpful for the poor guys. It's very > difficult to manually coordinate the build across modules even with > published SNAPSHOTs (which I don't see it happens frequently and it's > also very hard because a collection of SNAPSHOTs don't really > establish a baseline for those who want to try the latest code). > > I (assume that I) understand all the rationales and pricinples for > modulization. But I'm really scared by the user experiences. Where is > the reasonable middle ground? > > Thanks, > Raymond +1, I agree with all said here. Not being able to do a top down build is +a real turn off. Its fine if some don't want to use it but i don't think that should prevent us having this facility for those who do think it is useful. ...ant This message has been checked for all email viruses by MessageLabs. ***************************************************** You can find us at www.voca.com ***************************************************** This communication is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender named above immediately. Registered in England, No 1023742, Registered Office: Voca Limited Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire, WD3 1FX. United Kingdom VAT No. 226 6112 87 This message has been checked for all email viruses by MessageLabs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
