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

ASF GitHub Bot commented on MNG-5837:
-------------------------------------

GitHub user josephw opened a pull request:

    https://github.com/apache/maven/pull/50

    MNG-5837: Use a subshell, rather than the 'local' keyword, for POSIX 
compliance

    'local' is not POSIX, but supported by most shells. However, it's not
    supported by Solaris's /bin/sh, so use a subshell instead.
    
    Tested on OS X by invoking with `/bin/ksh`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/josephw/maven 
MNG-5837-avoid-non-posix-local-keyword

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/maven/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #50
    
----
commit 1efce60e0594f7445f946aeb34f89e36907fdaf1
Author: Joseph Walton <j...@kafsemo.org>
Date:   2015-06-07T13:29:39Z

    MNG-5837: Use a subshell, rather than the 'local' keyword, for POSIX 
compliance.
    
    'local' is not POSIX, but supported by most shells. However, it's not
    supported by Solaris's /bin/sh, so use a subshell instead.

----


> Syntax error in bin/mvn on Solaris SPARC
> ----------------------------------------
>
>                 Key: MNG-5837
>                 URL: https://issues.apache.org/jira/browse/MNG-5837
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.3.1
>         Environment: Solaris 10
>            Reporter: Erlend Birkedal
>
> When running {{mvn}} on Solaris 10 we get the following error:
> {code:none}/opt/apache-maven-3.3.1/bin/mvn: syntax error at line 200: `(' 
> unexpected{code}
> Looks like similas issues as in MNG-5658



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to