You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Luca De Vitis (JIRA)" <ji...@apache.org> on 2017/05/03 14:00:10 UTC

[jira] [Commented] (GROOVY-7906) groovy-2.4.7/bin/startGroovy: line 275: syntax error: bad substitution

    [ https://issues.apache.org/jira/browse/GROOVY-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994924#comment-15994924 ] 

Luca De Vitis commented on GROOVY-7906:
---------------------------------------

These are all useful workaround, but I would like that we don't miss the real issue here.

Bash syntax is kind of a super-set of the sh syntax: it is wrong for an sh script to source a bash script. Might be acceptable the other way around: however I wouldn't do that either. Just pick up one and stick with it.

In fact, I think that "no bash, busybox only" is not correct. You can have bash on alpine, as long as you tell me that you need it.

This problem is coming from the fact that many Linux distributions ship bash as an sh interpreter, but bash is not exactly sh compliant and that led to the misconception that sh and bash are so similar.

> groovy-2.4.7/bin/startGroovy: line 275: syntax error: bad substitution
> ----------------------------------------------------------------------
>
>                 Key: GROOVY-7906
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7906
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 2.4.7
>         Environment: Alpine linux (=> no bash, busybox only)
>            Reporter: Peter Butkovic
>
> running groovy in alpine linux results in:
> {code}
> /tmp/groovy-2.4.7/bin/startGroovy: line 275: syntax error: bad substitution
> {code}
> as a workaround I'm running:
> {code}
> sed -ie '274,275d' /tmp/groovy-2.4.7/bin/startGroovy
> {code}
> prior to invoking groovy



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)