Package Details: pcgen-git 6.09.06.g5f55b50ddf-1

Git Clone URL: https://aur.archlinux.org/pcgen-git.git (read-only, click to copy)
Package Base: pcgen-git
Description: An RPG Character Generator.
Upstream URL: http://pcgen.org
Keywords: java pathfinder RPG
Licenses: LGPL2
Conflicts: pcgen
Provides: pcgen
Submitter: calebj
Maintainer: calebj
Last Packager: calebj
Votes: 7
Popularity: 0.000000
First Submitted: 2015-12-07 05:12
Last Updated: 2021-10-21 22:10

Dependencies (9)

Required by (0)

Sources (5)

Latest Comments

1 2 3 Next › Last »

calebj commented on 2021-10-21 22:12

@blargle upstream added a commented-out version in their gradle.properties, so the pkgver() was trying to include both lines in the version string. Fixed now.

blargle commented on 2021-10-21 21:50

now getting an error in pkver:

==> Starting pkgver()...

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.

==> ERROR: pkgver() generated an invalid version: 6.09.06_SNAPSHOT 6.09.06.g5f55b50ddf

-> error making: pcgen-git

redneckdrow commented on 2021-05-28 22:30

Fails to build with gradle 7.0.2. Something about fop 2.6. I installed it, but that doesn't help:

Could not find method compile() for arguments [org.apache.xmlgraphics:fop:2.6, build_1fdclno03b5ihyeslqjal7c73$_run_closure7$_closure61@19bc5093]
on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

The gradlew in the repository works fine.

i.e. change the line in the PKGBUILD:

gradle build

to

./gradlew build

This also has the weird side effect txtsd was talking about.

txtsd commented on 2021-04-14 16:10

==> Starting build()...
Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :
Project : => no module-info.java found
Downloading Java 14 x64 for windows from https://api.adoptopenjdk.net/v3/binary/latest/14/ga/windows/x64/jdk/hotspot/normal/adoptopenjdk
Download https://api.adoptopenjdk.net/v3/binary/latest/14/ga/windows/x64/jdk/hotspot/normal/adoptopenjdk
Unzip jre_x64.zip
Downloading Java 14 x32 for windows from https://api.adoptopenjdk.net/v3/binary/latest/14/ga/windows/x32/jdk/hotspot/normal/adoptopenjdk
Download https://api.adoptopenjdk.net/v3/binary/latest/14/ga/windows/x32/jdk/hotspot/normal/adoptopenjdk
Unzip jre_x32.zip
Downloading Java 14 x64 for mac from https://api.adoptopenjdk.net/v3/binary/latest/14/ga/mac/x64/jdk/hotspot/normal/adoptopenjdk
Download https://api.adoptopenjdk.net/v3/binary/latest/14/ga/mac/x64/jdk/hotspot/normal/adoptopenjdk
Unzip jre_x64.tar.gz
Downloading Java 14 x64 for linux from https://api.adoptopenjdk.net/v3/binary/latest/14/ga/linux/x64/jdk/hotspot/normal/adoptopenjdk
Download https://api.adoptopenjdk.net/v3/binary/latest/14/ga/linux/x64/jdk/hotspot/normal/adoptopenjdk
Unzip jre_x64.tar.gz
Downloading Javafx mods 14-0-1 x64 for windows from https://gluonhq.com/download/javafx-14-0-1-jmods-windows/
Download https://gluonhq.com/download/javafx-14-0-1-jmods-windows/

Why is it downloading java for windows and mac? And why does it download java 14 when we require java 11?

Magotchi commented on 2019-05-23 22:52

EDIT: The latest builds now work, as of 2019-06-05, but I don't know if it was fixed upstream or some other package I had updated to be compatible.

On two computers, when running this PKGBUILD for the latest revision (via the terminal to see its output), the GUI hangs at "Initializing UI" with 100% progress, and the terminal shows an exception, "java.lang.UnsupportedOperationException: The APP_ABOUT action is not supported on the current platform!".

Are others seeing this, and has anyone been able to get past it?

(In contrast, running "java -jar pcgen.jar" on the pre-built versions works fine, so that's been my workaround.)

Magotchi commented on 2019-04-30 14:32

Thanks for a great, working package. It do have a minor issue, though. Your pkgver() function doesn't generate sequential versions as new commits happen over at GitHub. It takes the version from gradle.properties and tacks on the Git short commit hash, resulting, with the current GitHub commit, in "6.09.00_DEV.g07d47fe53e". The problem there is that it's not sequential. For example, the package version from when you last updated it in the PKGBUILD is "6.09.00_DEV.g13a608a30e", which appears to be a newer version than that actual latest version of "6.09.00_DEV.g07d47fe53e", and that causes AUR helpers to get confused on whether the package needs to be updated.

Please review the wiki section on the pkgver() function for VCS packages. If this were my package, I would probably either use the "most recent un-annotated tag" option, which would result currently in "6.08.00RC3.r681.g07d47fe53e", or maybe use the "number of revisions since beginning of the history" option, combined with that version value you're already using with gradle.properties , which would result in something like "6.09.00_DEV.r25683.g07d47fe53e".

allan_m commented on 2019-02-04 01:28

Thanks so much -- worked perfectly!

calebj commented on 2019-02-04 00:40

Hey @allan_m,

I've updated the PKGBUILD for some upstream changes and to require Java 11 to be installed and enabled. Now it'll abort with an error if you haven't set your Java version to 11. The command you'll need to run is:

sudo archlinux-java set java-11-openjdk

Or replace openjdk with jdk if you're using Oracle's version from the AUR. See https://wiki.archlinux.org/index.php/Java#Switching_between_JVM for more info.

allan_m commented on 2019-02-03 23:41

Thanks so much for offering this build of PCGen -- I have used it on Ubuntu for years and was glad to find this on my migration to Arch.

I am getting the following on build attempts: "FAILURE: Build failed with an exception.

  • What went wrong: Execution failed for task ':compileJava'.

    Could not target platform: 'Java SE 11' using tool chain: 'JDK 8 (1.8)'"

I have changed JAVA_HOME to no effect. Searches and reading gradle info yielded possible solutions but nothing that worked, so I'm asking for help. If this is the wrong place for that, my apologies. Thanks very much.

TrefArc commented on 2018-12-14 09:55

@calebj Indeed, on the other computer all the correctly (access). Sorry.