[
https://issues.apache.org/jira/browse/JENA-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470210#comment-13470210
]
Andy Seaborne commented on JENA-333:
------------------------------------
Restored prfix mapping - test break otherwise looking for a built in prefix.
It seems there are still tests of DAML stuff in Jena in TestOntAssembler.
Together with DAMLMicroReasoner just how much of DAML has been removed from
Jena? Maybe much/all of it is unreachable from the API.
Can we do more removal before the next release?
> Using javadoc 7 causes warning exception in build (DAMLVocabulary, DAML_OIL)
> ----------------------------------------------------------------------------
>
> Key: JENA-333
> URL: https://issues.apache.org/jira/browse/JENA-333
> Project: Apache Jena
> Issue Type: Bug
> Components: Build, Onotology API
> Affects Versions: Jena 2.7.4
> Environment: Java 7 (1.7.0_07) Linux 64 bit. (but not Java 1.6.0_24)
> Reporter: Andy Seaborne
> Priority: Minor
>
> Under java7, the build of jena core gets two stacktraces (marked as warning)
> in javadoc production. Unclear if the javadoc output is materially affected.
> The following two files are:
> com/hp/hpl/jena/vocabulary/DAMLVocabulary.java
> com/hp/hpl/jena/vocabulary/DAML_OIL.java
> It's unclear as to whether DAML_OIL.java problems maybe due to implementing
> DAMLVocabulary and nothing more.
> /usr/lib/jvm/java-7-openjdk-amd64/bin/javadoc \
> -classpath fuseki-server.jar \ -- just a source of compiled Jena and
> all dependencies
> -encoding utf-8 \
> -d jdoc I.java
> The core problem is the form:
> -----------------------------------------------------
> import com.hp.hpl.jena.rdf.model.Resource ;
> import com.hp.hpl.jena.rdf.model.Property ;
> public interface I
> {
> public Resource Property();
> }
> -----------------------------------------------------
> where Property is a class and a method name, which is legal, it just breaks
> javadoc (standard doclet).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
