Package Details: portfolio 0.83.2-2

Git Clone URL: https://aur.archlinux.org/portfolio.git (read-only, click to copy)
Package Base: portfolio
Description: Track your portfolio performance (finance)
Upstream URL: https://github.com/portfolio-performance/portfolio
Licenses: EPL-1.0
Submitter: Cobra
Maintainer: Cobra (Bevan)
Last Packager: Cobra
Votes: 43
Popularity: 0.47
First Submitted: 2015-11-08 10:45 (UTC)
Last Updated: 2026-04-22 09:43 (UTC)

Dependencies (4)

Required by (0)

Sources (3)

Pinned Comments

Cobra commented on 2025-12-19 15:13 (UTC)

80.4-2 adds OAuth authorization and thus the possibility to create a portfolio account for obtaining historic data.

Bevan implemented this crucial feature in the current PKGBUILD – and I'm very happy to welcome him as co-maintainer. :)

Cobra commented on 2023-08-19 13:34 (UTC)

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. :)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 14 Next › Last »

Cobra commented on 2023-11-10 13:33 (UTC) (edited on 2023-11-10 13:48 (UTC) by Cobra)

It insists for a good reason: portfolio is developed with Java 17 (an LTS version supported, AFAIK, until 2027), and it may or may not compile or run with any more recent version. We had several issues with that in the past until I decided to pin the version of Java to exactly the one used for its development.

But that's not really any problem: you can have several Java version installed in parallel, and switch between them using archlinux-java-run, which is installed together with portfolio. My default is currently 17, and I haven't tested if the current version of portfolio runs with 21.

jamesbond007 commented on 2023-11-06 16:55 (UTC)

Hi Cobra, could you make portfolio work with the current java version? (jdk-openjdk 21.u35-7)

Currently portfolio insists on the old java version 17.

Expatbrat commented on 2023-08-19 17:52 (UTC)

It works for me, many thanks to all those who worked on it.

Cobra commented on 2023-08-19 13:34 (UTC)

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. :)

Cobra commented on 2023-08-19 13:29 (UTC)

MUCH better. :D Simpler and yet much more clean.

Thanks a bunch, Bevan. :)

Bevan commented on 2023-08-19 11:15 (UTC)

Thanks! You may simplify that solution by letting makepkg download and extract Maven. That way, it would also not clutter the user's home directory. I made a patch to show what I mean: https://pastebin.com/S0TMEgf2

Cobra commented on 2023-08-19 10:31 (UTC)

@Bevan: thanks a lot for the suggestion; as you see I've followed it. I don't like it one bit, but couldn't think of any better way other than providing the maven binaries as separate AUR package, for which I don't have the time right now. Let's hope it's just a short-term workaround.

Bevan commented on 2023-08-15 11:05 (UTC)

As a workaround, one can download the Maven "Binary tar.gz archive" from https://maven.apache.org/download.cgi, extract it somewhere and add the following line to the PKGBUILD, directly below the export JAVA_HOME=... line in build():

export PATH=/path/to/your/extracted/apache-maven-3.9.4/bin:$PATH

Maybe it would even make sense to temporarily let the PKGBUILD download and use a recent Maven itself.

Cobra commented on 2023-08-14 15:30 (UTC)

I'm sorry to announce that even the new version 0.65.0 does not compile successfully:

The plugin org.eclipse.tycho:tycho-packaging-plugin:4.0.1 requires Maven 
version 3.9.0.

We are currently at 3.8.7, so I guess we play the waiting game once again.

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 14 Next › Last »