I can write a test project that you can try out with the IBM JDK. I'll push
something to GitHub this afternoon.

On 20 July 2017 at 13:59, Gary Gregory <[email protected]> wrote:

> On Thu, Jul 20, 2017 at 11:54 AM, Mikael Ståldal <[email protected]> wrote:
>
> > On 2017-07-20 03:16, Gary Gregory wrote:
> >
> >> I noticed WARNINGs like:
> >>
> >> [INFO] --- scala-maven-plugin:3.2.2:compile (default) @
> >> log4j-api-scala_2.11 ---
> >> [WARNING]  Expected all dependencies to require Scala version: 2.11.8
> >> [WARNING]  org.apache.logging.log4j:log4j-api-scala_2.11:11.0 requires
> >> scala version: 2.11.8
> >> [WARNING]  org.scala-lang:scala-reflect:2.11.8 requires scala version:
> >> 2.11.8
> >> [WARNING]  org.scalatest:scalatest_2.11:3.0.0 requires scala version:
> >> 2.11.8
> >> [WARNING]  org.scalactic:scalactic_2.11:3.0.0 requires scala version:
> >> 2.11.8
> >> [WARNING]  org.scala-lang.modules:scala-xml_2.11:1.0.5 requires scala
> >> version: 2.11.7
> >> [WARNING] Multiple versions of scala libraries detected!
> >>
> >
> > I have seen this too. It is hard to avoid, and I am quite confident that
> > it is harmless.
> >
> >
> > C:\temp\rc\apache-log4j-scala-11.0-src\log4j-api-scala_2.11\
> >> src\main\scala\org\apache\logging\log4j\scala\Logger.scala:59:
> >> warning: Variable user.getName undefined in comment for class Logger in
> >> class Logger
> >>    * logger.debug(s"Logging in user ${user.getName} with birthday
> >> ${user.calcBirthday}")
> >>                                      ^
> >> C:\temp\rc\apache-log4j-scala-11.0-src\log4j-api-scala_2.11\
> >> src\main\scala\org\apache\logging\log4j\scala\Logger.scala:59:
> >> warning: Variable user.calcBirthday undefined in comment for class
> Logger
> >> in class Logger
> >>    * logger.debug(s"Logging in user ${user.getName} with birthday
> >> ${user.calcBirthday}")
> >>                                                                    ^
> >> two warnings found
> >>
> >
> > Those warnings are bogus and definitely harmless.
> >
> > The build goes on and eventually crashes the IBM JVM:
> >>
> >
> > I have not seen and such crash. Does it crash Oracle JVM too, or only
> IBM?
> > I haven't tried IBM JVM for this.
> >
>
> Only IBM. My review states "Building it worked for me from the src zip with
> 'mvn clean install site'." and just below that I show the 'mvn -version'
> output which includes the Oracle JVM version.
>
> Gary
>



-- 
Matt Sicker <[email protected]>

Reply via email to