<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I created a PR to change this in jbosstools-integration-tests.<div class=""><a href="https://github.com/jbosstools/jbosstools-integration-tests/pull/887" class="">https://github.com/jbosstools/jbosstools-integration-tests/pull/887</a></div><div class="">So please keep us posted if it becomes something else eventually.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Martin<br class=""><div apple-content-edited="true" class=""><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 13. 3. 2015, at 5:33, Nick Boldt <<a href="mailto:nboldt@redhat.com" class="">nboldt@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">You can't do shell expansion of variables with dashes in the name.<br class=""><br class="">$ jbosstools-site-stream=4.3.mars<br class="">bash: jbosstools-site-stream=4.3.mars: command not found<br class=""><br class="">$ set jbosstools-site-stream=4.3.mars<br class="">$ echo ${jbosstools-site-stream}<br class="">site-stream<br class=""><br class="">$ export jbosstools-site-stream=4.3.mars<br class="">bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier<br class=""><br class="">More: <br class=""><a href="http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character" class="">http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character</a><br class=""><br class="">So... it doesn't work.<br class=""><br class="">But if you prefer I can use jbosstools_site_stream instead of <br class="">jbosstools_stream. Either way the old one is set to the new one [1] so <br class="">that old jobs can keep using the deprecated one.<br class=""><br class="">[1] <br class="">https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76<br class=""><br class=""><br class="">On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:<br class=""><blockquote type="cite" class="">I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.<br class=""><br class="">Can you elaborate more please ?<br class=""><br class="">/max<br class="">http://about.me/maxandersen<br class=""><br class=""><br class=""><blockquote type="cite" class="">On 12 Mar 2015, at 14:20, Nick Boldt <nboldt@redhat.com> wrote:<br class=""><br class="">TL;DR:<br class=""><br class="">jbosstools-site-stream is now jbosstools_stream; if you use<br class="">jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.<br class=""><br class="">---<br class=""><br class="">I've had to rename the parent pom Maven variable<br class=""><jbosstools-site-stream> in order to reuse it in Jenkins job configs.<br class="">This allows us to override it in Jenkins AND use the same value in shell<br class="">scripts to define where content is published on the server, as per the<br class="">new reorg going on for JBT 4.3 / JBDS 9 [1].<br class=""><br class="">The new variable is jbosstools_stream; I intentionally renamed it rather<br class="">than just swapping dashes (not allowed in bash variables) for<br class="">underscores (allowed) so it would be more obvious.<br class=""><br class="">[1] https://issues.jboss.org/browse/JBDS-3208<br class=""><br class="">As far as I can tell, the only affected projects are:<br class=""><br class="">jbosstools-build [2]<br class="">jbosstools-central [3]<br class="">jbosstools-integration-tests [4]<br class="">jbdevstudio-product [5]<br class=""><br class="">[2] https://github.com/jbosstools/jbosstools-build/pull/178<br class="">[3] https://github.com/jbosstools/jbosstools-central/pull/325<br class="">[4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884<br class="">[5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280<br class=""><br class="">Note that the old variable is *still in the parent pom*, but it is now<br class="">deprecated & derived from the the new one [6].<br class=""><br class="">[6]<br class="">https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76<br class=""><br class="">--<br class="">Nick Boldt :: JBoss by Red Hat<br class="">Productization Lead :: JBoss Tools & Dev Studio<br class="">http://nick.divbyzero.com<br class="">_______________________________________________<br class="">jbosstools-dev mailing list<br class="">jbosstools-dev@lists.jboss.org<br class="">https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br class=""></blockquote></blockquote><br class="">-- <br class="">Nick Boldt :: JBoss by Red Hat<br class="">Productization Lead :: JBoss Tools & Dev Studio<br class="">http://nick.divbyzero.com<br class="">_______________________________________________<br class="">jbosstools-dev mailing list<br class="">jbosstools-dev@lists.jboss.org<br class="">https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br class=""></div></blockquote></div><br class=""></div></body></html>