On Wed, Jun 23, 2010 at 5:56 PM, Luciano Resende <[email protected]> wrote: > On Wed, Jun 23, 2010 at 6:09 AM, ant elder <[email protected]> wrote: >> On Wed, Jun 23, 2010 at 1:58 PM, Mike Edwards >> <[email protected]> wrote: >>> ant elder wrote: >>>> >>>> On Tue, Jun 22, 2010 at 3:20 PM, kelvin goodson >>>> <[email protected]> wrote: >>>>> >>>>> 6.5 minutes for me to build the source jars with mvn -Psource >>>>> >>>> >>>> That command doesn't rebuild the classes jars so the 6.5 minutes >>>> includes all the overhead of running maven as well as building the >>>> source jars. When i try several times mvn clean install with/without >>>> -Psource in the modules folder I get: >>>> >>>> 15 minutes 51 seconds >>>> 12 minutes 55 seconds with source >>>> 8 minutes 17 seconds >>>> 9 minutes 2 seconds with source >>>> 8 minutes 14 seconds >>>> 8 minutes 37 seconds with source >>>> >>>> (I guess theres some caching going on is why the time keeps reducing) >>>> Anyway, i think that shows there's not so much extra overhead in >>>> building the source jars and as its quite confusing with them getting >>>> out of sync i think we should change to always build them, so i'll do >>>> that unless someone has a good reason not to. >>>> >>>> ...ant >>>> >>> 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. >> >>> 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. >> >> ...ant >> > > Would configuring Hudson to build and publish the source jars help ? >
It actually makes it worse because at least when the source is really old its more likely to be obvious as the lines in a debugger don't match up at all, but if its recent but not quite up to date then all the lines in a debugger can line up but the code isn't doing what the source in the debugger is showing which is _really_ confusing, i lost many hours debugging a problem due to that yesterday. ...ant
