On Fri, Jun 25, 2010 at 8:36 AM, Mike Edwards <[email protected]> wrote: > ant elder wrote: > <snip> >>> >>> Folks, >>> >>> I have to say that extending the time taken for the build does not fill >>> me >>> with enthusiasm. >>> >> >> The full build on my machine takes over 45 minutes, including the >> sources build adds not much more so its not very significant to the >> full build time. >> >>> Worse, I really don't want to experience the problems that Kelvin has run >>> into where the source link for Tuscany modules from Eclipse projects >>> points >>> to the repo rather than to the source for those modules inside my >>> Eclipse. >>> >> >> The only way to avoid that now that we do build the sources jars >> sometimes is by building them always so that they don't get out of >> sync. >> >>> Can you assure me that we all are not going to start having more hassle >>> because of this? >>> >> >> Yes, this fixes the problem not causes it. If some new problem comes >> up afterwards that we not aware of today then we can review and make >> any changes as necessary. >> > > Convince me on this point please. > > What I DONT want is to have my Eclipse pointing at the source jars in the > repo when I am working on changes to Tuscany modules in Eclipse. I want > Eclipse to point at the source code in my modules directory that Eclipse is > using. If Eclipse points at the repo, it is going to be out of sync with > the very code that I am working on. I can't imagine anything more annoying. > > >>> For me, local source jars in my repo are most certainly NOT a >>> requirement. >>> >> >> For those people who build in separate pieces and work on releases (eg >> at least me and Kelvin) the correct sources jars are necessary. > > I am all for helping work on releases, but at the moment it sounds as if > anyone using Eclipse to do the new work that goes into those releases will > end up with more hassle, so I'm asking if we can find a better solution for > both. >
Do you have a proposal? ...ant
