[jira] Reopened: (THRIFT-450) Check for log4j at configure time

["David Reiss (JIRA)" <ji...@apache.org>]

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

David Reiss reopened THRIFT-450:
--------------------------------

      Assignee: David Reiss

I found some limitations in my patch.  Fixes attached as v3.

> Check for log4j at configure time
> ---------------------------------
>
>                 Key: THRIFT-450
>                 URL: https://issues.apache.org/jira/browse/THRIFT-450
>             Project: Thrift
>          Issue Type: Improvement
>            Reporter: David Reiss
>            Assignee: David Reiss
>             Fix For: 0.1
>
>         Attachments: 0001-Extend-ax_javac_and_java.m4-to-test-for-specific-cla.patch, 0002-THRIFT-450.-Disable-Java-if-log4j-is-not-available.patch, v20001-Extend-ax_javac_and_java.m4-to-test-for-specific-cla.patch, v20002-THRIFT-450.-Don-t-use-Ivy-if-log4j-is-already-availa.patch, v3-0001-THRIFT-450.-java-Check-for-Apache-Commons-Lang-also.patch, v3-0002-THRIFT-450.-java-Respect-the-global-classpath-durin.patch, v3-0003-THRIFT-450.-java-Propagate-CLASSPATH-from-.-configu.patch
>
>
> The automake setup currently provides no way to disable the use of Ivy for building the Java library.  We should automatically disable it if log4j is already in the classpath.
> This is a nice-to-have for 0.1.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.