[jira] [Created] (FOP-2472) Allow to clear the hyphenation tree cache at runtime
Marc Wiest created FOP-2472:
---
Summary: Allow to clear the hyphenation tree cache at runtime
Key: FOP-2472
URL: https://issues.apache.org/jira/browse/FOP-2472
Project: Fop
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Marc Wiest
Priority: Minor
I suggest adding the following method (or similar) to the
org.apache.fop.hyphenation.Hyphenator class.
I had to hack FOP and create a custom build for myself, because I need to alter
and reload the hyphenation files at runtime.
The use case is, that I have a web application that allows editors - on an
admin page - to add hyphenation exceptions on-the-fly. In that case the
hyphenation pattern files are re-created including the new exceptions, but need
to be reloaded by FOP. The below worked for me, please consider adding to the
trunk.
/**
* Clear the hyphenation tree cache, in case the underlying data files have
changed at runtime.
*/
public static synchronized void clearHyphenationTreeCache() {
hTreeCache = new HyphenationTreeCache(); }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FOP-2472) Allow to clear the hyphenation tree cache at runtime
[
https://issues.apache.org/jira/browse/FOP-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Wiest updated FOP-2472:
Description:
I suggest adding the following method (or similar) to the
org.apache.fop.hyphenation.Hyphenator class.
I had to hack FOP and create a custom build for myself, because I need to alter
and reload the hyphenation files at runtime.
The use case is, that I have a web application that allows editors - on an
admin page - to add hyphenation exceptions on-the-fly. In that case the
hyphenation pattern files are re-created including the new exceptions, but need
to be reloaded by FOP. The below worked for me, please consider adding to the
trunk.
{code:title=Hyphenator.java|borderStyle=solid}
/**
* Clear the hyphenation tree cache, in case the underlying data files have
changed at runtime.
*/
public static synchronized void clearHyphenationTreeCache()
{
hTreeCache = new HyphenationTreeCache();
}
{code}
was:
I suggest adding the following method (or similar) to the
org.apache.fop.hyphenation.Hyphenator class.
I had to hack FOP and create a custom build for myself, because I need to alter
and reload the hyphenation files at runtime.
The use case is, that I have a web application that allows editors - on an
admin page - to add hyphenation exceptions on-the-fly. In that case the
hyphenation pattern files are re-created including the new exceptions, but need
to be reloaded by FOP. The below worked for me, please consider adding to the
trunk.
/**
* Clear the hyphenation tree cache, in case the underlying data files have
changed at runtime.
*/
public static synchronized void clearHyphenationTreeCache() {
hTreeCache = new HyphenationTreeCache(); }
Allow to clear the hyphenation tree cache at runtime
Key: FOP-2472
URL: https://issues.apache.org/jira/browse/FOP-2472
Project: Fop
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Marc Wiest
Priority: Minor
Labels: cache, hyphenation
Original Estimate: 0.5h
Remaining Estimate: 0.5h
I suggest adding the following method (or similar) to the
org.apache.fop.hyphenation.Hyphenator class.
I had to hack FOP and create a custom build for myself, because I need to
alter and reload the hyphenation files at runtime.
The use case is, that I have a web application that allows editors - on an
admin page - to add hyphenation exceptions on-the-fly. In that case the
hyphenation pattern files are re-created including the new exceptions, but
need to be reloaded by FOP. The below worked for me, please consider adding
to the trunk.
{code:title=Hyphenator.java|borderStyle=solid}
/**
* Clear the hyphenation tree cache, in case the underlying data files have
changed at runtime.
*/
public static synchronized void clearHyphenationTreeCache()
{
hTreeCache = new HyphenationTreeCache();
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release XML Graphics FOP 2.0
On 21 May 2015, at 20:47, Andreas Delmelle andreas.delme...@telenet.be wrote: snip / If everyone had committed to using it in the past, there would not be 143 warnings to address right before the release... Correction: 124 warnings... Mixing up 167 - 124 = 43. :)
RE: [VOTE] Release XML Graphics FOP 2.0
Hi, Did we agree that these need to be fixed (we never passed a vote to fail build on findbugs): XGC has no findbugs target in ant. XGC has 6 compiler warnings. FOP has 124 findbugs warnings: https://builds.apache.org/view/XMLGraphics/job/xmlgraphics-fop/ws/build/report_findbugs.html Thanks From: Glenn Adams [mailto:gl...@skynav.com] Sent: 21 May 2015 18:06 To: FOP Developers; XML Graphics Project Subject: Re: [VOTE] Release XML Graphics FOP 2.0 Before you create the final artifact, please ensure there are no compiler, checkstyle, or findbugs warnings. Same applies for XGC 2.0.1. On Thu, May 21, 2015 at 7:39 AM, Glenn Adams gl...@skynav.com mailto:gl...@skynav.com wrote: +1 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com mailto:simonsteiner1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
I too would prefer no findbugs* warnings going into a Release, and if it's 'easy' for someone to resolve that issue, then by all means, that's great! However, I'm not prepared to VETO this RELEASE due to this issue. IIRC, this issue has been brought up before, but was never resolved and I don't think now is the time to resolve, unless it's relatively painless. Clay My +1 remains... * [OT] heh... AutoCorrect tried to change that to 'windbags'! ;-) On May 21, 2015, at 11:00 AM, Glenn Adams gl...@skynav.com wrote: I would prefer no findbugs warnings going into the release. I'm finding more and more commercial uses of code have policies that require no findbugs warnings. You can simply add entries to the findbugs-exclude.xml file to disable the warnings for the release. On Thu, May 21, 2015 at 11:42 AM, Simon Steiner simonsteiner1...@gmail.com wrote: Hi, Did we agree that these need to be fixed (we never passed a vote to fail build on findbugs): XGC has no findbugs target in ant. XGC has 6 compiler warnings. FOP has 124 findbugs warnings: https://builds.apache.org/view/XMLGraphics/job/xmlgraphics-fop/ws/build/report_findbugs.html Thanks *From:* Glenn Adams [mailto:gl...@skynav.com] *Sent:* 21 May 2015 18:06 *To:* FOP Developers; XML Graphics Project *Subject:* Re: [VOTE] Release XML Graphics FOP 2.0 Before you create the final artifact, please ensure there are no compiler, checkstyle, or findbugs warnings. Same applies for XGC 2.0.1. On Thu, May 21, 2015 at 7:39 AM, Glenn Adams gl...@skynav.com wrote: +1 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
I'm not asking for a policy decision at this time. Rather, I'm asking that Simon ensure there are no warnings for the common warning sources we are accustomed to using, which for many users, includes: javac, checkstyle, findbugs. Some folks also use PMD, but i'm not asking for it here. On Thu, May 21, 2015 at 12:08 PM, Clay Leeds the.webmaes...@gmail.com wrote: I too would prefer no findbugs* warnings going into a Release, and if it's 'easy' for someone to resolve that issue, then by all means, that's great! However, I'm not prepared to VETO this RELEASE due to this issue. IIRC, this issue has been brought up before, but was never resolved and I don't think now is the time to resolve, unless it's relatively painless. Clay My +1 remains... * [OT] heh... AutoCorrect tried to change that to 'windbags'! ;-) On May 21, 2015, at 11:00 AM, Glenn Adams gl...@skynav.com wrote: I would prefer no findbugs warnings going into the release. I'm finding more and more commercial uses of code have policies that require no findbugs warnings. You can simply add entries to the findbugs-exclude.xml file to disable the warnings for the release. On Thu, May 21, 2015 at 11:42 AM, Simon Steiner simonsteiner1...@gmail.com wrote: Hi, Did we agree that these need to be fixed (we never passed a vote to fail build on findbugs): XGC has no findbugs target in ant. XGC has 6 compiler warnings. FOP has 124 findbugs warnings: https://builds.apache.org/view/XMLGraphics/job/xmlgraphics-fop/ws/build/report_findbugs.html Thanks *From:* Glenn Adams [mailto:gl...@skynav.com] *Sent:* 21 May 2015 18:06 *To:* FOP Developers; XML Graphics Project *Subject:* Re: [VOTE] Release XML Graphics FOP 2.0 Before you create the final artifact, please ensure there are no compiler, checkstyle, or findbugs warnings. Same applies for XGC 2.0.1. On Thu, May 21, 2015 at 7:39 AM, Glenn Adams gl...@skynav.com wrote: +1 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
Hi guys On 21 May 2015, at 20:00, Glenn Adams gl...@skynav.com wrote: I would prefer no findbugs warnings going into the release. I'm finding more and more commercial uses of code have policies that require no findbugs warnings. You can simply add entries to the findbugs-exclude.xml file to disable the warnings for the release. I agree with this preference. Adding entries to the exclusion file is OK, but at least, the assessment should be made whether they can/should be fixed right away. BTW - Not sure why some people are still reluctant to use it... It is really only a tiny effort to install that plugin in your IDE of choice. Granted, you will likely get a newer version than 2.0.3, which produces even more warnings --3.0.1 produces 167 on unmodified FOP trunk. If everyone had committed to using it in the past, there would not be 143 warnings to address right before the release... @Simon - To relieve you of some of the burden, I am definitely willing to assist with combing through those. How do I proceed? Do I commit related changes directly to trunk, so that you can merge them into the branch later? KR Andreas
[VOTE] Release XML Graphics FOP 2.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
On 21 May 2015, at 20:47, Andreas Delmelle andreas.delme...@telenet.be wrote: snip / @Simon - To relieve you of some of the burden, I am definitely willing to assist with combing through those. How do I proceed? Do I commit related changes directly to trunk, so that you can merge them into the branch later? FWIW - Those 17 'high' priority Reliance on default encoding warnings are definitely worth checking out. So far, I think the handful that I already looked at can be safely added to the exclusions list, but this is *exactly* the type of bug that can lead to issues at runtime that are a real pain to track down, if they do arise. KR Andreas
RE: [VOTE] Release XML Graphics FOP 2.0
+1 Date: Thu, 21 May 2015 15:23:22 +0100 From: bowditch_ch...@hotmail.com To: gene...@xmlgraphics.apache.org CC: fop-dev@xmlgraphics.apache.org Subject: Re: [VOTE] Release XML Graphics FOP 2.0 +1. Thanks Simon On 21/05/2015 14:21, Simon Steiner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
+1. Thanks Simon On 21/05/2015 14:21, Simon Steiner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
+1 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
I would prefer no findbugs warnings going into the release. I'm finding more and more commercial uses of code have policies that require no findbugs warnings. You can simply add entries to the findbugs-exclude.xml file to disable the warnings for the release. On Thu, May 21, 2015 at 11:42 AM, Simon Steiner simonsteiner1...@gmail.com wrote: Hi, Did we agree that these need to be fixed (we never passed a vote to fail build on findbugs): XGC has no findbugs target in ant. XGC has 6 compiler warnings. FOP has 124 findbugs warnings: https://builds.apache.org/view/XMLGraphics/job/xmlgraphics-fop/ws/build/report_findbugs.html Thanks *From:* Glenn Adams [mailto:gl...@skynav.com] *Sent:* 21 May 2015 18:06 *To:* FOP Developers; XML Graphics Project *Subject:* Re: [VOTE] Release XML Graphics FOP 2.0 Before you create the final artifact, please ensure there are no compiler, checkstyle, or findbugs warnings. Same applies for XGC 2.0.1. On Thu, May 21, 2015 at 7:39 AM, Glenn Adams gl...@skynav.com wrote: +1 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
Re: [VOTE] Release XML Graphics FOP 2.0
I forget whether this type of vote is for all committers or only the PMC, but saw Robert vote as well, so just to be sure +1 from me as well. Thanks, Simon! KR Andreas On 21 May 2015, at 15:21, Simon Steiner simonsteiner1...@gmail.com wrote: Signed PGP part Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks - To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: general-h...@xmlgraphics.apache.org
[jira] [Commented] (FOP-2472) Allow to clear the hyphenation tree cache at runtime
[
https://issues.apache.org/jira/browse/FOP-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554560#comment-14554560
]
Andreas L. Delmelle commented on FOP-2472:
--
Seems fine to me. Unless anyone has strong objections, I will commit this
change to trunk shortly.
Allow to clear the hyphenation tree cache at runtime
Key: FOP-2472
URL: https://issues.apache.org/jira/browse/FOP-2472
Project: FOP
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Marc Wiest
Priority: Minor
Labels: cache, hyphenation
Original Estimate: 0.5h
Remaining Estimate: 0.5h
I suggest adding the following method (or similar) to the
org.apache.fop.hyphenation.Hyphenator class.
I had to hack FOP and create a custom build for myself, because I need to
alter and reload the hyphenation files at runtime.
The use case is, that I have a web application that allows editors - on an
admin page - to add hyphenation exceptions on-the-fly. In that case the
hyphenation pattern files are re-created including the new exceptions, but
need to be reloaded by FOP. The below worked for me, please consider adding
to the trunk.
{code:title=Hyphenator.java|borderStyle=solid}
/**
* Clear the hyphenation tree cache, in case the underlying data files have
changed at runtime.
*/
public static synchronized void clearHyphenationTreeCache()
{
hTreeCache = new HyphenationTreeCache();
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Release XML Graphics FOP 2.0
Before you create the final artifact, please ensure there are no compiler, checkstyle, or findbugs warnings. Same applies for XGC 2.0.1. On Thu, May 21, 2015 at 7:39 AM, Glenn Adams gl...@skynav.com wrote: +1 On Thu, May 21, 2015 at 7:21 AM, Simon Steiner simonsteiner1...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, This is a vote to release XML Graphics FOP 2.0. Artifacts can be found there: https://people.apache.org/~ssteiner/fop-2.0 The release is signed with the key: https://people.apache.org/~ssteiner/KEYS The vote will end on 28/5/2015 +1 from me. Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVXduFAAoJEFuT8d98223qUtYP/3NaJGfuElP3RyKQFW71J7Fz M/RXeiHQrsxrEg0MW9HXnzGLDnqlmUiFHIs3EHU1vVBy2kBVD0OO42Eh68FqcwWS maqzGQHGKtyKhxS52X3mb/nSv8N/php1PlvqJbbNYl4KqMhT9GhOhilhtIXKD+Z5 KMIkDFkFPcN++H65CSMn3ynmR3XzUZffzrGwpjIBIj7gP2zW6ZJ5qM/E05k/90rd QsRT/UYBN3bGolZp3oOHLnB/H6KwGsHOfVmrxaFwhLGJnqpaBgYe2+dQ6I50Twx9 tlJhtv0/7nAq/Py/vPQj2kTDC7XV0pQhTFbhnhlJ4smk21G9XRV12nKlQtRmiLqp Yrmn8HPqSia6UZ2zl5ObDMVLjc+vnsUzkqa8ONkSmUW23XziF3anojaf4Hb8ENNg 8k8KpVQU1z1uOrPYxQDK9ajJPmlUocOpfVTBWyzyL39bhmJmx479TSViYGy2j29v 9JXN3r36tKfxxepT2u0npLPdqPi1MrOhUdMdFNuxZdIG9W2KgYDNqvaK4dTmYBT+ kghoQzM8Ega8bKPe+mMmoYsAEPo9iftnellcLKk7dBp6SRBVOdPLa8K+OKF1UAqW OrOS4ahlkRk3k0cl/SdSBfnEQcclVD6WenNZA2T09RELx8riWnVuRjmu+GSLhgzx Vs3s8aMGH8xBEN0SEv+l =t6hJ -END PGP SIGNATURE-
