6.5 minutes for me to build the source jars with mvn -Psource
On Tue, Jun 22, 2010 at 3:05 PM, ant elder <[email protected]> wrote: > On Tue, Jun 22, 2010 at 2:52 PM, kelvin goodson > <[email protected]> wrote: >> In debugging the otests, my eclipse workspace was showing an odd >> symptom obeing a few lines out of step with the executing code for >> tuscany code. This seems to be to do with the fact that there are >> 2.0-snapshot source jars in my local repo that are 1 day older than my >> 2.0-snapshot jars with classes in. Is there something different I >> must do now to keep these in step as I build? >> >> Kelvin >> > > I hit that the other day too. Its because of the way we build the > source jars which doesn't happen on regular builds. So when you build > a module the jar in you local repo is then up to date but the sources > jar will still be the old one from when a deploy or source profile was > run. > > I wondered about updating the build so the module source jars are > built all the time, the only reason not to is i guess how much extra > time it adds to the build. i'll give it a try to see how much time it > adds. > > ...ant >
