Basically, you need to do the following.

1) Get the JEVIO source code.

2) Compile it into a jar.

3) Put that jar someplace where Maven can find it e.g. the current one being


So you’d want to make a similar directory and file for 4.4.4.

There are Maven commands for this kind of manual installation but it is easy enough to do it manually.

4) Then you would modify the jevio dependency in HPS Java in parent/pom.xml which is currently listed as 4.4.3.  Change this to 4.4.4 instead.

5) You would then recompile the HPS Java trunk, and the new jevio should be picked up.

Now you should be able to run HPS Java with the new dependency.

If you want to make changes to jevio like debug print outs then you need to do steps #2, #3 and #5 every time you make a change (e.g. compile, install and rebuild HPS Java).

Hope that’s clear.


On Feb 16, 2015, at 7:22 PM, Maurik Holtrop <[log in to unmask]> wrote:

Hello Jeremy,

I am trying to debug why jevio cannot open certain evio files. I noted that the C version of evio has not problems with these files. There are likely bugs in jevio that are causing this, or there is some different way to open a file. I would like to run the hps-java against the latest version of jevio 4.4.4.  I got this version from the CODA download page and compiled it with ant.

How do I now link the hps-java, specifically the org.hps.evio.EvioToLcio to this new version?

Clearly what I want to do is debug this, so I want to add print statements and the like to the evio code.


Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link: