Skip to content

Commit

Permalink
Fix jelly of command interpreted, impossible to externalize descripti…
Browse files Browse the repository at this point in the history
…ons that contains variables to be resolved.
  • Loading branch information
nfalco79 committed Jan 8, 2017
1 parent 89ec9ee commit ad01b1a
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 5 deletions.
Expand Up @@ -32,7 +32,7 @@ THE SOFTWARE.
</select>
</f:entry>

<f:entry title="${%command.title}" description="${%command.description}">
<f:entry title="${%command.title}" description="See &lt;a href='${rootURL}/env-vars.html' target=_new>the list of available environment variables&lt;/a>">
<f:textarea field="command" />
</f:entry>
</j:jelly>
Expand Up @@ -23,5 +23,4 @@
nodeJSInstallationName.title=NodeJS Installation
nodeJSInstallationName.description=Specify nodejs installation where npm installed packages to execute the script
nodeJSInstallationName.emptyValue=- use system default -
command.title=Script
command.description=See <a href='${rootURL}/env-vars.html' target=_new>the list of available environment variable</a>
command.title=Script
Expand Up @@ -23,5 +23,4 @@
nodeJSInstallationName.title=Installazione NodeJS
nodeJSInstallationName.description=Seleziona l''installazione NodeJS dove sono presenti i packages npm di cui hai bisogno per eseguire lo script
nodeJSInstallationName.emptyValue=- use system default -
command.title=Script
command.description=Guarda <a href=''${rootURL}/env-vars.html'' target=_new>la lista delle variabili d''ambiente disponibili</a>
command.title=Script

0 comments on commit ad01b1a

Please sign in to comment.