Activity for Samael
-
Samael posted a comment on ticket #16
I've put this on my backlog but I'll need the latest edition of the ISO spec https://github.com/SingingBush/barcode4j/issues/91
-
This has been done on my fork https://github.com/SingingBush/barcode4j also with other improvements. Releases are available in maven central: https://search.maven.org/artifact/com.singingbush/barcode4j
-
I've done some testing of this on my fork: https://github.com/singingBush/barcode4j The EAN128LogicImpl.java will add brackets itself by default unless you use <barcode:omit-brackets>true</barcode:omit-brackets> so perhaps what's needed here is: <fo:instream-foreign-object> <barcode:barcode xmlns:barcode="http://barcode4j.krysalis.org/ns" message="{$message}" orientation="0"> <barcode:ean-128> <barcode:height>18mm</barcode:height> <barcode:module-width>0.43mm</barcode:module-width> <barcode:human-readable>...
-
great thanks. Will the 2.0 tag be published to maven central?
-
fix test in trunk and update pom
-
just wanted to clarify, with this patch Java 1.8 is still supported. It should be built with a later JDK such as Java 11 but the bulk of the source will compile to Java 1.8 byte code, only the module-info.java file will be compiled with the newer JDK. It is a multi-release jar.
-
update to properly support Java modules
-
Attaching an updated build.sh script that will also compile test sources and run unit tests
-
Sorry for the delay in looking into this. I ended up using standard Java instead of relying on Jericho. However I did checkout the source code and take a look. First off I was surprised to find it's using bazaar, if you do intend to migrate to git it should be as simple as initialising a git repo in the same directory and running brz fast-export -b main | git fast-import assuming the branch is called main. See https://jugmac00.github.io/blog/migrate-a-repository-from-bazaar-to-git/ for details. As...
-
It's possible to have multi release jars but it's not trivial. You'd need to compile the existing source with JDK 7 and use JDK 9 or above to compile the module-info.java and bundle it into the same jar. See here for some info about multi-release jars: https://nipafx.dev/multi-release-jars-multiple-java-versions/ I don't really get the desire to support JDK 7 these days, or anything below Java 11 tbh, but if it's needed perhaps it's worth continuing a 3.* branch for JDK 7/8 support and starting a...
-
It's possible to have multi release jars but it's not trivial. You'd need to compile the existing source with JDK 7 and use JDK 9 or above to compile the module-info.java and bundle it into the same jar. See here for some info about multi-release jars: https://nipafx.dev/multi-release-jars-multiple-java-versions/ I don't really get the desire to support JDK 7 these days, or anything below Java 11 tbh, but if it's needed perhaps it's worth continuing a 3. branch for JDK 7/8 support and starting a...
-
I exported the code along with commit history to https://github.com/SingingBush/jour as it'll be a lot easier to setup a CI process.
-
update junit
-
thanks Vlad, I've pushed those changes as r153. Is there an automated build process that will allow tags to be published to maven central? In the long term, it may be easier to maintain this project if it get's moved to github. The integrated build pipelines and publishing of artifacts makes things a lot easier.
-
updated to work with Java 1.8
-
I've attached a patch that updates a bunch of dependencies and maven plugins and gets the codebase working with some newer JDK versions (I used JDK 1.8 locally, updating for current versions of Java will require further changes due to JPMS). If there's no intention of supporting the project moving forward then please consider giving me write access as I'd be interested in continuing with this and getting it working with the more recent versions of Java. Perhaps making a new major version that supports...
-
will there be another release?
-
please support java modules in the next release
-
Is there chance of this still happening? Occasionally there's a need to work on legacy...
-
osx crash on closing window
1