You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2016/07/02 18:46:10 UTC

[jira] [Resolved] (CRYPTO-102) Makefile.common defines JAVA/JAVAH/JAVAC incorrectly for Windows

     [ https://issues.apache.org/jira/browse/CRYPTO-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved CRYPTO-102.
-------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

CRYPTO-102 Makefile defines JAVA/JAVAH/JAVAC incorrectly for Windows

Project: http://git-wip-us.apache.org/repos/asf/commons-crypto/repo
Commit: http://git-wip-us.apache.org/repos/asf/commons-crypto/commit/5b44a003
Tree: http://git-wip-us.apache.org/repos/asf/commons-crypto/tree/5b44a003
Diff: http://git-wip-us.apache.org/repos/asf/commons-crypto/diff/5b44a003


> Makefile.common defines JAVA/JAVAH/JAVAC incorrectly for Windows
> ----------------------------------------------------------------
>
>                 Key: CRYPTO-102
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-102
>             Project: Commons Crypto
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 1.0.0
>
>
> Makefile.common defines the following:
> JAVA  := "$$JAVA_HOME/bin/java"
> JAVAC := "$$JAVA_HOME/bin/javac"
> JAVAH := "$$JAVA_HOME/bin/javah"
> This results in the the following being used at run-time:
> "$JAVA_HOME/bin/java"
> etc
> This is OK for shells that support $NAME as a variable reference; Windows for one does not.
> The variables should be resolved at definition time.



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