On Wed, Aug 31, 2011 at 4:46 PM, Eduard Moraru <[email protected]> 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?
Sources packages are generally way bigger that jars. See http://maven.xwiki.org/releases/org/xwiki/commons/xwiki-commons-component-ap... for example. But maybe it's not really an issue to have a maven repository way bigger, storage is not that expensive AFAIK.
Would it be that much of a build time penalty for actually generating source builds for each artefact?
It's not minor but I could not tell you the exact cost.
WDYT?
Thanks, Eduard _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne