You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Nate McCall (JIRA)" <ji...@apache.org> on 2010/07/29 02:04:17 UTC

[jira] Created: (THRIFT-833) build.xml in lib/java is missing a classpathref attribute for the javadoc task

build.xml in lib/java is missing a classpathref attribute for the javadoc task
------------------------------------------------------------------------------

                 Key: THRIFT-833
                 URL: https://issues.apache.org/jira/browse/THRIFT-833
             Project: Thrift
          Issue Type: Bug
          Components: Compiler (Java)
    Affects Versions: 0.4
            Reporter: Nate McCall
            Priority: Minor
             Fix For: 0.4


make install produces scary looking compile errors while creating java api. These turn out to be of no consequence functionally - just caused by the javadoc ant task not having a classpathref, and thus not finding slf4j, etc. APIs. 

The following patch just adds the test classpath (since this has everything) to the javadoc task:

130d129
<       classpathref="test.classpath"


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


[jira] Assigned: (THRIFT-833) build.xml in lib/java is missing a classpathref attribute for the javadoc task

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury reassigned THRIFT-833:
------------------------------------

    Assignee: Bryan Duxbury

> build.xml in lib/java is missing a classpathref attribute for the javadoc task
> ------------------------------------------------------------------------------
>
>                 Key: THRIFT-833
>                 URL: https://issues.apache.org/jira/browse/THRIFT-833
>             Project: Thrift
>          Issue Type: Bug
>          Components: Compiler (Java)
>    Affects Versions: 0.4
>            Reporter: Nate McCall
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.4
>
>
> make install produces scary looking compile errors while creating java api. These turn out to be of no consequence functionally - just caused by the javadoc ant task not having a classpathref, and thus not finding slf4j, etc. APIs. 
> The following patch just adds the test classpath (since this has everything) to the javadoc task:
> 130d129
> <       classpathref="test.classpath"

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


[jira] Closed: (THRIFT-833) build.xml in lib/java is missing a classpathref attribute for the javadoc task

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury closed THRIFT-833.
--------------------------------

    Resolution: Fixed

Thanks for the heads up. I just committed this.

> build.xml in lib/java is missing a classpathref attribute for the javadoc task
> ------------------------------------------------------------------------------
>
>                 Key: THRIFT-833
>                 URL: https://issues.apache.org/jira/browse/THRIFT-833
>             Project: Thrift
>          Issue Type: Bug
>          Components: Compiler (Java)
>    Affects Versions: 0.4
>            Reporter: Nate McCall
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.4
>
>
> make install produces scary looking compile errors while creating java api. These turn out to be of no consequence functionally - just caused by the javadoc ant task not having a classpathref, and thus not finding slf4j, etc. APIs. 
> The following patch just adds the test classpath (since this has everything) to the javadoc task:
> 130d129
> <       classpathref="test.classpath"

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