Arch Linux User Repository

Thanks to Bevan, we now have a simple and elegant (compared to my attempt) workaround that lets the PKGBUILD download and use the most recent version of maven (currently 3.9.4). Should not need any intervention from you. :)

@bounty I've just reproduced the error message you reported by attempting to build with java-14-openjdk. With java-8-openjdk, the build was successful. It seems that my decision to replace the dependence on JRE8 with JRE ≥ 8 (see the pinned comment just below) was premature... sigh

@flortsch Can you confirm that the build fails with java-14?

@all For now, I'll leave the PKGBUILD as it is. Should you experience the same problem, please set an older version of Java (13 still seemed to work, 8 for sure does) as the default (using archlinux-java) and report here. Thank you.

@Cobra: deleting ~/.eclipse does not help

@bounty: does deleting ~/.eclipse help?

During installation I get the following Maven error:

[INFO] Resolving dependencies of MavenProject: name.abuchen.portfolio:name.abuchen.portfolio:0.46.3 @ /home/programs/portfolio/src/portfolio-0.46.3/name.abuchen.portfolio/pom.xml
[ERROR] Cannot resolve target definition:
[ERROR]   Software being installed: org.mockito 2.23.0.v20190527-1420
[ERROR]   Missing requirement: net.bytebuddy.byte-buddy 1.9.0.v20181107-1410 requires 'osgi.ee; (&(osgi.ee=JavaSE)(version=1.5))' but it could not be found
[ERROR]   Cannot satisfy dependency: org.mockito 2.23.0.v20190527-1420 depends on: java.package; net.bytebuddy [1.9.0,2.0.0)
[ERROR] 
[ERROR] Failed to resolve target definition /home/tbfk/Downloads/programs/portfolio/src/portfolio-0.46.3/portfolio-target-definition/portfolio-target-definition.target: See log for details -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
==> ERROR: A failure occurred in build().
    Aborting...

With version 0.46.3, I've replaced the dependency on JRE8 with JRE ≥ 8 as suggested by flortsch. Consequently, JAVA_HOME now points to /usr/lib/jvm/default-runtime. With the java default set to java-13-openjdk, portfolio builds successfully, and even significantly faster than before.

@flortsch Thanks for this valuable bit of information. The PKGBUILD contains three lines for exactly this situation since a very long time. I regularly tried to compile portfolio with more recent Java builds, but compilation always failed. I will try with Java 13, and if it works, I'll replace the hard with a soft dependency. :)

Is the hard dependency to Java 8 still required? I am using latest Java 13 to build and run portfolio and for me it is working without any issue. It would be nice if we could get rid of the fixed version dependency.

shellcheck detects an potential issue with the PKDBUILD file:

In /dev/stdin line 55:
    cp -r * ${pkgdir}${_DEST}
          ^-- SC2035: Use ./*glob* or -- *glob* so names with dashes won't become options.

@cobra

Didn't know a logfile existed. Issue was solved by deleting .eclipse folder, that contained old config.

@dbacc I assume that “also does” refers to the statement one line above, implying that the upstream version works fine. If this is the case, then the build must have failed in some point. Please clarify.

The Gtk warnings are nonessential, but nonetheless disquieting – I don't have them here.

Please also consult the portfolio log file and journalctl.