build: make jni depend on jna to avoid mvn dependency resolution fails

[ghost]

Basics

These points need to be fulfilled for every PR:

• Short descriptions of your changes are in the release notes
  (added as entry in doc/news/_preparation_next_release.md which
  contains _(my name)_)
  Please always add something to the release notes.
• Details of what you changed are in commit messages
  (first line should have module: short statement syntax)
• References to issues, e.g. close #X, are in the commit messages.
• The buildservers are happy.
• The PR is rebased with current master.

If you have any troubles fulfilling these criteria, please write
about the trouble as comment in the PR. We will help you.
But we cannot accept PRs that do not fulfill the basics.

Checklist

Check relevant points but please do not remove entries.
For docu fixes, spell checking, and similar none of these points below
need to be checked.

• I added unit tests for my code
• I fully described what my PR does in the documentation
  (not in the PR description)
• I fixed all affected documentation
• I added code comments, logging, and assertions as appropriate (see Coding Guidelines)
• I updated all meta data (e.g. README.md of plugins and METADATA.ini)
• I mentioned every code not directly written by me in THIRD-PARTY-LICENSES

Review

Reviewers will usually check the following:

• Documentation is introductory, concise, good to read and describes everything what the PR does
• Examples are well chosen and understandable
• Code is conforming to our Coding Guidelines
• APIs are conforming to our Design Guidelines
• Code is consistent to our Design Decisions

Labels

If you are already Elektra developer:

• Add the "work in progress" label if you do not want the PR to be reviewed yet.
• Add the "ready to merge" label if the basics are fulfilled and you also
  say that everything is ready to be merged.

[ghost]

@sanssecours do you think that this is the correct approach to avoid jna and jni be built in parallel?

Or should I add its own dependency such as

add_dependencies (jni jna)

You are very proficient in cmake as far as I can tell :)

[sanssecours]

@sanssecours do you think that this is the correct approach to avoid jna and jni be built in parallel?

Adding an additional dependency seems to be the correct approach. However, I think we need to add the dependency earlier. For me it would make sense to require a compiled JNA binding, before we call Maven in the CMake code of the JNI plugin. I think adding jna to the argument DEPENDS here:

libelektra/src/plugins/jni/CMakeLists.txt

Line 74 in 8d138a2

DEPENDS "${LIBELEKTRA4J_PATH}/pom.xml")

should accomplish that.

[markus2330]

If it solves the problem, it looks good to me.

[ghost]

jenkins build libelektra please

[markus2330]

Please do not restart too many build jobs at once. It seems like this was too much for the server, see #160.

[ghost]

jenkins build libelektra please

[ghost]

jenkins build libelektra please

[markus2330]

Thank you! Hopefully this fixed #2855.