[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19756: ------------------------------------ a) Do you mean you want a root folder called jbosstools-source, and then under that all the individual repo folders? Or just mush everything into the same root folder? (Also, how about just using `unzip -d /path/to/destination/folder`?) Also, since the zip is mandated to be called "jbosstools-src", do you actually want a root folder called "jbosstools-src" with the matching name, or are you intentionally requesting a different folder name? b) The zip, once released, will have the fully-qualified version of JBoss Tools (or JBDS) on it, eg., *jbosstools-4.3.0.Beta1-src.zip*, but the qualifiers _INSIDE_ the zip reflect the version of the _individual projects' versions_. This is why you should see `jbosstools-portlet_Final` and `jbosstools-freemarker_Final` (they're not being built (yet) for 4.3.0.x, so we use their 4.2.x.Final versions). So I guess you want the x.y.z.qualifier versions here, not the 4.3.0.Beta1 version. But what do we do when there are more than one version in a project? For example, jbosstools-server has sources versioned to 1.2.0, 4.3.0, 1.7.0, 3.1.0, ... Would you like me to use the largest number? (This is why I've only used the BUILD_ALIAS and not the pom.xml version(s) for the source folders within the zip. The BUILD_ALIAS is useful, IMHO, and provides information; using the same version as the zip (4.3.0.Beta1) provides no more information than simply using Beta1. And if we use the projects' versions, then as noted above... which one do we use?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)