[ https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13835: ------------------------------------ {quote}The installable source bundles are buildable so I actually think it is enough.{quote} So for the use case of "I want to rebuild JBDS from source" you suggest people take a few hundred source plugins, unpack them all, and build them one by one? What we have today is a zip containing 17 subfolders (one per github project) which can be built in series without any futzing other than unpacking the zip. {quote}why don't our maven builds produce -source artifacts?{quote} There has never been a request for that. There has ONLY ever been a request for a JBT and JBDS source zip. Therefore it's more expedient to get the sources when we need them rather than producing and aggregating source zips into a larger JBT and JBDS zip. Do we have a community need for source zips? Surely for the community people can just go to github directly and fetch from the appropriate tag, branch, or SHA? {quote}Also, just to comment on the publish.sh script... {quote} Yes, agreed. That's why I'm refactoring it to rsync.sh so it's just doing an rsync copy, trivially generating MD5s for zips, and cleaning up old builds. See https://github.com/jbosstools/jbosstools-build-ci/pull/119 Are you suggesting you'd rather have the jobs configured to run rsync.sh THEN cleanup.sh as two steps? -- This message was sent by Atlassian JIRA (v6.3.11#6341)