Personally I don't like it too much at this point because: - we need the builds to be as fast as possible to provide early feedback to developers when something is broken. Generating source/javadoc would delay significantly the build times. We need to try to reduce build times, not the other way around ;) So one way would be to generate sources/javadocs separately but that would work only if we add even more build agents and is a bit complex to set up. - we regularly have disk space issues on the maven machine so this would need to be fixed before we can even consider doing this. Thanks -Vincent On Aug 31, 2011, at 4:46 PM, Eduard Moraru wrote:
Hi devs,
I was wondering why we don`t generate source artefacts for snapshots, just like we do for final versions?
While I do agree that final versions are the important ones, it's often very annoying to have to manually add sources from the filesystem (assuming you have cloned locally the git repo) for all the maven modules that you want to see the code or even the javadoc or method parameter names. For final releases we don`t have that problem because Eclipse and the Maven plugin (for example) can automatically download the sources in the background providing an effortless process. However, while working with snapshots, you are nagged continuously that the sources can not be found automatically and you experience a bit of unneeded frustration :). Not only that
Would it be that much of a storage penalty for the extra sources jars to accompany the snapshot builds? Would it be that much of a build time penalty for actually generating source builds for each artefact?
WDYT?
Thanks, Eduard