I saw this happen again and on a whim did some googling to see if it was reported/fixed:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=547181 and a duplicate https://bugs.eclipse.org/bugs/show_bug.cgi?id=550263 These both seem to think that this is fixed in a September build, which I think would be <dependency> <groupId>org.eclipse.jdt</groupId> <artifactId>ecj</artifactId> <version>3.19.0</version> </dependency> The current Lucene build version is 3.17.0: https://github.com/apache/lucene-solr/blob/master/lucene/common-build.xml#L2039 Is it possible that it is simple to just upgrade the ecj version? Kevin Risden On Thu, Jun 13, 2019 at 6:42 PM Chris Hostetter <hossman_luc...@fucit.org> wrote: > > So, FWIW: these ecj/precommit ERRORS related to "javax.naming.*" > packages/classes still seems to be happening periodically > but unpredictibly & unreliably... > > 1) speaking persnally: it happens on my machine periodically, even with > "ant clean precommit" and then goes away the very next time i run "ant > clean precommit" -- w/o any changes to the source code, working dir, java > version, etc... > > openjdk version "11.0.2" 2019-01-15 > OpenJDK Runtime Environment 18.9 (build 11.0.2+9) > OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode) > > (It's possible it relates to something in the ivy cache, but if so, it can > aparently "self fix" or "self break" w/o any other java processes running > on on the machine in the meantime) > > 2) It also happens periodically to jenkins builds, as recently as > yesterday, on multiple jenkins clusters and diff build OSs... > > https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/5195/ > https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/7988/ > https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/24208/ > https://builds.apache.org/job/Lucene-Solr-Tests-master/3365/ > https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/1360/ > > ...that's just a handful of examples from the past few days, in generally > ERRORs that start with "The type javax.naming." seem to pop up on at least > 1 jenkins build a day. > > The only commonality seems to be builds of *master* using jdk11 > ... it doesn't seem to pop up in any 8x builds (even when using > jdk11 .... i think because precommit on 8x doesn't do this check anymore?) > and it doesn't show up in Policeman master builds using jdk12 & jdk13 > > anybody have any idea WTF is happening here? > > > > > : Date: Mon, 06 May 2019 20:25:46 +0000 > : From: Uwe Schindler <u...@thetaphi.de> > : Reply-To: dev@lucene.apache.org > : To: dev@lucene.apache.org, Erick Erickson <erickerick...@gmail.com> > : Subject: Re: precommit failures > : > : I am not fully sure if the "java.naming" module is enabled by default in > Java 11. Maybe that's a side effect of some global configuration parameter. > : > : Is Java version really fully identical including vendor? > : > : The strange thing is that only ecj breaks. Could it be that you have > older version of ecj in ant's classpath? > : > : Uwe > : > : Am May 6, 2019 7:47:45 PM UTC schrieb Erick Erickson < > erickerick...@gmail.com>: > : >Weirder and weirder. My mac pro precommits successfully, same Java > : >version but my MBP fails every time. > : > > : >> On May 6, 2019, at 9:03 AM, Dawid Weiss <dawid.we...@gmail.com> > : >wrote: > : >> > : >> I had it this morning before committing the fst patch from Mike. > : >> Cleaned the repo, re-ran precommit and it passed... Very strange. > : >> > : >> D. > : >> > : >> On Mon, May 6, 2019 at 5:53 PM Erick Erickson > : ><erickerick...@gmail.com> wrote: > : >>> > : >>> > : >>> Both Kevin Risden and I are seeing: > : >>> > : >>> [ecj-lint] 1. ERROR in > : > >/Users/Erick/apache/solrVersions/playspace/solr/contrib/dataimporthandler/src/java/org/apache/solr/handler/dataimport/JdbcDataSource.java > : >(at line 28) > : >>> [ecj-lint] import javax.naming.InitialContext; > : >>> [ecj-lint] ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > : >>> [ecj-lint] The type javax.naming.InitialContext is not accessible``` > : >>> > : >>> This import hasn’t been changed since 2009. > : >>> > : >>> I'm using: openjdk version “11.0.2” 2019-01-15 > : >>> > : >>> I tried a fresh clone of master and cleaned the ivy cache, still the > : >same problem. But we can't be the only ones seeing this, any clues? > : >>> > : >--------------------------------------------------------------------- > : >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > : >>> For additional commands, e-mail: dev-h...@lucene.apache.org > : >>> > : >> > : >> --------------------------------------------------------------------- > : >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > : >> For additional commands, e-mail: dev-h...@lucene.apache.org > : >> > : > > : > > : >--------------------------------------------------------------------- > : >To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > : >For additional commands, e-mail: dev-h...@lucene.apache.org > : > : -- > : Uwe Schindler > : Achterdiek 19, 28357 Bremen > : https://www.thetaphi.de > > -Hoss > http://www.lucidworks.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org
