compiling eid-viewer on slackware 13.1

[Jan Herrygers]

Hello

I've tried compiling the eid-viewer (svn_revision 52) on slackware
13.1

I downloaded the source tarball from eid-viewer-continuous
I untarred it.
I ran "./configure" without any options
I ran make.

First the build process failed with this warning:

Unable to locate the Javac Compiler in:
/usr/lib64/java/../lib/tools.jar

which is to be expected since the jar in question is at /usr/lib64/
java/lib/tools.jar and not /usr/lib64/lib/tools.jar
A temporary symbolic link let me work around this.

Then the tests failed.
First because I didn't have an eid in the reader.
Then for some reason I don't understand:
-------------------------------------------------------------------------------
Test set: be.fedict.eidviewer.lib.TestView
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.034
sec <<< FAILURE!
initializationError(be.fedict.eidviewer.lib.TestView) Time elapsed:
0.013 sec <<< ERROR!
java.lang.Exception: No runnable methods
at
org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMethods(BlockJUnit4ClassRunner.java:
154)
at
org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:
112)
at org.junit.runners.ParentRunner.validate(ParentRunner.java:
253)
at org.junit.runners.ParentRunner.<init>(ParentRunner.java:55)
at
org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:
56)
at
org.junit.internal.builders.JUnit4Builder.runnerForClass(JUnit4Builder.java:
13)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:
57)
at
org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:
29)
at
org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:
57)
at
org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:
24)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:
45)
at
org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:
56)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:
96)
at
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:
209)
at org.apache.maven.surefire.Surefire.run(Surefire.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:
345)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:
1009)

The XML version of this "surefire-report" is on http://pastebin.com/VSjVEaUe

I don't know if it is relevant, but I have eid-mw 4.0.0 svn 929
installed.

Can you point me in the general direction of how to solve this error?
Also, is there a cleaner way to let the build process find the jdk?

[Jan Herrygers]

Follow-up:

The java error was because I had both the JRE and the JDK packages
intalled, and maven found the JRE before it found the JDK. Removing
the JRE (and reinstalling the JDK just to be sure) solved that part of
the problem.

Getting to the TestView had nothing to do with having or not having a
card in the reader. The AppTest is a bit more torough when you do have
a card in the reader, but it doesn't fail if you don't.

There's no real progress on the TestView front, but I thought I'd post
this update to let you know I'm still working on it in case you guys /
are/ reading this.

[Jan Herrygers]

Upgrading maven from 2.2.1 to 3.0.3 let the make process complete with
BUILD SUCCESS.

However, "mvn clean test" still ends in build failure. I've posted the
output from this command here: http://pastebin.com/hXU1Mvcy
It doesn't even get to the TestView test anymore.

I will keep looking into this and post new info as I find it.
Eventually I want to make a SlackBuild script for the eid-viewer, but
for now I think I need to learn more about how it is compiled, and why
the tests fail.

[Jan Herrygers]

From what I have discovered, there is no TestView unit test. Don't
know where maven2 got the idea.
The warnings about the jboss repository were caused by the eid-applet
depency. This had already been fixed upstream, but not in the maven
repositories.
Commenting out the maven1 repository with "legacy" layout fixed a
bunch of warnings, and it didn't affect compilation (I think).

That leaves only 3 warnings:
[WARNING] Using platform encoding (ISO-8859-15 actually) to copy
filtered resources, i.e. build is platform dependent!
[WARNING] Cannot include project artifact: be.fedict.eid-
viewer:package:pom:4.0.0; it doesn't have an associated file or
directory.
[WARNING] Assembly file: /home/janh/insta/eid-viewer-4.0.0/eid-viewer-
package/target/package-4.0.0 is not a regular file (it may be a
directory). It cannot be attached to the project build for
installation or deployment.

The first seems pretty harmless (especially if you're not going to use
the binary package on other systems).
The second and the third seem related.

Can you confirm that commenting out the http://download.java.net/maven/1/
repository doesn't break things and that the "Cannot include artifact"
warning can be ignored safely?

Regards

Jan

[Jan Herrygers]

sorry for spamming your newsgroup, but I forgot to mention:

When running the eid-viewer, I cannot validate certificates. The
application tries to open a connection to trust.services.belgium.be,
but the server never answers to the TCP SYN packet. Connection to
193.191.245.59 or 193.191.245.58, port 80, no proxy in network, no
proxy configured in application, normal web browsing works.

Are these servers up? Or can they only be reached from trusted
networks?