Hi Jim, No, there was no "larger" intent :-). I'm merely trying to get all the source .java files I require into Eclipse (besides having an executable binary of course), so I can step through the flow of control using an sca sample. SDO and DAS are, as you said, largely unrelated - but I did not know which sections of SCA to exclude. Building all of SCA seemed to be the most straightforward option, since it meant not having to weed through the POM's to figure out a build order, if it exists, for myself. If there are any pointers any one of you gentlemen would care to share regarding the same, kindly do so. thanks, snehit (tuscany newbie)
On 2/27/07, Jim Marino <[EMAIL PROTECTED]> wrote:
On Feb 27, 2007, at 12:26 AM, Snehit Prabhu wrote: > Thanks a lot Raymond! Works like a charm. Am building the rest of the > components like so as well. > So there was nothing wrong with the inner POM's. Looks like only a > few minor > changes to the parent directory POM can easily fix the problem. It > is quite > irksome for a newcomer to setup the trunk as of now, since things > dont work > as purported on the webpage right away. Can this be easily fixed? Sorry the web site is a bit out of date - it needs to be updated. The builds works exactly as intended so it is the web site that has the bug :-) I'll try to briefly explain why this is the case... SCA is completely independent from DAS and SDO so it doesn't make much sense to couple them. In SCA, as our modules (e.g. Kernel, Spring support, JPA support, Axis support) are developed and released independently, they are built separately. For example, the Spring and JPA extensions are working off the latest trunk while the Axis extension has not been upgraded yet. Having a topdown build would make this impossible and force us to migrate all extensions at once which has gotten unworkable as their numbers have increased. In the past, we tried having a "build-the-world" option and it pretty much proved unworkable for a number of reasons. I won't go into detail as there have been quite a number of posts to the list over the past several months on this subject (if you are interested in the details the posts can be found in the mail archives) but one of the main issues was that releases (e.g. M1 and M2) took forever to get out due to the difficulty of preparing and syncing all of the extensions. We decided to decouple kernel from extensions and allow them to be released independently. Decoupling their development and release cycles entailed decoupling their builds. I never have found a need to build the entire trunk. Is there something that you are trying to do which requires you to build everything? Jim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
