required to build jabref 2.8+ (#385751)
Created attachment 320502 [details]
Created attachment 320504 [details]
Hi, thanks for the ebuild.
The pom for pcfi says "Multiple licenses, see META-INF/LICENSE.txt", also is this jar only used at build time? Btw, you can get it at https://github.com/jukka/pcfi as maven central tends to disable wget from time to time.
Also disable the minimum of tests so it passes for you, this way at least regressions can be detected.
Created attachment 326878 [details]
Created attachment 326880 [details, diff]
Created attachment 326882 [details, diff]
(In reply to comment #3)
Thanks for your comments. I've managed the test issue, but how to handle pcfi? Should it be formed-in as separate ebuild, as https://github.com/jukka/pcfi provides sources and not the jar file? The font's license leads to http://www.adobe.com/devnet/font.html#pcfi, which isn't very clean to me. The pdfbox actually embeds the adobe's fonts into the final jar-file...
Created attachment 333294 [details, diff]
Created attachment 333296 [details]
The last ebuild and patch use uncleanly-licensed pcfi dependendy as separate ebuild (#448532). I'm waiting the response from firstname.lastname@example.org howto manage the last.
pdfbox-1.8.1 was released. see http://mail-archives.apache.org/mod_mbox/www-announce/201304.mbox/%3C516643B8.email@example.com%3E
(In reply to Ivan Baidakou (dmol) from comment #10)
> The last ebuild and patch use uncleanly-licensed pcfi dependendy as separate
> ebuild (#448532). I'm waiting the response from firstname.lastname@example.org howto
> manage the last.
Any news from the licensing team?
*** Bug 504690 has been marked as a duplicate of this bug. ***
What's the status on the font licensing issue? Any resolution so we can move this issue forward?
any update here? would be greate to remove the old EAPI=1 ebuild in the tree.
+*pdfbox-1.8.8 (21 Feb 2015)
+ 21 Feb 2015; Patrice Clement <email@example.com>
+ +files/pdfbox-1.8.8-build.xml.patch, +pdfbox-1.8.8.ebuild:
+ Version bump. Fix bug #430054.
This package was a bit of a nightmare to version bump. Note: upstream messed up the package version in build.xml. I've put together a patch to correct it. Anyway, give it a try and let me know.