[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I did not answer anything about ant or maven scripting. I gave examples of variable declaration in general - this issue applies to both maven, shell and ant etc. And no, the same issue apply to devstudio.redhat.com. Reasons why having 10.0 on devstudio and neon on download.jboss.org is a Good Thing: #1 It is very clear if some publishing went wrong. If 10.0 shows up on download.jboss.org or neon on devstudio.redhat.com we know something got messed up. #2 You do not need to have the full hostname to know what kind of deployment we are looking at. #3 10.0 is the actual version of the product so it has a much clearer meaning to users than Neon. Yes, you could argue then we should use version numbers on jboss tools community - but then see reason #1 And no matter if we use maven, ant or shell - none of this matters if the abstraction in property names are which release stream are being referenced, as opposed to devstudioVersion or eclipseBase. So in short - no advantages to having the exact same for this base path (I 100% agree the further sub paths which we constantly publish/update are good to have aligned), but at lest 3 advantages to have a different base path. -- This message was sent by Atlassian JIRA (v6.4.11#64026)