Re: [VOTE] Release XML Graphics FOP 2.0 (2nd attempt)

2015-05-26 Thread Andreas Delmelle
+1 from me, too.

... and, you are all very welcome. :)


Andreas

> On 26 May 2015, at 15:31, Glenn Adams  wrote:
> 
> +1. Thanks for all the work on FB fixes.
> 
> On Tue, May 26, 2015 at 2:33 AM, Simon Steiner 
> wrote:
> 
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> 
>> Hi,
>> 
>> This is a vote to release XML Graphics FOP 2.0. Findbugs is passing.
>> 
>> 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 2/6/2015
>> 
>> +1 from me.
>> 
>> Thanks
>> 
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1
>> 
>> iQIcBAEBAgAGBQJVZC+NAAoJEFuT8d98223qmbQQALDSXQIf+owqV/s/5eXfvSu3
>> EvzQtgu6RZEfL6TwZZX/iY3/7RtTF5OPz6b+i9QFpH2TN5fmLM7A720tK0IAjhB1
>> oU9RdKH4dakii7uRUOoolGVOAav0K0DDF1/3HSxf1Ys11CraRqKSGEnJH4WYI1Pv
>> xvGgQvFpRP2oQm12jTcfx9rolqijDykboEH+uCUF+MzNSoFMo/W93Id4CLpskr3O
>> /m+cNXz0YqUdwnsD/1HrzfauozLR/jDOWePj3OnOyw+CXzrtmtil7fytIHzg1YD3
>> B2t7+0InDVgEEqY94ojMXTGB9f/5iYfw/Gol4kg40o7H+9FXdO4YoduE5G7qEaKb
>> k9QGwaN4DG74vIlB4DtCdJONI9ikgj6xDA8LV/e6XmpFcKEFmsk6HVgoRU9NKKyI
>> jH+r4baa2tlR+cGJgeAr8SgjAQ3cf67ynRXBP74k9RPFATwCt5f+9GAVzV+Q/IDd
>> LODw0S+2oKmI1lXPS5pLqeoeo7ccBPlI8rzqTd+9L0RqBQ5K7YmUI2ZngqU86NjV
>> 1GC5R/caPd1kbnhS6alZAKDj5XAv26kHp/wtHPkKcsdBAcpQk+GjEC7UotD1s0VI
>> B0Xja4VBxpUyLIp1jcDTkPe0JgXM7CqjY+Y40CCJeJSek2F/HpRy4QKJcZJYUW0v
>> NM66eXRXoVEfVRrkwQqq
>> =Xhjn
>> -END PGP SIGNATURE-
>> 
>> 



Re: [VOTE] Release XML Graphics FOP 2.0 (2nd attempt)

2015-05-26 Thread Glenn Adams
+1. Thanks for all the work on FB fixes.

On Tue, May 26, 2015 at 2:33 AM, Simon Steiner 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> This is a vote to release XML Graphics FOP 2.0. Findbugs is passing.
>
> 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 2/6/2015
>
> +1 from me.
>
> Thanks
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJVZC+NAAoJEFuT8d98223qmbQQALDSXQIf+owqV/s/5eXfvSu3
> EvzQtgu6RZEfL6TwZZX/iY3/7RtTF5OPz6b+i9QFpH2TN5fmLM7A720tK0IAjhB1
> oU9RdKH4dakii7uRUOoolGVOAav0K0DDF1/3HSxf1Ys11CraRqKSGEnJH4WYI1Pv
> xvGgQvFpRP2oQm12jTcfx9rolqijDykboEH+uCUF+MzNSoFMo/W93Id4CLpskr3O
> /m+cNXz0YqUdwnsD/1HrzfauozLR/jDOWePj3OnOyw+CXzrtmtil7fytIHzg1YD3
> B2t7+0InDVgEEqY94ojMXTGB9f/5iYfw/Gol4kg40o7H+9FXdO4YoduE5G7qEaKb
> k9QGwaN4DG74vIlB4DtCdJONI9ikgj6xDA8LV/e6XmpFcKEFmsk6HVgoRU9NKKyI
> jH+r4baa2tlR+cGJgeAr8SgjAQ3cf67ynRXBP74k9RPFATwCt5f+9GAVzV+Q/IDd
> LODw0S+2oKmI1lXPS5pLqeoeo7ccBPlI8rzqTd+9L0RqBQ5K7YmUI2ZngqU86NjV
> 1GC5R/caPd1kbnhS6alZAKDj5XAv26kHp/wtHPkKcsdBAcpQk+GjEC7UotD1s0VI
> B0Xja4VBxpUyLIp1jcDTkPe0JgXM7CqjY+Y40CCJeJSek2F/HpRy4QKJcZJYUW0v
> NM66eXRXoVEfVRrkwQqq
> =Xhjn
> -END PGP SIGNATURE-
>
>


Re: [VOTE] Release XML Graphics FOP 2.0 (2nd attempt)

2015-05-26 Thread Clay Leeds
+1

Cheers!

Clay

--

"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet

> On May 26, 2015, at 1:33 AM, Simon Steiner  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> This is a vote to release XML Graphics FOP 2.0. Findbugs is passing.
> 
> 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 2/6/2015
> 
> +1 from me.
> 
> Thanks
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQIcBAEBAgAGBQJVZC+NAAoJEFuT8d98223qmbQQALDSXQIf+owqV/s/5eXfvSu3
> EvzQtgu6RZEfL6TwZZX/iY3/7RtTF5OPz6b+i9QFpH2TN5fmLM7A720tK0IAjhB1
> oU9RdKH4dakii7uRUOoolGVOAav0K0DDF1/3HSxf1Ys11CraRqKSGEnJH4WYI1Pv
> xvGgQvFpRP2oQm12jTcfx9rolqijDykboEH+uCUF+MzNSoFMo/W93Id4CLpskr3O
> /m+cNXz0YqUdwnsD/1HrzfauozLR/jDOWePj3OnOyw+CXzrtmtil7fytIHzg1YD3
> B2t7+0InDVgEEqY94ojMXTGB9f/5iYfw/Gol4kg40o7H+9FXdO4YoduE5G7qEaKb
> k9QGwaN4DG74vIlB4DtCdJONI9ikgj6xDA8LV/e6XmpFcKEFmsk6HVgoRU9NKKyI
> jH+r4baa2tlR+cGJgeAr8SgjAQ3cf67ynRXBP74k9RPFATwCt5f+9GAVzV+Q/IDd
> LODw0S+2oKmI1lXPS5pLqeoeo7ccBPlI8rzqTd+9L0RqBQ5K7YmUI2ZngqU86NjV
> 1GC5R/caPd1kbnhS6alZAKDj5XAv26kHp/wtHPkKcsdBAcpQk+GjEC7UotD1s0VI
> B0Xja4VBxpUyLIp1jcDTkPe0JgXM7CqjY+Y40CCJeJSek2F/HpRy4QKJcZJYUW0v
> NM66eXRXoVEfVRrkwQqq
> =Xhjn
> -END PGP SIGNATURE-
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 


Re: [VOTE] Release XML Graphics FOP 2.0 (2nd attempt)

2015-05-26 Thread Chris Bowditch

+1

On 26/05/2015 09:33, Simon Steiner wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

This is a vote to release XML Graphics FOP 2.0. Findbugs is passing.

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 2/6/2015

+1 from me.

Thanks

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJVZC+NAAoJEFuT8d98223qmbQQALDSXQIf+owqV/s/5eXfvSu3
EvzQtgu6RZEfL6TwZZX/iY3/7RtTF5OPz6b+i9QFpH2TN5fmLM7A720tK0IAjhB1
oU9RdKH4dakii7uRUOoolGVOAav0K0DDF1/3HSxf1Ys11CraRqKSGEnJH4WYI1Pv
xvGgQvFpRP2oQm12jTcfx9rolqijDykboEH+uCUF+MzNSoFMo/W93Id4CLpskr3O
/m+cNXz0YqUdwnsD/1HrzfauozLR/jDOWePj3OnOyw+CXzrtmtil7fytIHzg1YD3
B2t7+0InDVgEEqY94ojMXTGB9f/5iYfw/Gol4kg40o7H+9FXdO4YoduE5G7qEaKb
k9QGwaN4DG74vIlB4DtCdJONI9ikgj6xDA8LV/e6XmpFcKEFmsk6HVgoRU9NKKyI
jH+r4baa2tlR+cGJgeAr8SgjAQ3cf67ynRXBP74k9RPFATwCt5f+9GAVzV+Q/IDd
LODw0S+2oKmI1lXPS5pLqeoeo7ccBPlI8rzqTd+9L0RqBQ5K7YmUI2ZngqU86NjV
1GC5R/caPd1kbnhS6alZAKDj5XAv26kHp/wtHPkKcsdBAcpQk+GjEC7UotD1s0VI
B0Xja4VBxpUyLIp1jcDTkPe0JgXM7CqjY+Y40CCJeJSek2F/HpRy4QKJcZJYUW0v
NM66eXRXoVEfVRrkwQqq
=Xhjn
-END PGP SIGNATURE-


-
To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: general-h...@xmlgraphics.apache.org







[VOTE] Release XML Graphics FOP 2.0 (2nd attempt)

2015-05-26 Thread Simon Steiner
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

This is a vote to release XML Graphics FOP 2.0. Findbugs is passing.

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 2/6/2015

+1 from me.

Thanks

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJVZC+NAAoJEFuT8d98223qmbQQALDSXQIf+owqV/s/5eXfvSu3
EvzQtgu6RZEfL6TwZZX/iY3/7RtTF5OPz6b+i9QFpH2TN5fmLM7A720tK0IAjhB1
oU9RdKH4dakii7uRUOoolGVOAav0K0DDF1/3HSxf1Ys11CraRqKSGEnJH4WYI1Pv
xvGgQvFpRP2oQm12jTcfx9rolqijDykboEH+uCUF+MzNSoFMo/W93Id4CLpskr3O
/m+cNXz0YqUdwnsD/1HrzfauozLR/jDOWePj3OnOyw+CXzrtmtil7fytIHzg1YD3
B2t7+0InDVgEEqY94ojMXTGB9f/5iYfw/Gol4kg40o7H+9FXdO4YoduE5G7qEaKb
k9QGwaN4DG74vIlB4DtCdJONI9ikgj6xDA8LV/e6XmpFcKEFmsk6HVgoRU9NKKyI
jH+r4baa2tlR+cGJgeAr8SgjAQ3cf67ynRXBP74k9RPFATwCt5f+9GAVzV+Q/IDd
LODw0S+2oKmI1lXPS5pLqeoeo7ccBPlI8rzqTd+9L0RqBQ5K7YmUI2ZngqU86NjV
1GC5R/caPd1kbnhS6alZAKDj5XAv26kHp/wtHPkKcsdBAcpQk+GjEC7UotD1s0VI
B0Xja4VBxpUyLIp1jcDTkPe0JgXM7CqjY+Y40CCJeJSek2F/HpRy4QKJcZJYUW0v
NM66eXRXoVEfVRrkwQqq
=Xhjn
-END PGP SIGNATURE-



Re: Fix FB warnings (was: Re: [VOTE] Release XML Graphics FOP 2.0)

2015-05-24 Thread Andreas Delmelle

> On 23 May 2015, at 23:15, Andreas Delmelle  
> wrote:

> FYI  - High and medium priority warnings addressed in r1681384, and absent an 
> answer to my question, assumed the lazy approach there, for now.
> 
> Will try to have a look at the low priority ones tomorrow.

... and low priority warnings now addressed in r1681435.

Going through those, the number of implicit assertions made at various places 
in the codebase is quite amazing.

In some cases, making those explicit looks a bit silly, but it actually makes 
perfect sense.

Example from the o.a.f.render.afp package:

---
/** {@inheritDoc} */
@Override
protected AFPDataObjectInfo createDataObjectInfo() {
return new AFPGraphicsObjectInfo();
}

/** {@inheritDoc} */
public void handleImage(RenderingContext context, Image image, Rectangle pos)
throws IOException {
AFPRenderingContext afpContext = (AFPRenderingContext)context;

AFPDataObjectInfo info = createDataObjectInfo();
assert (info instanceof AFPGraphicsObjectInfo);
AFPGraphicsObjectInfo graphicsObjectInfo = (AFPGraphicsObjectInfo) info;
---

For us, humans, it looks evident that casting the object returned by 
createDataObjectInfo() to an AFPGraphicsObjectInfo is legitimate. 
However, strictly speaking, one cannot exclude the possibility that someone 
creates a subclass and  overrides createDataObjectInfo(), but not 
handleImage(), in which case the code would fail at runtime with an ugly 
ClassCastException...

Perhaps it is also possible and cleaner to force the return type to an 
AFPGraphicsObjectInfo, which is a subclass of AFPDataObjectInfo. I may look 
into that later. At least now, the assertion is clearly visible in the code.



KR

Andreas



Fix FB warnings (was: Re: [VOTE] Release XML Graphics FOP 2.0)

2015-05-23 Thread Andreas Delmelle
> On 22 May 2015, at 22:36, Andreas Delmelle  
> wrote:


> Is the convention then to insert the commented annotation once for every 
> field or does it suffice to add one per class?
> 
> I am fine with both. Just thought I'd ask before committing to trunk.

FYI  - High and medium priority warnings addressed in r1681384, and absent an 
answer to my question, assumed the lazy approach there, for now.

Will try to have a look at the low priority ones tomorrow.



KR

Andreas


Re: [VOTE] Release XML Graphics FOP 2.0

2015-05-22 Thread Andreas Delmelle
> On 22 May 2015, at 17:04, Andreas Delmelle  
> wrote:
> 
> Hi Simon
> 
>> On 22 May 2015, at 12:59, Simon Steiner  wrote:
>> 
>> We have an old branch with findbugs passing I was going to port this to
>> trunk.


I realise now Simon's remark may have been referring to XGC, not to FOP (?) 
Or do we really have an old FOP branch there which passed all those 124 
warnings... Would seem strange, since a lot of those must have been in there 
for quite some time already. That would be a *very* old branch, then. :-)

At any rate, in the meantime, I have already done 45 (high and medium 
priority), of which a handful are code fixes.

The ones related to default encoding, as already suggested, would be added to 
the unapproved exclusion list.

The remaining ones would become approved exclusions.

About the latter set, one question:
Suppose I add following to the approved exclusions

  


  
  

  
  


  

and this concerns basically ALL fields of said classes.

Is the convention then to insert the commented annotation once for every field 
or does it suffice to add one per class?

I am fine with both. Just thought I'd ask before committing to trunk.



KR

Andreas

Re: [VOTE] Release XML Graphics FOP 2.0

2015-05-22 Thread Andreas Delmelle
> On 21 May 2015, at 22:20, Andreas Delmelle  
> wrote:
> 
> 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.

Some follow-up:
In the meantime, I had a look at each of those 17, and the suggestion here 
would be a temporary blanket exclusion of the pattern for now.
Note - This should be replaced with an explicit set of approved exclusions, so 
that future warnings in new code would not go unnoticed due to the exclusion of 
the entire bug pattern.

Only one occurrence seemed suspicious, and would be easy to resolve, but not 
really an issue - 
Strictly speaking, RtfHandler.startDocument should be using explicit US-ASCII 
encoding for the stream. No priority to fix, since the RTF library already 
contains code that automatically escapes any character outside of the US-ASCII 
range.

The remainder can be divided in following groups:

1) The actual source encoding seems out of FOP's control (?) - 5 warnings
This is the case for the warnings in the o.a.f.fonts package and the one 
o.a.f.render.ps package. 
The binary data here comes from FontBox classes. 
Not sure how to resolve those. I have to defer to the experts here. Should we 
assume that constructing Strings from the byte arrays using default encoding is 
always going to work here?

3) Default encoding is used as a fallback/last resort - 3 warnings
The developer in question added this in a catch-block for an 
UnsupportedEncodingException, so the choice is either to terminate or try the 
default, which should always work... 
Strictly speaking, if an explicit encoding is expected, I would say that the 
safer bet is to terminate, rather than silently revert to the default, but I am 
not going to insist. 

2) Reads from/writes to the console (System.in/System.out) - 3 warnings
Using the default encoding is OK in this case.

4) Private methods where byte-to-string and string-to-byte conversions are 
guaranteed to always happen on the same platform - 1 warning
No problem to use default encoding here.

5) Classes used by the build or from the command line - 4 warnings
Should be cleaned up over time, but no priority now.



KR

Andreas





Re: [VOTE] Release XML Graphics FOP 2.0

2015-05-22 Thread Andreas Delmelle
Hi Simon

> On 22 May 2015, at 12:59, Simon Steiner  wrote:
> 
> We have an old branch with findbugs passing I was going to port this to
> trunk.

OK, sure. That works for me too.

> 
> Findbugs 3 requires java 7 so we shouldn’t move to that yet.
> 

Oh, I realize we cannot move to that, due to the 1.6 requirement for FOP. 

What I was saying is: *if* you have 1.7+ installed and you would request the 
IDE plugin, you would get that version --and see even more than those 124 
warnings you got, which may sound discouraging to people who are rabidly 
against using it... :/

I did not mean to bring you down or anything like that. If that was the case, 
then my apologies.


Big Thanks again for taking care of the release process. It seemed long overdue.


KR

Andreas

Re: [VOTE] Release XML Graphics FOP 2.0

2015-05-22 Thread Glenn Adams
On Fri, May 22, 2015 at 4:59 AM, Simon Steiner 
wrote:

> Hi,
>
> We have an old branch with findbugs passing I was going to port this to
> trunk.
>

I noticed you committed an update to fix many XGC warnings. Thanks for
addressing my comment.

I also notice you have introduced x.clone() in many cases. You should be
careful in doing this not to introduce a performance hit in hot code paths.
I expect you did this to fix various *_EXPOSE_REP* warnings. I often
exclude those warnings rather than introduce clone() usage due to potential
performance problems. It requires some amount of subjective judgment to
decide whether to exclude or use clone. In the present case, it may have
been better to simply exclude these warnings, e.g., by using the following
in the exclude file:


  


  


Make sure that all unit and integration tests are still running after these
changes, which one hopes does not introduce any regressions.


>
> Thanks
>
> -Original Message-
> From: Andreas Delmelle [mailto:andreas.delme...@telenet.be]
> Sent: 21 May 2015 19:48
> To: fop-dev@xmlgraphics.apache.org
> Subject: Re: [VOTE] Release XML Graphics FOP 2.0
>
> Hi guys
>
> > On 21 May 2015, at 20:00, Glenn Adams  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
>
>


RE: [VOTE] Release XML Graphics FOP 2.0

2015-05-22 Thread Simon Steiner
Hi,

We have an old branch with findbugs passing I was going to port this to
trunk.

Thanks

-Original Message-
From: Andreas Delmelle [mailto:andreas.delme...@telenet.be] 
Sent: 21 May 2015 19:48
To: fop-dev@xmlgraphics.apache.org
Subject: Re: [VOTE] Release XML Graphics FOP 2.0

Hi guys

> On 21 May 2015, at 20:00, Glenn Adams  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



Re: [VOTE] Release XML Graphics FOP 2.0

2015-05-21 Thread Andreas Delmelle
> On 21 May 2015, at 20:47, Andreas Delmelle  
> wrote:
> 
> 
> @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

2015-05-21 Thread Andreas Delmelle

> On 21 May 2015, at 20:47, Andreas Delmelle  
> wrote:
> 
> 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

2015-05-21 Thread Andreas Delmelle
Hi guys

> On 21 May 2015, at 20:00, Glenn Adams  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

Re: [VOTE] Release XML Graphics FOP 2.0

2015-05-21 Thread Glenn Adams
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 
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  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  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

2015-05-21 Thread Clay Leeds
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  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 
> 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  wrote:
>> 
>> +1
>> 
>> 
>> 
>> On Thu, May 21, 2015 at 7:21 AM, 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

2015-05-21 Thread Glenn Adams
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 
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  wrote:
>
> +1
>
>
>
> On Thu, May 21, 2015 at 7:21 AM, 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

2015-05-21 Thread Simon Steiner
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 mailto:gl...@skynav.com> > wrote:

+1

 

On Thu, May 21, 2015 at 7:21 AM, Simon Steiner 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

2015-05-21 Thread Glenn Adams
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  wrote:

> +1
>
> On Thu, May 21, 2015 at 7:21 AM, 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

2015-05-21 Thread Andreas Delmelle
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  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
> 



RE: [VOTE] Release XML Graphics FOP 2.0

2015-05-21 Thread Robert Meyer
+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

2015-05-21 Thread Chris Bowditch

+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

2015-05-21 Thread Glenn Adams
+1

On Thu, May 21, 2015 at 7:21 AM, 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-
>
>


[VOTE] Release XML Graphics FOP 2.0

2015-05-21 Thread Simon Steiner
-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-