polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: Javadocs fails
Date Wed, 08 Jul 2015 08:09:16 GMT
Oh... There was magic;
   1. JAVA_HOME is used to find that.
   2. It is still an ERROR on JDK 1.7, but the build doesn't stop. I guess
it is about Exit Code from javadoc executable that changed.

Mystery solved.

Cheers
Niclas

On Wed, Jul 8, 2015 at 11:04 AM, Niclas Hedhman <niclas@hedhman.org> wrote:

> No, I am pretty sure I am on JDK 1.7.0_75. Unless Gradle has some extra
> power to dig up the 1.8 version...
>
> On Wed, Jul 8, 2015 at 10:48 AM, Paul Merlin <paul@nosphere.org> wrote:
>
>> Hey Niclas,
>>
>>
>> > Gang,
>> > The Jenkins build doesn't seem to run with Javadocs generation,
>> Quick check jobs don't but the @daily distributions checks job does.
>> BUT, it does so using Java 7. The missing symbol is reported as a
>> warning and this doesn't fail the build. I presume you're running Java 8.
>> I just added a new @daily distributions check job that runs Java 8 so we
>> don't get caught again.
>>
>>
>> > and when I
>> > do that locally it fails;
>> >
>> >
>> C:\Users\hedmann\dev\qi4j\extensions\indexing-solr\src\main\java\org\qi4j\index\solr\internal\SingleTokenTokenizer.java:40:
>> > error: cannot find symbol
>> >    public SingleTokenTokenizer( AttributeFactory factory, Reader in )
>> >                                 ^
>> >   symbol:   class AttributeFactory
>> >   location: class SingleTokenTokenizer
>> >
>> >
>> > For some reason it can't find a inner class that the compiler has no
>> > problem with.
>> >
>> > First I thought that perhaps the explicit import was required, but that
>> > simply gave me;
>> >
>> >
>> C:\Users\hedmann\dev\qi4j\extensions\indexing-solr\src\main\java\org\qi4j\index\solr\internal\SingleTokenTokenizer.java:23:
>> > error: cannot find symbol
>> > import org.apache.lucene.util.AttributeSource.AttributeFactory;
>> >
>> >   symbol:   class AttributeFactory
>> >   location: class AttributeSource
>> >  ^
>> >
>> >
>> > Does anyone has any idea of what could be going on here, and what to do
>> to
>> > overcome it??
>> And yes, this one is a weirdo ... I tried to change the imports in
>> several ways without success ....
>> BUT, the Solr extension compiles and its tests pass without the
>> incriminated constructor, I mean by removing this constructor. Looks
>> like it is unused.
>>
>> HTH
>>
>> /Paul
>>
>>
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java
>



-- 
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message