Ouch.. seems like a bug in Maven (or more likely) this magic
org.rzo.yajsw.os.posix.PosixProcess used by org.everit.osgi.

I guess setting it manually with -Djna.nosys=true didn't help either?


Another reason to have a quick look at the PAX Exam (JENA-879) - which
I'm in the middle of now. It's much more complicated.. :-(

On 2 February 2015 at 20:34, Andy Seaborne <[email protected]> wrote:
> On 02/02/15 11:33, Stian Soiland-Reyes wrote:
>>>
>>> 1/ Build failure
>>> >
>>> >jena-osgi-test fails the build in step "verify"
>>> >
>>> >tried: java-8-openjdk and java-7-openjdk
>>> >
>>> >------------------------
>>> >Exception in thread "main" java.lang.Error:
>>> >
>>> >There is an incompatible JNA native library installed on this system.
>>> >To resolve this issue you may do one of the following:
>>> >  - remove or uninstall the offending library
>>> >  - set the system property jna.nosys=true
>>> >  - set jna.boot.library.path to include the path to the version of the
>>> >    jnidispatch library included with the JNA jar file you are using
>>> >
>>> >         at com.sun.jna.Native.<clinit>(Native.java:142)
>>
>> I'm not sure what JNl library you have, possibly some OS X thing?
>>
>> I'll find out how we can set this jna.nosys property, as it should not
>> be of any worry for this testing.
>>
>> (but it should be of worry if you made an OSGi application which
>> needed that JNI library! :))
>>
>> Do you know if this error is thrown from the Felix or the Equinox
>> test? (As it tests both frameworks)
>>
>>
> (HTML for the formatting)
>
> After #23 I still get the error.  The output is:
>
> ....
> constituent[36]:
> file:/home/afs/sys/apache-maven/lib/aether-util-0.9.0.M2.jar
> constituent[37]:
> file:/home/afs/sys/apache-maven/lib/wagon-http-shared-2.6.jar
> constituent[38]:
> file:/home/afs/sys/apache-maven/lib/org.eclipse.sisu.plexus-0.0.0.M5.jar
> constituent[39]: file:/home/afs/sys/apache-maven/conf/logging/
> ---------------------------------------------------
> Exception in thread "main" java.lang.Error:
>
> There is an incompatible JNA native library installed on this system.
> To resolve this issue you may do one of the following:
>  - remove or uninstall the offending library
>  - set the system property jna.nosys=true
>  - set jna.boot.library.path to include the path to the version of the
>    jnidispatch library included with the JNA jar file you are using
>
>     at com.sun.jna.Native.<clinit>(Native.java:142)
>     at com.sun.jna.Pointer.<clinit>(Pointer.java:42)
>     at com.sun.jna.PointerType.<init>(PointerType.java:25)
>     at com.sun.jna.ptr.ByReference.<init>(ByReference.java:32)
>     at com.sun.jna.ptr.IntByReference.<init>(IntByReference.java:22)
>     at com.sun.jna.ptr.IntByReference.<init>(IntByReference.java:18)
>     at org.rzo.yajsw.os.posix.PosixProcess.<init>(PosixProcess.java:43)
>     at org.rzo.yajsw.os.posix.bsd.BSDProcess.<init>(BSDProcess.java:21)
>     at
> org.everit.osgi.dev.maven.IntegrationTestMojo.execute(IntegrationTestMojo.java:393)
>     at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
>     at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>     at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>     at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>     at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>     at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
>     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
>     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:497)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>
> after which maven crashes out and I get the command line prompt back.  No
> trailing maven [INFO] messages at all.
>
>     Andy

-- 
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718

Reply via email to