Re: Contributing the JBig2 ImageIO Plugin to PDFBox

2017-08-24 Thread Andreas Lehmkühler
I'll check the docs after the weekend when I'm back.
I don't see any issue with the different signers.

Andreas

Am 24. August 2017 13:53:10 MESZ schrieb "Jörg Henne" :
>Am 23.08.2017 um 21:35 schrieb Andreas Lehmkuehler:
>
>> The CCLA is on file
>The software-grant and another ICLA have been sent.
>Some clarification about the software-grant might be necessary, though.
>
>The software-grant and the CCLA are signed by different legal entities 
>(levigo holding/levigo solutions). This is due to the fact that 
>contributors are employed by levigo solutions whereas the IP to be 
>transferred belongs to the parent holding.
>
>Jörg
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
>For additional commands, e-mail: dev-h...@pdfbox.apache.org


Re: Contributing the JBig2 ImageIO Plugin to PDFBox

2017-08-24 Thread Andreas Lehmkühler

> Jörg Henne  hat am 24. August 2017 um 10:08 geschrieben:
> 
> 
> 
> Am 23.08.2017 um 18:40 schrieb Andreas Lehmkuehler:
> > readded dev@pdfbox
> >
> > Am 22.08.2017 um 19:14 schrieb Jörg Henne:
> >> Am 19.08.2017 um 17:07 schrieb Andreas Lehmkuehler:
> >>
> >>> The following files don't have a license header:
> >>>
> >> Good catch. Tracked as https://github.com/levigo/jbig2-imageio/issues/46
> >>
> >>> What about the binary test files in src/test/resources/? I assume 
> >>> their license is cleared as well, isn't it?
> >>>
> >> That's what I assumed as well, but upon re-checking, things no longer 
> >> seem to be so clear. I'm tracking this question as 
> >> https://github.com/levigo/jbig2-imageio/issues/48
> >> Maybe you guys can help me with this problem or let me know how you 
> >> deal with it.
> > Is there any jbig2-viewer available?
> In theory, yes, for example XnView supports JBIG2 via jbig2dec.exe. In 
> reality, support for the various cases covered in the test suite is 
> rather spotty: many of the images cannot be decoded with XnView. So, 
> strange as it might seem, I don't know of any reliable stand-alone JBIG2 
> viewer.
> 
> However, obviously those images can be decoded using the plugin. I've 
> attached PNG versions of them to a comment on the above issue: 
> https://github.com/levigo/jbig2-imageio/issues/48#issuecomment-324556311
Cool, I've already thought about converting them myself, but you were faster. 
Thanks. I'll have a look after the weekend as my time will be limited the next 
few days.

> > Are these testfiles somehow special, do they trigger some special 
> > processing within the plugin or are they just a bunch of jbig2 files 
> > and could be replaced by others
> JBIG2 isn't quite as simple as, say, PNG. There are several entropy 
> coding options (Arithmetic/MQ, Huffman) several different segment types 
> and several ways to maintain, refine and reference shape dictionaries. 
> Therefore there a large number of code paths need to be covered in the 
> tests. Since it is rather hard to generate all those possible 
> combinations (no single encoder library will use all of them) the 
> refrerence library provides (provided?) a convenient way of achieving 
> decent test coverage.
OK, so we should try to keep as much as possible of those data.

> >> The files seem to fall into three categories:
> >> 1. Files from the original test suite. While the copyright status of 
> >> the file isn't problematic, the status of the content seems to be 
> >> muddy in some cases.
> >>- Files containing representations of public U.S. government 
> >> documents should be in the public domain: 
> >> https://en.wikipedia.org/wiki/Copyright_status_of_work_by_the_U.S._government
> >>- The same applies to representations of U.S. patents: 
> >> https://en.wikipedia.org/wiki/Copyright_on_the_content_of_patents_and_in_the_context_of_patent_prosecution
> >>  
> >>
> >>- 004.jb2 and 005.jb2 seem problematic but may be covered by some 
> >> exemption.
> >>- amb.bmp no idea
> > amb.bmp seems problematic as it looks like a promo photo of Ally 
> > McBeal aka Callista Flockhart.
> You seem to be more up to speed regarding TV characters. I certainly 
> didn't recognise the person in the photo :-)
Maybe I'm old enough to know that TV-show from the late 90's

> Losing this image would be bad, though, since it is the only halftone 
> region sample bitstream in there.
Maybe, we should think about a README which expains the origin of some/all of 
the test files

> >> 2. Files provided to us with the permission to use them for testing 
> >> purposes
> >>201231100*.jb2 is the only case, seems to be a public U.S. 
> >> document anyway and therefore in the public domain. I have not 
> >> contacted the original provider of the files for the simple reason 
> >> that his or her e-mail address has been lost when the Googlecode site 
> >> went into archived state. >
> >> 3. Files with content so trivial that copyright should not be an 
> >> issue, i.e. fragments of bitstreams, isolated segments, trivial test 
> >> images
> > This isn't a question of copyright but of license and/or privacy.
> The files in this category are sampledata_page(1,2,3).jb2. The content 
> is obviously not a matter of privacy. Regarding the license I am 
> currently asking around whether anyone still knows where this came from 
> (unfortunately we lost some very early RCS history from before we 
> open-sourced the component).
> 
> Jörg

Andreas

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



Re: Contributing the JBig2 ImageIO Plugin to PDFBox

2017-08-22 Thread Andreas Lehmkühler

> Jörg Henne  hat am 22. August 2017 um 13:20 geschrieben:
> 
> 
> Am 19.08.2017 um 19:59 schrieb Tilman Hausherr:
> > Am 19.08.2017 um 18:09 schrieb Andreas Lehmkuehler:
> >>>
> >> +1, there is one superfluous "pdfbox". Besides some other minor 
> >> things to be adjusted we have to discuss how the plugin shall be 
> >> integrated.
> >>
> >> IMHO, we should keep it independent, so that we could cut independent 
> >> releases of the plugin and pdfbox. Doing so, we have to reorg our svn 
> >> repository. We have to create a pdfbox directory in trunk and move 
> >> everything to that directory. There will be another directoy jbig2 
> >> for the sources of the plugin. 
> >
> > Is there a need to have independent releases? Maybe for existing 
> > levigo clients with support contracts?
> Honoring those should not be a problem one way or the other. We can 
> always cut our own releases under dedicated version numbers, as we 
> provide dedicated Maven repositories to our customers.
Just to avoid missunderstandings, once the code is under the PDFBox umbrella 
only the PDFBox PMC can cut releases. There can't be any outside the project 
(with the same maven coords and the same package name). That's the reason why 
I'd like to keep it independent so that we can cut a release whenever is't s 
necessary.

> Jörg

Andreas

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



Re: PDFBox and PDF 2.0

2017-08-14 Thread Andreas Lehmkühler

> Maruan Sahyoun  hat am 11. August 2017 um 18:36 
> geschrieben:
> 
> 
> 
> > Am 11.08.2017 um 18:24 schrieb Tilman Hausherr :
> > 
> > Am 11.08.2017 um 10:07 schrieb Maruan Sahyoun:
> >> Hi,
> >> 
> >> with PDF 2.0 being available it might be time to start to introduce some 
> >> of the features in PDFBox (no rush I think as it will need some time to be 
> >> adopted). One feature I would like to discuss if it would be good to 
> >> introduce a version support so one could say to save as PDF 2.0 file or 
> >> some other version. E.g. one could now use utf-8 encoded text strings 
> >> which will introduce issues in readers not supporting that where some of 
> >> the other changes like new properties will simply be ignored.
> > 
We need to support such 2.0 features as there will be some people who will use 
PDFBox to render such pdfs. And if we add that utf-8 support for reading it 
shouldn't be that hard to add it for writing as well.
I like Maruans idea to add some version support. So that adding some features 
to a pdf could change the version automatically or could trigger an exception.

Andreas

> > We can indicate the version when saving, and we know the version when 
> > loading... Maybe what you mean is to propagate the version to the COS 
> > classes?
> 
> Yes - as there are some areas in PDF 2.0 - such as utf-8 encoded text strings 
> - which we would need to enable e.g. when generating a document from scratch 
> or adding new annotations. Currently if we pass text as an input to some of 
> our setters when writing out the file it will not use utf-8 text strings 
> which is fine as it will ensure that older readers are able to read the 
> content. But if you'd like to 'enforce' 2.0 there is currently now way in 
> doing so.
> 
> For other areas where there is a new 'PDF Object' or property with 2.0 we can 
> wait until there is demand for it and let the developer decide if that shall 
> be used (the same way we handle it today as there is no specific version 
> support in PDFBox i.e. one could declare the file as being 1.4. compliant but 
> use 1.7 features wthout any complaints). The low level lib we are I think 
> that's acceptable.
> 
> Maruan
> 
> > 
> > Tilman
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: OWASP dependency-check

2017-07-11 Thread Andreas Lehmkühler
> Tilman Hausherr  hat am 8. Juli 2017 um 15:40 
> geschrieben:
> 
> 
> https://github.com/jeremylong/dependency-check-gradle#current-release
> 
> Tim Allison pointed us to this on twitter... Should we use it (maybe 
> just in "pedantic" mode, because it needs 400MB in the repository)?
> 
> Or just recommend our users to use it?
> 
> Or should just tika use it?
> 
> It tells whether any components we're using have security risks. This 
> xml segment is to be put into the pom.xml:
> 
>  
>  org.owasp
> dependency-check-maven
>  2.0.0
>  
> true
>  
>  
>  
>  
>  check
>  
>  
>  
>  
> 
> I tried it with a project that linked pdfbox 2.0.0 (has XXE 
> vulnerability) and yes, the build stopped.
Let's add this, but just in "pedantic" mode

Andreas

> Tilman
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: Contributing the JBig2 ImageIO Plugin to PDFBox

2017-06-27 Thread Andreas Lehmkühler
Hi Jörg,

> Jörg Henne  hat am 26. Juni 2017 um 15:36 geschrieben:
> 
> 
> Hi all,
> 
> 
> Apache PDFBox currently uses the JBig2 ImageIO-Plugin at 
> https://github.com/levigo/jbig2-imageio as an optional component and 
> recommends the use of it at https://pdfbox.apache.org/2.0/dependencies.html. 
> I am writing this as a representative of the ISV levigo, the owner and 
> publisher of this component. Besides being an open source component we use 
> the component on our own software suite. Over the years we have invested 
> significant time into it and have been maintaining it for many years so that 
> I would consider its code-base reasonably mature and stable. However, we 
> continue to address any bugs reported to us and have accepted several 
> community-provided fixes.
> 
> 
> The plugin in question is currently licensed under the GNU General Public 
> License V3 with other licensing options available, including commercial 
> licensing. Having PDFBox under the ASL and the plugin under a different 
> license has long been a nuisance for PDFBox users which has deterred many 
> users fron using it. On the other hand, many users have a strong need for it 
> as our plugin is (IMHO) still the highest quality pure-Java open source 
> decoder available.
> 
> We would like to change this situation by licensing the plugin under the ASL. 
> At the same time, however, we think that it would make sense to move the code 
> base over to a new home that makes it independent of a single vendor. That's 
> where the ASF and the PDFBox project comes into play :-)
> 
This is good news and higly appreciated!

> We are currently in the very early stages of evaluating such a transition. A 
> few random thoughts:
> 
> - All of those thoughts are subject to the PDFBox community​ being willing to 
> do this and accepting the contribution, obviously.
> 
I can think about 2 possible new homes within the ASF, Apache PDFBox and Apache 
Commons. The first option might be the easier way if it comes to the 
"paperwork".

> - One of the reasons for us to favor the ASF as a new home is that the ASF 
> has strong provisions in place to ensure that a project can thrive without it 
> being dependent on life-support by a single vendor.
> 
+1

> - We need to do proper IP vetting: while the vast majority has been done by 
> levigo there is one other GitHub committer who has provided bug fixes and 
> whom we need to talk to.
> 
Good catch, these are the important bits which have to be resolved first. After 
that you have to provide a Software Grant Agreement, see [1] for details, so 
that we can start the IP clearance process, see [2] and [3]

> - Package names and maven coordinates will have to be updated to reflect the 
> transition
+1

> - After a transition colleagues of mine would continue to contribute to the 
> maintenance of the component. The necessary committer rights would need to be 
> bestowed upon them. I myself have been an Apache committed for many years, 
> albeit almost completely inactive.
> 
As an apache committer you might know that nobody can request committer rights 
but has to be voted in. But that is maybe just a formality. About how many devs 
are we talking here?

> - It would make sense (and is required by the Apache rules) to have 
> additional know-how about the component outside of levigo. I don't know 
> whether there is enough interest in the PDFBox community to ensure this.
> 
Yes, diversity is an important aspect. I'm pretty sure that the code will 
attract other (pdfbox) developers once it is under the apache umbrella. The 
imaging [4] devs might be interested in the code as well.

> So that's it for now, I guess. Please let me know what you think.
I support your plan to integrate the plugin with pdfbox. We, the PDFbox PMC, 
have to discuss that topic first and have to perform a vote, but I guess this 
is just a formality.

Feel free to ask if there are any further questions.

> Jörg Henne
> 

Andreas

[1] http://www.apache.org/licenses/
[2] http://incubator.apache.org/ip-clearance/pdfbox-padaf.html
[3] https://issues.apache.org/jira/browse/PDFBOX-1056
[4] http://commons.apache.org/proper/commons-imaging/

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



RE: 2.0.6 release ?

2017-05-10 Thread Andreas Lehmkühler

> "Allison, Timothy B."  hat am 10. Mai 2017 um 11:42 
> geschrieben:
> 
> 
> Haven't had a chance to look. Reports are here:
> http://162.242.228.174/reports/reports_pdfbox_2_0_6_20170510.tar.gz
Thanks again for running the report again

I had a quick look and there are 2 new exceptions. It seems to be a regression. 
I'm going to dig deeper later when I'm back home

Here a 2 sample pfs, one for each exception
commoncrawl2/YV/YVFDWHF767TEYTT7IVFSLUIJTDF3YP57
commoncrawl2/5W/5WULWDW54DAQ4ORVJSACEE2KCXQ7PQLL

Andreas

> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



2.0.6 release ?

2017-05-02 Thread Andreas Lehmkühler
Hi,

I'm planning to cut a 2.0.6 release in about 1 or 2 weeks from now, any 
objections?

Andreas

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



Re: Problems updating the website

2017-03-17 Thread Andreas Lehmkühler

> Maruan Sahyoun <sahy...@fileaffairs.de> hat am 17. März 2017 um 12:13 
> geschrieben:
> 
> 
> Hi,
> 
> > Am 17.03.2017 um 12:09 schrieb Maruan Sahyoun <sahy...@fileaffairs.de>:
> > 
> > Hi,
> > 
> >> Am 17.03.2017 um 11:24 schrieb Andreas Lehmkühler <andr...@lehmi.de>:
> >> 
> >> 
> >>> Maruan Sahyoun <sahy...@fileaffairs.de> hat am 17. März 2017 um 11:06 
> >>> geschrieben:
> >>> 
> >>> 
> >>> Hi,
> >>> 
> >>>> Am 17.03.2017 um 07:59 schrieb Andreas Lehmkuehler <andr...@lehmi.de>:
> >>>> 
> >>>> Hi,
> >>>> 
> >>>> I've updated the download section due to the new release. After running 
> >>>> the mvn command to publish the content I saw some unwanted changes. I 
> >>>> can't tell where they came from, e.g. [1]
> >>>> 
> >>> 
> >>> what in particular is unwanted? The complete page, parts of it?
> >> Have a look at the end of that page, the formatting for the formatting 
> >> style example is gone.
> >> 
> > 
> > works fine on my local copy. Even after pulling the latest changes. I'm at 
> > jekyll 3.1.2. I'll do a minor change and push to see if that corrects the 
> > issue.
> 
> that fixed it
Thanks for the fix. I've to investigate on my side to see what went wrong.
> 
> BR
> Maruan
> 
> > 
> > BR
> > Maruan
> > 
> > 
> >>> 
> >>>> @Maruan Any idea what went wrong/I did wrong?
> >>>> 
> >>>> I'm using jekyll 3.0.1 on linux fedora.
> >>>> 
> >>>> BR
> >>>> Andreas
> >>>> 
> >>>> [1] https://pdfbox.apache.org/codingconventions.html
> >>>> 
> >>>> -
> >>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>> 
> >>> 
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>> 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >> 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: Problems updating the website

2017-03-17 Thread Andreas Lehmkühler

> Maruan Sahyoun  hat am 17. März 2017 um 11:06 
> geschrieben:
> 
> 
> Hi,
> 
> > Am 17.03.2017 um 07:59 schrieb Andreas Lehmkuehler :
> > 
> > Hi,
> > 
> > I've updated the download section due to the new release. After running the 
> > mvn command to publish the content I saw some unwanted changes. I can't 
> > tell where they came from, e.g. [1]
> > 
> 
> what in particular is unwanted? The complete page, parts of it?
Have a look at the end of that page, the formatting for the formatting style 
example is gone.

> 
> > @Maruan Any idea what went wrong/I did wrong?
> > 
> > I'm using jekyll 3.0.1 on linux fedora.
> > 
> > BR
> > Andreas
> > 
> > [1] https://pdfbox.apache.org/codingconventions.html
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



2.0.5 release

2017-03-03 Thread Andreas Lehmkühler
Hi,

I'm planning to cut a 2.0.5 release in about 1 or 2 weeks from now, any 
objections?

BR
Andreas

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



Re: JIRA thread replies

2017-01-24 Thread Andreas Lehmkühler
I've opened a JIRA-ticket 

https://issues.apache.org/jira/browse/INFRA-13380

BR
Andreas

> Andreas Lehmkühler <andr...@lehmi.de> hat am 18. Januar 2017 um 12:40 
> geschrieben:
> 
> 
> I've forwared your question to users@infra
> 
> BR
> Andreas
> > Tilman Hausherr <thaush...@t-online.de> hat am 17. Januar 2017 um 18:29 
> > geschrieben:
> > 
> > 
> > Did I miss something or is it a setting? I do no longer see the 
> > possibility to do thread replies in JIRA, only ordinary replies.
> > 
> > Tilman
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: JIRA thread replies

2017-01-18 Thread Andreas Lehmkühler
I've forwared your question to users@infra

BR
Andreas
> Tilman Hausherr  hat am 17. Januar 2017 um 18:29 
> geschrieben:
> 
> 
> Did I miss something or is it a setting? I do no longer see the 
> possibility to do thread replies in JIRA, only ordinary replies.
> 
> Tilman
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: [JENKINS] - More build NODES ; Less build LABELS

2016-11-14 Thread Andreas Lehmkühler

> Maruan Sahyoun  hat am 12. November 2016 um 16:09 
> geschrieben:
> 
> 
> Hi,
> 
> > Am 12.11.2016 um 15:01 schrieb Andreas Lehmkuehler :
> > 
> > Hi,
> > 
> > infra consolidated jenkins nodes and labels. The most interesting part is 
> > the comment of the reserved nodes H19 Sounds like we should be able to 
> > create a job to build our website using jenkins.
> > 
> 
> we are already using asf-site to publish the content to but it's a little 
> unclear to me how the actual build will be done as we are currently using 
> jekyll to do that. So how would we go from the current template + unprocessed 
> content to the actual HTML?

Maybe it is possible to create a job which publishes changes based on a git 
checkin trigger, so that we can automate that part of the publishing as well.

But let's wait for the announced post about that topic.

BR
Andreas
> 
> BR
> Maruan
> 
> > BR
> > Andreas
> > 
> > 
> >  Weitergeleitete Nachricht 
> > Betreff: [JENKINS] - More build NODES ; Less build LABELS
> > Datum: Sat, 12 Nov 2016 11:41:36 +1100
> > Von: Gavin McDonald 
> > Antwort an: bui...@apache.org
> > An: bui...@apache.org
> > 
> > HI All,
> > 
> > As some of you may have noticed, we have been working behind the scenes in 
> > Infra making some improvements to the overall stability and health of 
> > Jenkins.
> > 
> > New Nodes
> > =
> > 
> > Recently, we have added another 9 nodes  H12 - H20 of which H12 to H18 are 
> > general purpose nodes for everyone.
> > 
> > Previously we added jenkins-us1, jenkins-eu2 and jenkins-eu3 again general 
> > purpose.
> > ubuntu-3 (Hemera) has been taken offline.
> > 
> > New Windows Nodes - we have 2 new windows 2012 nodes, which directly 
> > replaced windows1 and windows2.
> > Labels Removed
> > =
> > 
> > As promised some time ago, quite a few labels that were deemed no longer 
> > required, have been removed.
> > 
> > Labels removed: yahoo-not-h2, docker, HDFS, MapReduce, Pig, Falcon, Tez and 
> > ZooKeeper.
> > 
> > The current list of mapped Nodes to Labels can be found on our wiki page 
> > here:-
> > 
> > https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels 
> > 
> > In general, if you are a Hadoop related project, you would use as a 
> > priority the ‘Hadoop’ label for  H0-H9 - thats 10 nodes.
> > If not a Hadoop related project, use the ‘ubuntu’ label  which currently 
> > consists of 17 nodes.
> > You may mix n match - if appropriate use Hadoop||ubuntu for a choice of 27 
> > nodes.
> > 
> > For Windows, please just use the generic ‘Windows’ label - as we add more 
> > Windows nodes they will get this label.
> > 
> > Reserved Nodes
> > =
> > 
> > There are specific nodes that have priority for projects - such as the 
> > Beam* nodes, the Cassandra* nodes etc. These are all listed in the above 
> > wiki page. These are not included in the generic ‘ubuntu’ labels.
> > 
> > In addition, H nodes H19 and H20 are reserved - they are for all projects 
> > to use, however they are restricted to those projects that want to use 
> > Jenkins + Git + Gitpubsub in order to publish their main www website(s). 
> > I’ll do a new post up specifically on this topic soon, but we are looking 
> > for one or two projects as testers so please email if interested in knowing 
> > more.
> > 
> > Summary
> > ===
> > 
> > We have more nodes and less labels. yay!
> > 
> > Even more nodes are coming soon also so do stay tuned.
> > 
> > When I removed labels I also changed job configurations to replace any 
> > matching labels with alternative remaining labels.
> > Some projects have already reverted to previous configurations and are 
> > failing to build as a result. Please check your jobs ASAP and change them 
> > in necessary,
> > 
> > Thanks All, any questions or comments, direct to the builds@ list please.
> > 
> > Gav… (ASF Infra.)
> > 
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



[ANNOUNCE] Apache PDFBox 2.0.2 released

2016-06-09 Thread Andreas Lehmkühler

The Apache PDFBox community is pleased to announce the release of
Apache PDFBox version 2.0.2. The release is available for download at:

http://pdfbox.apache.org/download.cgi

See the full release notes below for details about this release.

Release Notes -- Apache PDFBox -- Version 2.0.2

Introduction


The Apache PDFBox library is an open source Java tool for working with PDF 
documents.


This is an incremental bugfix release based on the earlier 2.0.1 release. It 
contains

a couple of fixes and small improvements.

For more details on these changes and all the other fixes and improvements
included in this release, please refer to the following issues on the
PDFBox issue tracker at https://issues.apache.org/jira/browse/PDFBOX.

Bug

[PDFBOX-3267] - Using threads results in different images
[PDFBOX-3326] - Issue in RenderingMode.isStroke method
[PDFBOX-3327] - IndexOutOfBoundsException when retrieving kerning information
[PDFBOX-3332] - Apache PDFBox Form Fill TrueType text spacing issue
[PDFBOX-] - Wrong appearance generation for rotated AcroForms fields
[PDFBOX-3336] - several errors in the incremental save
[PDFBOX-3338] - CCITT Fax decoder fails
[PDFBOX-3341] - currentAccessPermission.setReadOnly() not set in 
StandardSecurityHandler

[PDFBOX-3346] - Create example with empty signature
[PDFBOX-3347] - COSName parsing doesn't handle ISO-8859-1 encoded bytes
[PDFBOX-3348] - NPE in Type1Parser.parseBinary
[PDFBOX-3351] - NPE when drawing annotation with empty border color array
[PDFBOX-3354] - PDCIDFont.getAverageFontWidth always returns 0
[PDFBOX-3355] - PDPageLabels.getLabelsByPageIndices() returns Uppercase letters 
for style a

[PDFBOX-3360] - java.lang.IllegalArgumentException: dash lengths all zero
[PDFBOX-3362] - PageLayout.TwoColumnRight was Illegal
[PDFBOX-3363] - Leftover file in temp directory when signing
[PDFBOX-3368] - ContainsKey don't work for the Map returned by 
PDStructureTreeRoot.getRoleMap

[PDFBOX-3369] - Error expected floating point number actual='0.00-35095424'

Improvement

[PDFBOX-3089] - Investigate why glyph path caching does not always cache glyph 
accesses

[PDFBOX-3316] - Add comment to PDF
[PDFBOX-3329] - Create PDFMergerUtility example with improved metadata handling
[PDFBOX-3342] - Add example to jump to a local page to AddAnnotations
[PDFBOX-3352] - Calendar values are parsed with unknown timezones
[PDFBOX-3364] - PDModel.getSignatureFields() only returns top level signature 
fields


Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/pdfbox/KEYS.

About Apache PDFBox
---

Apache PDFBox is an open source Java library for working with PDF documents.
This project allows creation of new PDF documents, manipulation of existing
documents and the ability to extract content from documents. Apache PDFBox
also includes several command line utilities. Apache PDFBox is published
under the Apache License, Version 2.0.

For more information, visit http://pdfbox.apache.org/

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.

For more information, visit http://www.apache.org/


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



Re: PDFBox JavaDoc and Subprojects

2016-06-07 Thread Andreas Lehmkühler
> Maruan Sahyoun  hat am 29. Mai 2016 um 18:35
> geschrieben:
> 
> 
> Hi,
> 
> in order to publish the API docs for pdfbox and it's subproject I see two
> options
> 
> a) one combined JavaDoc for PDFBox and all subproject
> b) single JavaDoc for PDFBox and for each of it's subprojects
> 
> a) is easier to generate
> b) would allow us to handle them individually as part of per subproject
> microsite
> 
> Thoughts?
I'd prefer a), keep it simple as long as the second option isn't needed.

BR
Andreas
> 
> BR
> Maruan
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: [CVE-2016-2175] Apache PDFBox XML External Entity vulnerability

2016-06-07 Thread Andreas Lehmkühler
Hi,

> Maruan Sahyoun  hat am 6. Juni 2016 um 12:40
> geschrieben:
> 
> 
> Hi,
> 
> > Am 06.06.2016 um 11:41 schrieb Simon Steiner :
> > 
> > Hi,
> > 
> > Should this be on the pdfbox homepage.
> 
> I'll let Andreas decide on that
What should we add, just a news posting or adding a new security section as
other projects like Tomcat?

BR
Andreas
> > The homepage has http://pdfbox.apache.org/download.cgi but its not
> > clickable.
> 
> done - thanks for letting us know.
> 
> Maruan
> 
> > 
> > Thanks
> > 
> > -Original Message-
> > From: Andreas Lehmkuehler [mailto:le...@apache.org] 
> > Sent: 27 May 2016 07:03
> > To: annou...@apache.org; dev@pdfbox.apache.org; us...@pdfbox.apache.org;
> > secur...@apache.org; oss-secur...@lists.openwall.com;
> > bugt...@securityfocus.com
> > Subject: [CVE-2016-2175] Apache PDFBox XML External Entity vulnerability
> > 
> > CVE-2016-2175: Apache PDFBox XML External Entity vulnerability
> > 
> > Severity: Important
> > 
> > 
> > Vendor:
> > The Apache Software Foundation
> > 
> > Versions Affected:
> > Apache PDFBox 1.8.0 to 1.8.11
> > Apache PDFBox 2.0.0
> > Earlier, unsupported Apache PDFBox versions may be affected as well
> > 
> > Description:
> > Apache PDFBox parses different XML data within PDF files such as XMP and the
> > initialization of the XML parsers did not protect against XML External
> > Entity
> > (XXE) vulnerabilities. According to www.owasp.org [1]: "This attack may lead
> > to the disclosure of confidential data, denial of service, server side
> > request forgery, port scanning from the perspective of the machine where the
> > parser is located, and other system impacts."
> > 
> > 
> > Mitigation:
> > Upgrade to Apache PDFBox 1.8.12 respectively 2.0.1
> > 
> > Credit:
> > This issue was discovered by Arthur Khashaev (https://khashaev.ru), Seulgi
> > Kim, Mesut Timur and Microsoft Vulnerability Research.
> > 
> > [1] https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional
> > commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



New mail archives interface

2016-05-19 Thread Andreas Lehmkühler
Hi,

at the recent ApacheCon NA conference, the new mail archives interface was
unveiled.

See https://lists.apache.org/


BR
Andreas

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



[ANNOUNCE] Apache PDFBox 2.0.1 released

2016-04-26 Thread Andreas Lehmkühler
The Apache PDFBox community is pleased to announce the release of
Apache PDFBox version 2.0.1. The release is available for download at:

http://pdfbox.apache.org/download.cgi

See the full release notes below for details about this release.

Release Notes -- Apache PDFBox -- Version 2.0.1

Introduction


The Apache PDFBox library is an open source Java tool for working with PDF
documents.

This is an incremental bugfix release based on the earlier 2.0.0 release. It
contains
a couple of fixes and small improvements.

For more details on these changes and all the other fixes and improvements
included in this release, please refer to the following issues on the
PDFBox issue tracker at https://issues.apache.org/jira/browse/PDFBOX.

Bug

[PDFBOX-3272] - Loaded fonts file descriptors open after closing document
[PDFBOX-3273] - Fonts not rendered correctly
[PDFBOX-3276] - Double encryption dictionary for files with XRef stream
[PDFBOX-3279] - PDDocument.importPage creates two inputstreams
[PDFBOX-3281] - HTML output wrongly specifies UTF-16 in header
[PDFBOX-3286] - Think I found a bad constant (TTF) value and constant use in
PDFBox source
[PDFBOX-3292] - Error reading stream, expected='endstream' actual='' in
non-truncated files
[PDFBOX-3297] - Infinite loop
[PDFBOX-3299] - TIFF-files with FillOrder=2 can't be converted to PDF
[PDFBOX-3301] - NPE in PDAcroForm.flatten if a widget doesn't contain a /P entry
[PDFBOX-3303] - setWidgets should set connection to parent
[PDFBOX-3308] - Missing endOfName chars
[PDFBOX-3312] - NPE in saveIncremental() / fix javadoc
[PDFBOX-3317] - Merged PDF/A files no longer valid PDF/A
[PDFBOX-3319] - Chinese character overlap other chinese character

Improvement

[PDFBOX-3275] - Show glyph bounds in DrawPrintTextLocations
[PDFBOX-3289] - Wrong unit MM_PER_INCH in PDRectangle
[PDFBOX-3295] - Improve parsing performance of object streams
[PDFBOX-3305] - PDPageContentStream should allow drawing images at current
position
[PDFBOX-3307] - Enable AES128 encryption
[PDFBOX-3323] - Cannot set destination meta data in PDFMergerUtility

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/pdfbox/KEYS.

About Apache PDFBox
---

Apache PDFBox is an open source Java library for working with PDF documents.
This project allows creation of new PDF documents, manipulation of existing
documents and the ability to extract content from documents. Apache PDFBox
also includes several command line utilities. Apache PDFBox is published
under the Apache License, Version 2.0.

For more information, visit http://pdfbox.apache.org/

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.

For more information, visit http://www.apache.org/

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



[ANNOUNCE] Apache PDFBox 1.8.12 released

2016-04-26 Thread Andreas Lehmkühler
The Apache PDFBox community is pleased to announce the release of
Apache PDFBox version 1.8.12. The release is available for download at:

http://pdfbox.apache.org/download.cgi

See the full release notes below for details about this release.

Release Notes -- Apache PDFBox -- Version 1.8.12

Introduction


The Apache PDFBox library is an open source Java tool for working with PDF
documents.

This is an incremental bugfix release based on the earlier 1.8.11 release. It 
contains a couple of fixes and small improvements.

For more details on all fixes included in this release, please refer to the
following
issues on the PDFBox issue tracker at
https://issues.apache.org/jira/browse/PDFBOX.

Bug

[PDFBOX-1995] - AdobePDFSchema.getProducer() returns empty string
[PDFBOX-2428] - An error occured when reading table hmtx
[PDFBOX-3024] - Preflight validation call PDType0Font.clear at the wrong time
[PDFBOX-3116] - COSNumber NumberFormatException for large number
[PDFBOX-3201] - Skip zlib-header and checksum to avoid DataFormatException
[PDFBOX-3204] - JVM crashes on PDFRenderer.renderImageWithDPI
[PDFBOX-3217] - PdfaExtensionHelper.populatePDFAPropertyType
[PDFBOX-3226] - No such Element Exception processing File
[PDFBOX-3229] - Decryption fails when Metadata not encrypted but EncryptMetadata
is true/default.
[PDFBOX-3235] - ColorSpace validation fails for inlined image
[PDFBOX-3237] - ASCII85Filter does not use or recognize the correct end-of-data
terminator
[PDFBOX-3254] - Corrupted XMP causes java.lang.StringIndexOutOfBoundsException
[PDFBOX-3257] - XMPSchemaBasic setCreateDate and setModifyDate don't work if
already set
[PDFBOX-3258] - XMPBox XMPBasicSchema setters don't work if already set
[PDFBOX-3259] - ClassCastException in PDTilingPattern.getContents
[PDFBOX-3285] - All lines that use a given font stop rendering if 'ö' is
inserted - 
ArrayIndexOutOfBoundsException in TTFSubFont.buildPostTable
[PDFBOX-3297] - Infinite loop
[PDFBOX-3299] - TIFF-files with FillOrder=2 can't be converted to PDF
[PDFBOX-3308] - Missing endOfName chars
[PDFBOX-3321] - ASCII stream data size is increased when written

Improvement

[PDFBOX-1840] - Automatically load isartor for preflight tests
[PDFBOX-3196] - Update maven plugins and apache parent pom
[PDFBOX-3231] - Update PDPropBuildDataDict
[PDFBOX-3251] - Improve parsing and validation of ColorSpace for inline image
[PDFBOX-3295] - Improve parsing performance of object streams

Wish

[PDFBOX-3241] - return original PDF Header


Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/pdfbox/KEYS.

About Apache PDFBox
---

Apache PDFBox is an open source Java library for working with PDF documents.
This project allows creation of new PDF documents, manipulation of existing
documents and the ability to extract content from documents. Apache PDFBox
also includes several command line utilities. Apache PDFBox is published
under the Apache License, Version 2.0.

For more information, visit http://pdfbox.apache.org/

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.

For more information, visit http://www.apache.org/

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



Re: Jira Spam - And changes made as a result.

2016-04-22 Thread Andreas Lehmkühler


> Petr Slabý <sl...@kadel.cz> hat am 22. April 2016 um 10:49 geschrieben:
> 
> 
> Hi,
> does that mean that you are free of bug reports from now on? That is a great 
> invention, we should make the same in our company internal JIRA, that would 
> save a lot of work to me :-)
Hopefully nowone already filed a patent on that ;-)
> 
> Can you please add me to a group which is allowed to post issues, too?
Done. 

BR
Andreas
> 
> Best regards,
> Petr.
> 
> -Původní zpráva- 
> From: Andreas Lehmkühler
> Sent: Friday, April 22, 2016 10:31 AM
> To: dev@pdfbox.apache.org
> Subject: Re: FW: Jira Spam - And changes made as a result.
> 
> 
> Hi,
> 
> > Simon Steiner <simonsteiner1...@gmail.com> hat am 22. April 2016 um 10:17
> > geschrieben:
> >
> >
> > Hi,
> >
> >
> >
> > I cant create/comment on pdfbox issues anymore.
> I've added your account ot the contributor group so that you should be able 
> to
> comment/creat again
> 
> BR
> Andreas
> 
> >
> >
> >
> > Thanks
> >
> >
> >
> > From: Gav [mailto:gmcdon...@apache.org]
> > Sent: 22 April 2016 01:14
> > To: infrastruct...@apache.org Infrastructure <infrastruct...@apache.org>
> > Subject: Jira Spam - And changes made as a result.
> >
> >
> >
> > Hi All,
> >
> > Apologies for notifying you after the fact.
> >
> > Earlier today (slowing down to a halt about 1/2 hr ago due to our changes) 
> > we
> > had a
> >
> > big Spam attack directed at the ASF Jira instance.
> >
> > Many project were affected, including :-
> >
> > TM, ARROW ACCUMULO, ABDERA, JSPWIKI, QPIDIT, LOGCXX, HAWQ, AMQ, ATLAS,
> > AIRFLOW, ACE, APEXCORE, RANGER and KYLIN .
> >
> > During the process we ended up banning 27 IP addresses , deleted well over 
> > 200
> > tickets, and about 2 dozen user accounts.
> >
> > The spammers were creating accounts using the normal system and going 
> > through
> > the required captchas.
> >
> > In addition to the ban hammer and deletions and to prevent more spam 
> > coming
> > in, we changed the 'Default Permissions Scheme' so that anyone in the
> > 'jira-users' group are no longer allowed to 'Create' tickets and are no 
> > longer
> > allowed to 'Comment' on any tickets.
> >
> > Obviously that affects genuine users as well as the spammers, we know 
> > that.
> >
> > Replacement auth instead of jira-users group now includes allowing those 
> > in
> > the 'Administrator, PMC, Committer, Contributor and Developer' ROLES in 
> > jira.
> >
> > Projects would you please assist in making this work - anyone that is not 
> > in
> > any of those roles for your project; and needs access to be able to create
> > issues and comment, please do add their jira id to one of the available 
> > roles.
> > (Let us know if you need assistance in this area)
> >
> > This is a short term solution. For the medium to long term we are working 
> > on
> > providing LDAP authentication for Jira and Confluence through Atlassian 
> > Crowd
> > (likley).
> >
> > If any projects are still being affected, please notify us as you may be 
> > using
> > another permissions scheme to the one altered. Notify us via INFRA jira 
> > ticket
> > or reply to this mail to infrastruct...@apache.org
> > <mailto:infrastruct...@apache.org>  or join us on hipchat
> > (https://www.hipchat.com/gIjVtYcNy)
> >
> > Any project seriously adversely impacted by our changes please do come 
> > talk to
> > us and we'll see what we can work out.
> >
> > Thanks all for your patience and understanding.
> >
> > Gav... (ASF Infra)
> >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>

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



Re: FW: Jira Spam - And changes made as a result.

2016-04-22 Thread Andreas Lehmkühler

Hi,

> Simon Steiner  hat am 22. April 2016 um 10:17
> geschrieben:
> 
> 
> Hi,
> 
>  
> 
> I cant create/comment on pdfbox issues anymore.
I've added your account ot the contributor group so that you should be able to
comment/creat again

BR
Andreas

> 
>  
> 
> Thanks
> 
>  
> 
> From: Gav [mailto:gmcdon...@apache.org] 
> Sent: 22 April 2016 01:14
> To: infrastruct...@apache.org Infrastructure 
> Subject: Jira Spam - And changes made as a result.
> 
>  
> 
> Hi All,
> 
> Apologies for notifying you after the fact.
> 
> Earlier today (slowing down to a halt about 1/2 hr ago due to our changes) we
> had a
> 
> big Spam attack directed at the ASF Jira instance.
> 
> Many project were affected, including :-
> 
> TM, ARROW ACCUMULO, ABDERA, JSPWIKI, QPIDIT, LOGCXX, HAWQ, AMQ, ATLAS,
> AIRFLOW, ACE, APEXCORE, RANGER and KYLIN .
> 
> During the process we ended up banning 27 IP addresses , deleted well over 200
> tickets, and about 2 dozen user accounts.
> 
> The spammers were creating accounts using the normal system and going through
> the required captchas.
> 
> In addition to the ban hammer and deletions and to prevent more spam coming
> in, we changed the 'Default Permissions Scheme' so that anyone in the
> 'jira-users' group are no longer allowed to 'Create' tickets and are no longer
> allowed to 'Comment' on any tickets.
> 
> Obviously that affects genuine users as well as the spammers, we know that. 
> 
> Replacement auth instead of jira-users group now includes allowing those in
> the 'Administrator, PMC, Committer, Contributor and Developer' ROLES in jira.
> 
> Projects would you please assist in making this work - anyone that is not in
> any of those roles for your project; and needs access to be able to create
> issues and comment, please do add their jira id to one of the available roles.
> (Let us know if you need assistance in this area)
> 
> This is a short term solution. For the medium to long term we are working on
> providing LDAP authentication for Jira and Confluence through Atlassian Crowd
> (likley).
> 
> If any projects are still being affected, please notify us as you may be using
> another permissions scheme to the one altered. Notify us via INFRA jira ticket
> or reply to this mail to infrastruct...@apache.org
>   or join us on hipchat
> (https://www.hipchat.com/gIjVtYcNy)
> 
> Any project seriously adversely impacted by our changes please do come talk to
> us and we'll see what we can work out.
> 
> Thanks all for your patience and understanding.
> 
> Gav... (ASF Infra)
>

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



New PDFBox releases 1.8.12 and 2.0.1

2016-04-19 Thread Andreas Lehmkühler
Hi,

as there are already a couple of changes for both branches (1.8 and 2.0) I'm
going to cut a release for both next friday april 22th at about 18:00 CET.

Please have a look at all scheduled jira tickets which aren't set to resolved
yet. Either solve them or simply move them to another version. I've just created
the new jira versions 1.8.13 and 2.0.2.

BR
Andreas

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



RE: shading/relocating 1.8.x?

2016-03-29 Thread Andreas Lehmkühler
> "Allison, Timothy B."  hat am 28. März 2016 um 21:02
> geschrieben:
> 
> 
> Oh, wow, so it really might be possible without too much work?  I'm more than
> happy to supply examples. :) 
Ups, it isn't as simply as it sounds. If we simply swallow the exception pdfbox
most likel runs into a NPE. IMHO we have to implement some sort of an on demand
parser which is able to handle null-values for specific parts of a pdf without
throwing any exception.

> Should I open an issue?
Thanks, but I'm going to do that soon, as some other things should be done as
well.

BR
Andreas
> 
> 
> -Original Message-
> From: Andreas Lehmkuehler [mailto:andr...@lehmi.de] 
> Sent: Monday, March 28, 2016 10:58 AM
> To: dev@pdfbox.apache.org
> Subject: Re: shading/relocating 1.8.x?
> 
> Am 25.03.2016 um 17:39 schrieb John Hewson:
> >
> >> On 23 Mar 2016, at 06:20, Allison, Timothy B.  wrote:
> >>
> >> All,
> >>   We've upgraded to 2.0.0 on Tika.  Many thanks again!
> >>   One of our users is interested in continuing to use the
> >> classic/SequentialParser, or at least having it available as a back-off
> >> parser for corrupt pdfs [0].
> >
> > Using the old parser really isn’t a good idea, it’s known to be pretty
> > broken. I think that we would be much better off making sure the new parser
> > can handle truncated files. We already do a lot of repair in the new parser,
> > so this doesn’t seem like to much work? Maybe Andreas can comment further?
> The biggest issue here is the truncated stream or dictionary. The current
> version simply throws an exception when running into such constellations. We
> have to implement some algorithm to ignore such incomplete parts of a pdf if
> possible.
> 
> BR
> Andreas
> 
> >
> > Do we have some JIRA issues which identify some of these cases?
> >
> > — John
> >
> >>   Would you be willing to distribute a shaded/relocated 1.8.x app so that
> >> we could load both 1.8.x and 2.0.0 in the same jvm without collisions?  Or,
> >> is there a better solution?
> >
> > I wouldn’t recommend doing that, because you’re going to be stuck with using
> > 1.8 for everything, not just parsing, at least as far as corrupt/truncated
> > files are concerned.
> >
> > — John
> >
> >>   Thank you!
> >>
> >>   Cheers,
> >>
> >>  Tim
> >>
> >> [0]
> >> https://issues.apache.org/jira/browse/TIKA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208360#comment-15208360
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: PDFBox 2.1

2016-03-29 Thread Andreas Lehmkühler
> Maruan Sahyoun  hat am 29. März 2016 um 12:28
> geschrieben:
> 
> 
> Hi,
> 
> now as PDFBox 2.0 is out what about collecting ideas for 2.1? Could put that
> on our website the same way we had the old ideas published.
Goodi idea!

> From my perspective:
> - simplify creation of AcroForm fields
> - appearance generation for new AcroForm fields
> - rework/enhancement to the plain text formatter.
> - Java 1.7
> - incremental parsing i.e. page by page
> - discussion/decision on XMP (shall we enhance XMPBox, restore Jempbox, base
> on Adobe's XMP library, join forces with the FOP project …)
Most likely some of these ideas will come with breaking changes, so that we have
to think about the correct target: 2.1 vs 3.0

> 
> 
> BR
> Maruan

BR
Andreas

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



Re: pdfbox 2

2016-02-15 Thread Andreas Lehmkühler
Hi,

> Simon Steiner  hat am 15. Februar 2016 um 11:46
> geschrieben:
> 
> 
> Hi,
> 
>  
> 
> Whats the release date for pdfbox 2?
We don't have a fix date, but I'm pretty sure that the next release will be the
final one and I guess it'll be releases quite soon.

> Thanks

BR
Andreas

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



JIRA and PDFBOx 1.8.11

2016-01-18 Thread Andreas Lehmkühler
Hi,

due to the PDFBox 1.8.11 release I've closed all resolved 1.8.11 related issues
in a bulk operation without email notification to avoid an email flood.

I already created a new version 1.8.12 some days ago.

BR
Andreas

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



[ANNOUNCE] Apache PDFBox 2.0.0 RC3 released

2016-01-15 Thread Andreas Lehmkühler
The Apache PDFBox community is pleased to announce the release of
Apache PDFBox version 2.0.0 RC3. The release is available for download at:

http://pdfbox.apache.org/download.cgi

The numerous feedback on our second release candidate helps us to make
this release candidate better again, e. g. optimized font cache, improved text
extraction. A lot of bug fixes are included as well.
We'd like to thank everybody who helps us to get a step foward.
Please have a look at the new release candidate as well, so that the next
release hopefully could be the final one.

See the full release notes below for details about this release.

Release Notes -- Apache PDFBox -- Version 2.0.0-RC3

Introduction


The Apache PDFBox library is an open source Java tool for working with PDF
documents.

This is the third release candidate for the upcoming major release 2.0.0 of
PDFBox.
This release contains a lot of improvements, fixes and refactorings. The API is 
supposed to be stable, but we can't guarantee that there won't be any last
changes
to it before providing the final release candidate.

For more details on these changes and all the other fixes and improvements
included in this release, please refer to the following issues on the
PDFBox issue tracker at https://issues.apache.org/jira/browse/PDFBOX.

Sub-task

[PDFBOX-1869] - Implementation for ShadingType 1
[PDFBOX-1870] - PDFunctionType0 incorrect
[PDFBOX-2117] - AxialShadingContext is slow
[PDFBOX-2279] - Text with gradient not shown
[PDFBOX-2529] - Preflight: mention the page on which a problem has been found
[PDFBOX-2531] - better error message on not yet read stream
[PDFBOX-2535] - mention subtype in COSStream IOException
[PDFBOX-2536] - More specific TIFFFaxDecoder exceptions
[PDFBOX-2537] - do not discard underlying cause when creating validation error
[PDFBOX-2611] - possibly incorrect error message "Hexa String must have only
Hexadecimal Characters" in preflight
[PDFBOX-2612] - error "Destination contains invalid page reference 'null'" is
not detected by preflight
[PDFBOX-2613] - Conflicting /N information for OutputIntent not detected by
preflight
[PDFBOX-2614] - missing /Type/FontDescriptor not detected by preflight
[PDFBOX-2619] - XMP dates contain time zone, while document info dates do not,
and this isn't detected by preflight
[PDFBOX-2625] - Preflight error: The character with CID 0 should have a width
equals to 57.0, but has 57.78
[PDFBOX-2627] - Add block composer to handle multiline text
[PDFBOX-2630] - "loop in destinations" not detected by preflight
[PDFBOX-2647] - Check thumbnails in XMP metadata
[PDFBOX-2718] - Allow to create new AcroForm fields from scratch
[PDFBOX-2783] - Remove getCOSDictionary() method, adjust getCOSObject() return
type
[PDFBOX-2849] - fix problems with setting existing AcroForm buttons
[PDFBOX-2863] - Support the comb flag for PDF forms
[PDFBOX-2877] - Wrong text placement for autosize fields compared to Adobe
generated
[PDFBOX-2889] - Support appearance generation for choice fields
[PDFBOX-2900] - PDF Debugger doesn't print inline images correctly
[PDFBOX-2993] - Create a PDTransparencyGroup for added code clarity
[PDFBOX-2994] - Rename PDGroup to PDTransparencyGroupAttributes
[PDFBOX-3051] - COSArray.getObject() incorrect handling of indirect reference to
COSNull
[PDFBOX-3052] - NPE in PDFStreamEngine.ShowText when no font set
[PDFBOX-3053] - Text extraction fails with type 3 fonts
[PDFBOX-3057] - NPE in CFFParser.parseType1Dicts()
[PDFBOX-3060] - Catalog cannot be found
[PDFBOX-3061] - Word concatenation in 2.0 not in 1.8
[PDFBOX-3062] - Text extraction and height different in 2.0
[PDFBOX-3068] - Null metadata in 2.0 in some files that had metadata in 1.8.10
with old parser
[PDFBOX-3112] - Avoid crazy /Length1 values in font descriptor
[PDFBOX-3123] - Text extraction garbled in this file, was OK in 1.8
[PDFBOX-3125] - IndexOutOfBoundsException in PDFont.getWidth()
[PDFBOX-3126] - IndexOutOfBoundsException in PfbParser.parsePfb
[PDFBOX-3127] - Text with vertical font not extracted correctly
[PDFBOX-3129] - NullPointerException in PDFStreamEngine.showText()
[PDFBOX-3186] - Parsing fails when XRef stream object is 1 byte later

Bug

[PDFBOX-31] - bug with the Type3 font
[PDFBOX-37] - Text Extraction Weirdness
[PDFBOX-40] - Font problem when setting form value
[PDFBOX-53] - Problem getting value from PDRadioCollection
[PDFBOX-54] - please correct the SetField example
[PDFBOX-62] - Incorrect (zero) character widths returned in some docs
[PDFBOX-101] - ImportXFDF results in PDF with larger text fields
[PDFBOX-123] - too many space made in extracted text file
[PDFBOX-129] - Error when setting the value of a combo box to " "
[PDFBOX-159] - Field renaming character set problem
[PDFBOX-161] - java.util.EmptyStackException from PDFTextStripper.writeText
[PDFBOX-166] - ConvertColorSpace RGB to CMYK
[PDFBOX-198] - Tiff image problems
[PDFBOX-205] - Miscellaneous errors on valid files
[PDFBOX-239] - PDFToImage prints every word 

Re: [VOTE] Release Apache PDFBox 1.8.11

2016-01-13 Thread Andreas Lehmkühler
Hi,

> Maruan Sahyoun  hat am 14. Januar 2016 um 07:48
> geschrieben:
> 
> 
> Hi,
> 
> I'd cancel the vote and redo the release.
Just for the record, if you would like to do so, you have to withdraw your vote
and cast a -1 instead. ;-)

But I agree and I'm going to stop the vote due to the regression.

I'm going to cut the second attempt this evening (in about 10 hours from now) if
no one objects.

BR
Andreas


> 
> BR
> Maruan
> 
> > Am 13.01.2016 um 18:23 schrieb Tilman Hausherr :
> > 
> > Please see this
> > 
> > https://issues.apache.org/jira/browse/PDFBOX-3193
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 

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



[RESULT][VOTE] Release Apache PDFBox 1.8.11 CANCELLED

2016-01-13 Thread Andreas Lehmkühler
Hi,

> Andreas Lehmkuehler  hat am 11. Januar 2016 um 20:39
> geschrieben:
> 
> 
> Hi,
> 
> a candidate for the PDFBox 1.8.11 release is available at:
> 
>  https://dist.apache.org/repos/dist/dev/pdfbox/1.8.11/
> 
> The release candidate is a zip archive of the sources in:
> 
>  http://svn.apache.org/repos/asf/pdfbox/tags/1.8.11/
> 
> The SHA1 checksum of the archive is e2494b60b0ff376ea66211bff2dd0ea2059b0155.
> 
> Please vote on releasing this package as Apache PDFBox 1.8.11.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 PDFBox PMC votes are cast.

The vote was cancelled due to a regression [1]

I'm going to cut another release soon.

Thanks for your input so far.

BR
Andreas

[1] https://issues.apache.org/jira/browse/PDFBOX-3193

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



Re: Odp.: JIRA contributors

2015-11-19 Thread Andreas Lehmkühler
Hi,

> Maciej Woźniak  hat am 16. November 2015 um
> 20:31 geschrieben:
> 
> 
> 
> 
> 
> 
> Hello
> 
> 
> I would like to assign some issues to myself (PDFox project), but I can't do
> it. I have joined mailing lists and I have created an account on JIRA. Cold
> you please help me?
> 
Ordinary JIRA-user don't have the permission to do so. What is your JIRA-account
name?

What are you planning to work on? You can start with attaching a patch to the
concerned ticket without assigning the ticket to you.

P.S.: Please ask such questions on dev@

BR
Andreas

> 
> Maciej

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



Re: 2.0.0-RC2

2015-11-18 Thread Andreas Lehmkühler

> Tilman Hausherr  hat am 18. November 2015 um 07:50
> geschrieben:
> 
> 
> Am 18.11.2015 um 07:38 schrieb Maruan Sahyoun:
> > I'd like to see PDFBOX-3082 to be addressed or at least the patch provided
> > by Tom Callahan to be reviewed.
> > It has a very high impact on memory usage and there were several complaints.
> 
> I hope to be able to test, review and commit the rest of his patch 
> before 20:00. But the part I committed should also bring some improvement.
We could postpone the release for another day or two if needed.

BR
Andreas
 
> Tilman
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 

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



Re: 2.0.0-RC2

2015-11-17 Thread Andreas Lehmkühler
Hi,

> Andreas Lehmkuehler <andr...@lehmi.de> hat am 9. November 2015 um 18:36
> geschrieben:
> 
> 
> Hi,
> 
> Am 07.11.2015 um 14:38 schrieb Andreas Lehmkuehler:
> > On 11/06/2015 10:24 PM, Andreas Lehmkuehler wrote:
> >> I've found work around for my problem (gfx card). It's not perfect, but it
> >> works.
> > The work around doesn't work for my signing environment. :-(
> >
> > We have to postpone the RC
> Everything works again. I'm going to cut the RC next week on wednesday (18th) 
> and I promise not to change anything until I'm finished with the release.
I'm still planning to cut the RC tomorrow (approx. 30 hours from now). Any
objections?

BR
Andreas

> 
> BR
> Andreas
> 
> >
> > BR
> > ANdreas
> >
> >>
> >> I'll try to find some time tomorrow to cut the RC .
> >>
> >> BR
> >> Andreas
> >>
> >> On 11/06/2015 07:58 PM, Andreas Lehmkühler wrote:
> >>> Hi,
> >>>
> >>> I have bad news. After a software update my machine is somehow broken and
> >>> I
> >>> couldn't get it to run.
> >>>
> >>> I'm afraid we have to postpone the RC2.
> >>>
> >>> Sorry, my fault :-((
> >>>
> >>> BR
> >>> Andreas
> >>>
> >>>> John Hewson <j...@jahewson.com> hat am 6. November 2015 um 19:12
> >>>> geschrieben:
> >>>>
> >>>>
> >>>> Ok, I’m done making changes. PDFBOX-2950 is working well enough now. So
> >>>> I’m
> >>>> happy for RC2.
> >>>>
> >>>> — John
> >>>>
> >>>>
> >>>>> On 6 Nov 2015, at 09:21, John Hewson <j...@jahewson.com> wrote:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> I’m online now and will take a look at the build issue. Sorry, I’d
> >>>>> assumed
> >>>>> that Id fixed it yesterday one my local build passed, but I don’t run
> >>>>> Isartor so I missed that one.
> >>>>>
> >>>>> — John
> >>>>>
> >>>>>> On 5 Nov 2015, at 22:30, Andreas Lehmkuehler <andr...@lehmi.de> wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>>
> >>>>>> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> do we need another release candidate before releasing the final
> >>>>>>> version?
> >>>>>>>
> >>>>>>> I would have some cycles to cut a RC2 this week only (on Wednesday?).
> >>>>>>>
> >>>>>>> WDYT?
> >>>>>>
> >>>>>> I'm going to cut the RC today in the evening (CET) aprox. 10-12 hours
> >>>>>> from
> >>>>>> now
> >>>>>>
> >>>>>> BUT I wont' do it if the build error still persists.
> >>>>>>
> >>>>>> Any objections?
> >>>>>>
> >>>>>> BR
> >>>>>> Andreas
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> -
> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> -
> >>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: 2.0.0-RC2

2015-11-06 Thread Andreas Lehmkühler
> Tilman Hausherr <thaush...@t-online.de> hat am 6. November 2015 um 09:36
> geschrieben:
> 
> 
> Am 06.11.2015 um 08:21 schrieb Maruan Sahyoun:
> >> Am 06.11.2015 um 07:30 schrieb Andreas Lehmkuehler <andr...@lehmi.de>:
> >>
> >> Hi,
> >>
> >>
> >> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
> >>> Hi,
> >>>
> >>> do we need another release candidate before releasing the final version?
> >>>
> >>> I would have some cycles to cut a RC2 this week only (on Wednesday?).
> >>>
> >>> WDYT?
> >> I'm going to cut the RC today in the evening (CET) aprox. 10-12 hours from
> >> now
> >>
> >> BUT I wont' do it if the build error still persists.
> > +1
> >
> 
> Yes :-(
> 
> Alternatives:
> - revert the problem commits
I'm reluctant to revert commits of someone else without feedback of the origin
author.

> - shorten the voting time so that you can still to the 2nd step before 
> you're unavailable (is this 72 hours thing an apache "must"?)
There has to be enough time so that everybody who is willing/wants to help is
able to do so. We have to take into account, that not all devs may be in the
same timezone.

72 hours is a widely accepted value to ensure that nobody is ignored because of
a too short period of time for voting.

BR
Andreas

> Tilman
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: 2.0.0-RC2

2015-11-06 Thread Andreas Lehmkühler
Hi,

I have bad news. After a software update my machine is somehow broken and I
couldn't get it to run.

I'm afraid we have to postpone the RC2. 

Sorry, my fault :-((

BR
Andreas

> John Hewson <j...@jahewson.com> hat am 6. November 2015 um 19:12 geschrieben:
> 
> 
> Ok, I’m done making changes. PDFBOX-2950 is working well enough now. So I’m
> happy for RC2.
> 
> — John
> 
> 
> > On 6 Nov 2015, at 09:21, John Hewson <j...@jahewson.com> wrote:
> > 
> > Hello,
> > 
> > I’m online now and will take a look at the build issue. Sorry, I’d assumed
> > that Id fixed it yesterday one my local build passed, but I don’t run
> > Isartor so I missed that one.
> > 
> > — John
> > 
> >> On 5 Nov 2015, at 22:30, Andreas Lehmkuehler <andr...@lehmi.de> wrote:
> >> 
> >> Hi,
> >> 
> >> 
> >> Am 02.11.2015 um 12:29 schrieb Andreas Lehmkühler:
> >>> Hi,
> >>> 
> >>> do we need another release candidate before releasing the final version?
> >>> 
> >>> I would have some cycles to cut a RC2 this week only (on Wednesday?).
> >>> 
> >>> WDYT?
> >> 
> >> I'm going to cut the RC today in the evening (CET) aprox. 10-12 hours from
> >> now
> >> 
> >> BUT I wont' do it if the build error still persists.
> >> 
> >> Any objections?
> >> 
> >> BR
> >> Andreas
> >> 
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >> 
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: debugger-app

2015-11-03 Thread Andreas Lehmkühler
> John Hewson <j...@jahewson.com> hat am 2. November 2015 um 19:24 geschrieben:
> 
> 
> 
> > On 2 Nov 2015, at 02:58, Andreas Lehmkühler <andr...@lehmi.de> wrote:
> > 
> > 
> > 
> >> John Hewson <j...@jahewson.com> hat am 30. Oktober 2015 um 19:43
> >> geschrieben:
> >> 
> >> 
> >> 
> >>> On 30 Oct 2015, at 03:50, Andreas Lehmkühler <andr...@lehmi.de> wrote:
> >>> 
> >>>> 
> >>>> John Hewson <j...@jahewson.com <mailto:j...@jahewson.com>> hat am 30.
> >>>> Oktober 2015 um 08:28 geschrieben:
> >>>> 
> >>>> 
> >>>> 
> >>>>> On 30 Oct 2015, at 00:00, Andreas Lehmkuehler <andr...@lehmi.de> wrote:
> >>>>> 
> >>>>> Hi,
> >>>>> 
> >>>>> Am 29.10.2015 um 07:34 schrieb John Hewson:
> >>>>>> Hi All,
> >>>>>> 
> >>>>>> I see we’ve ended up with both “debugger” and “debugger-app” modules.
> >>>>>> Can
> >>>>>> these be combined?
> >>>>> There are separate jars so that the debugger stuff can be used as
> >>>>> dependency
> >>>>> within other projects. The debugger-app can't be used that way.
> >>>> 
> >>>> The main reason for moving the debugger into its own jar was so that it
> >>>> wouldn’t become a dependency of other projects, i.e. so that it remains
> >>>> an
> >>>> API
> >>>> internal to PDFBox, because we have no intention of keeping it stable.
> >>>> That
> >>>> would seem to be in contradiction to the situation here.
> >>> 
> >>> I've found another consumer for the debugger.jar: our own standalone app
> >>> contains to debugger as well.
> >> 
> >> That explains it. Can’t we combine debugger-app and debugger though? All
> >> that
> >> debugger-app does is add a manifest - why not put than manifest inside the
> >> debugger
> >> jar itself?
> > The app jar contains the manifest and all libs which are needed to run the
> > debugger as standalone app. AFAIKT it can't be combined, as the debugger is
> > used
> > withing the pdfbox app jar which has it's own manifest.
> 
> Why bundle the jars together? Shipping them side-by-side is just as good,
> especially as
> the 3rd party jbig2 and jpeg2000 jars (an optionally bouncy castle) have to be
> shipped
> on the side to actually provide all libraries that are needed to run the
> debugger.
> 
> The same applies to pdfbox-app, I was told that this jar exists so that the
> tools could be
> run, back when they were in that jar, but now the tools are in their own jar,
> yet we still
> have pdfbox-app? Again, because it doesn’t actually bundle the required 3rd
> party jars,
> it’s not actually fulfilling any purpose.
> 
> I guess that applies to preflight-app, too. That’s another bundle which is
> actually incomplete.
No, all standalone app jars are as complete as intended. Only some optional jars
(you've already mentioned jbig2 and jpeg2000) are missing due to their license.
But those libs aren't needed for all pdfs, so that's not a big problem.

Andreas

> — John
> 
> > BR
> > Andreas
> > 
> >> 
> >> — John
> >> 
> >>> BR
> >>> Andreas
> >>>> 
> >>>> — John
> >>>> 
> >>>>> BR
> >>>>> Andreas
> >>>>>> 
> >>>>>> — John
> >>>>>> -
> >>>>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>>>> 
> >>>>> 
> >>>>> 
> >>>>> -
> >>>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>>> 
> >>>> 
> >>>> 
> >>>> -
> >>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>> <mailto:dev-unsubscr...@pdfbox.apache.org>
> >>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>> <mailto:dev-h...@pdfbox.apache.org>
> >>>> 
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>> <mailto:dev-unsubscr...@pdfbox.apache.org>
> >>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>> <mailto:dev-h...@pdfbox.apache.org>
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



2.0.0-RC2

2015-11-02 Thread Andreas Lehmkühler
Hi,

do we need another release candidate before releasing the final version?

I would have some cycles to cut a RC2 this week only (on Wednesday?).

WDYT?

BR
Andreas

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



Re: debugger-app

2015-11-02 Thread Andreas Lehmkühler


> John Hewson <j...@jahewson.com> hat am 30. Oktober 2015 um 19:43 geschrieben:
> 
> 
> 
> > On 30 Oct 2015, at 03:50, Andreas Lehmkühler <andr...@lehmi.de> wrote:
> > 
> >> 
> >> John Hewson <j...@jahewson.com <mailto:j...@jahewson.com>> hat am 30.
> >> Oktober 2015 um 08:28 geschrieben:
> >> 
> >> 
> >> 
> >>> On 30 Oct 2015, at 00:00, Andreas Lehmkuehler <andr...@lehmi.de> wrote:
> >>> 
> >>> Hi,
> >>> 
> >>> Am 29.10.2015 um 07:34 schrieb John Hewson:
> >>>> Hi All,
> >>>> 
> >>>> I see we’ve ended up with both “debugger” and “debugger-app” modules. Can
> >>>> these be combined?
> >>> There are separate jars so that the debugger stuff can be used as
> >>> dependency
> >>> within other projects. The debugger-app can't be used that way.
> >> 
> >> The main reason for moving the debugger into its own jar was so that it
> >> wouldn’t become a dependency of other projects, i.e. so that it remains an
> >> API
> >> internal to PDFBox, because we have no intention of keeping it stable. That
> >> would seem to be in contradiction to the situation here.
> > 
> > I've found another consumer for the debugger.jar: our own standalone app
> > contains to debugger as well.
> 
> That explains it. Can’t we combine debugger-app and debugger though? All that
> debugger-app does is add a manifest - why not put than manifest inside the
> debugger
> jar itself?
The app jar contains the manifest and all libs which are needed to run the
debugger as standalone app. AFAIKT it can't be combined, as the debugger is used
withing the pdfbox app jar which has it's own manifest.

BR
Andreas

> 
> — John
> 
> > BR
> > Andreas
> >> 
> >> — John
> >> 
> >>> BR
> >>> Andreas
> >>>> 
> >>>> — John
> >>>> -
> >>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>>> 
> >>> 
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>> 
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> <mailto:dev-unsubscr...@pdfbox.apache.org>
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >> <mailto:dev-h...@pdfbox.apache.org>
> >> 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > <mailto:dev-unsubscr...@pdfbox.apache.org>
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > <mailto:dev-h...@pdfbox.apache.org>

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



Re: Convert README.txt to README.md and markdown

2015-11-02 Thread Andreas Lehmkühler
Hi,

> Maruan Sahyoun  hat am 2. November 2015 um 12:16
> geschrieben:
> 
> 
> Hi,
> 
> I would like to take the current README.txt in the projects top level folder,
> rename that to README.md and use markdown for formatting. In addition I would
> like to add some more content as a kind of quick start how to get help, file
> issues… Benefit would be that a) the README provides some basic information
> for the ones looking at the source code and b) renaming to .MD and using
> markdown will provide a better look on GitHub as that will be the initial
> document visible at the bottom of the PDFBox GitHib repo. 
> 
> WDYT?
+1, good idea

BR
Andreas

> Maruan
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: debugger-app

2015-10-30 Thread Andreas Lehmkühler

> John Hewson  hat am 30. Oktober 2015 um 08:28 geschrieben:
> 
> 
> 
> > On 30 Oct 2015, at 00:00, Andreas Lehmkuehler  wrote:
> > 
> > Hi,
> > 
> > Am 29.10.2015 um 07:34 schrieb John Hewson:
> >> Hi All,
> >> 
> >> I see we’ve ended up with both “debugger” and “debugger-app” modules. Can
> >> these be combined?
> > There are separate jars so that the debugger stuff can be used as dependency
> > within other projects. The debugger-app can't be used that way.
> 
> The main reason for moving the debugger into its own jar was so that it
> wouldn’t become a dependency of other projects, i.e. so that it remains an API
> internal to PDFBox, because we have no intention of keeping it stable. That
> would seem to be in contradiction to the situation here.

I've found another consumer for the debugger.jar: our own standalone app
contains to debugger as well.

BR
Andreas
> 
> — John
> 
> > BR
> > Andreas
> >> 
> >> — John
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >> 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



Re: News/Blog on PDFBox website

2015-10-20 Thread Andreas Lehmkühler
Hi,

> Maruan Sahyoun  hat am 19. Oktober 2015 um 10:52
> geschrieben:
> 
> 
> Hi,
> 
> I would like to start a news/blog section on the PDFBox website so we can give
> regular updates more quickly. As that is not so easily done using the Apache
> CMS I'd like to discuss moving to a local build of the website publishing to
> the Apache CMS the same way we are doing it now for the Javadoc with the maven
> scm-publish plugin (or using svnpubsub/gitpubsub at a later stage - ).
> 
> As a base for the local build I'd propose to use jekyll [http://jekyllrb.com]
> a static site generator.
> 
> WDYT?
I'm ok with that as long as 
- the new environment is available for all common platforms (OSX, Windows and
Linux)
- it's not to complicated to install a local build environment

> Maruan

BR 
Andreas

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



Re: News/Blog on PDFBox website

2015-10-20 Thread Andreas Lehmkühler


> Maruan Sahyoun <sahy...@fileaffairs.de> hat am 20. Oktober 2015 um 12:10
> geschrieben:
> 
> 
> Hi,
> 
> > Am 20.10.2015 um 11:45 schrieb Andreas Lehmkühler <andr...@lehmi.de>:
> > 
> > Hi,
> > 
> >> Maruan Sahyoun <sahy...@fileaffairs.de> hat am 19. Oktober 2015 um 10:52
> >> geschrieben:
> >> 
> >> 
> >> Hi,
> >> 
> >> I would like to start a news/blog section on the PDFBox website so we can
> >> give
> >> regular updates more quickly. As that is not so easily done using the
> >> Apache
> >> CMS I'd like to discuss moving to a local build of the website publishing
> >> to
> >> the Apache CMS the same way we are doing it now for the Javadoc with the
> >> maven
> >> scm-publish plugin (or using svnpubsub/gitpubsub at a later stage - ).
> >> 
> >> As a base for the local build I'd propose to use jekyll
> >> [http://jekyllrb.com]
> >> a static site generator.
> >> 
> >> WDYT?
> > I'm ok with that as long as 
> > - the new environment is available for all common platforms (OSX, Windows
> > and
> > Linux)
> 
> that's the case with jekyll but I'm open to other suggestions with a similar
> capability. The reason I was proposing jekyll
> - it's very active
> - several Apache Projects such as Drill, Wicket, JClouds,  are already using
> it
> - it supports markdown - so the current content can remain (with some minor
> changes to the file header)
> - supports prebuilt content which remains as is
> - it was one of the suggestions in an earlier discussion about deprecating the
> Apache CMS
> 
> > - it's not to complicated to install a local build environment
> 
> http://jekyllrb.com/docs/installation/
> http://jekyllrb.com/docs/windows/
> 
> Shall I wait for more feedback or move forward converting to jekyll?
IMHO, go ahead

BR
Andreas

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



Re: PDFBox 2.0.0 release

2015-10-12 Thread Andreas Lehmkühler
Hi,

> Maruan Sahyoun  hat am 9. Oktober 2015 um 13:01
> geschrieben:
> 
> 
> Hi,
> 

SNIP

> > Did I forget anything else?
> > 
> 
> Maybe we should announce a date when we would like to go from RC to final -
> 15th of November ?
I'm ok with that, but I can't confirm the supposed date as I won't be available
as release manager. How about the 18th or 19th of November

> BR
> Maruan
> 

BR
Andreas

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



PDFBox 2.0.0 release

2015-10-09 Thread Andreas Lehmkühler
Hi,

in a quick discussion on private@pdfbox we agreed to cut a new release next week
on october 15th. There are some questions which should be answered before:

- Are we still in the same boat? Are there any concerns not to do a release and
postpone it?
- RC or "real" release?

If we do a RC the following is done/expected

- we expect the API to be stable, but there may be some anyway if neccessary
- I won't create a 2.0.0 branch
- I'll deploy the RC to maven central and we'll provide the RC for download
through our website
- I won't close any jira tickets

Did I forget anything else?



BR
Andreas

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



Re: Apache PDFBox October 2015 board report due

2015-10-06 Thread Andreas Lehmkühler


> Maruan Sahyoun <sahy...@fileaffairs.de> hat am 6. Oktober 2015 um 08:18
> geschrieben:
> 
> 
> Hi,
> > Am 06.10.2015 um 08:07 schrieb Andreas Lehmkuehler <andr...@lehmi.de>:
> > 
> > Am 05.10.2015 um 23:02 schrieb Maruan Sahyoun:
> >> Hi,
> >> 
> >> + 1
> >> 
> >> One thing we might want to address is the large numbers of eMail to dev
> >> because of the commit etc. stuff.
> > Hmmm, I'm not sure that I've got your point. Do you want to explain the high
> > number of mails on dev@ compared to users@?
> 
> yes - as removing the commit messages from dev the traffic as users is higher
> (which is good)
There are many other projects using the dev list the same way so that we don't
have to explain that explicitly.

BR
Andreas

> Maruan
> 
> > 
> >> 
> >> Maruan
> >> 
> >>> Am 05.10.2015 um 19:47 schrieb Andreas Lehmkuehler <andr...@lehmi.de>:
> >>> 
> >>> Hi,
> >>> 
> >>> find attached a quick draft of the board report we're expected to submit
> >>> this
> >>> month. It's based upon the report template which can be found at [1]
> >>> 
> >>> 
> >>> Any further comments, objections or additions?
> >>> 
> >>> 
> >>> 
> >>> 
> >>> Report from the Apache PDFBox committee [Andreas Lehmkühler]
> >>> 
> >>> ## Description:
> >>>   The Apache PDFBox library is an open source Java tool for working with
> >>>   PDF documents.
> >>> 
> >>> ## Activity:
> >>> - after a long time of hard work we decided to cut a release candidate for
> >>>   2.0.0 this october. As we are down to 6 open tickets I'm quite
> >>> optimistic
> >>>   that it'll really come true
> >>> - we joined forces with Tim Allison from Apache TIKA to run some bulk
> >>> tests
> >>>   from time to time to avoid regressions
> >>> 
> >>> ## Health report:
> >>> - there is a steady stream of contributions, bug reports and questions on
> >>>   the mailing lists
> >>> - the core team consists of 4 - 5 active developers
> >>> - we expect to attract more people once our new major release is out of
> >>> the
> >>>   door
> >>> 
> >>> ## Issues:
> >>> - there are no issues requiring board attention at this time"
> >>> 
> >>> ## PMC changes:
> >>> 
> >>> - Currently 16 PMC members.
> >>> - No new PMC members added in the last 3 months
> >>> - Last PMC addition was John Hewson at Thu Feb 06 2014
> >>> 
> >>> ## LDAP changes:
> >>> 
> >>> - Currently 16 committers and 16 committee group members.
> >>> - No new committee group members added in the last 3 months
> >>> - No new committers added in the last 3 months
> >>> - Last committer addition was John Hewson at Fri Feb 07 2014
> >>> 
> >>> ## Releases:
> >>> 
> >>> - 1.8.10 was released on Wed Jul 22 2015
> >>> 
> >>> ## Mailing list activity:
> >>> 
> >>> - us...@pdfbox.apache.org:
> >>>- 497 subscribers (up 6 in the last 3 months):
> >>>- 519 emails sent to list (578 in previous quarter)
> >>> 
> >>> - dev@pdfbox.apache.org:
> >>>- 145 subscribers (down -4 in the last 3 months):
> >>>- 2932 emails sent to list (2594 in previous quarter)
> >>> 
> >>> 
> >>> ## JIRA activity:
> >>> 
> >>> - 151 JIRA tickets created in the last 3 months
> >>> - 143 JIRA tickets closed/resolved in the last 3 months
> >>> 
> >>> 
> >>> 
> >>> 
> >>> BR
> >>> Andreas Lehmkühler
> >>> 
> >>> [1] https://reporter.apache.org/?pdfbox
> >>> 
> >>> 
> >>> 
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >>> 
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> >> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> >> 
> > 
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> > For additional commands, e-mail: dev-h...@pdfbox.apache.org
> > 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>

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



[ANNOUNCE] Apache PDFBox 1.8.10 released

2015-07-23 Thread Andreas Lehmkühler
The Apache PDFBox community is pleased to announce the release of
Apache PDFBox version 1.8.10. The release is available for download at:

http://pdfbox.apache.org/download.cgi

See the full release notes below for details about this release.

Release Notes -- Apache PDFBox -- Version 1.8.10

Introduction


The Apache PDFBox library is an open source Java tool for working with PDF
documents.

This is an incremental bugfix release based on the earlier 1.8.9 release. It
contains a couple of fixes and small improvements.

For more details on all fixes included in this release, please refer to the
following
issues on the PDFBox issue tracker at
https://issues.apache.org/jira/browse/PDFBOX.

Bug

[PDFBOX-1453] - NPE saving modified encrypted document
[PDFBOX-1642] - NPE when parsing XMP schema definition with closed Choice
value type
[PDFBOX-2501] - Page render without barcode
[PDFBOX-2730] - PDFSplit slow and keeps unused pages
[PDFBOX-2733] - Nullpointer exception in PDFXrefStreamParser.parse
[PDFBOX-2734] - Can't create PDF with DeviceN colorspace
[PDFBOX-2737] - PDF not converted to Image
[PDFBOX-2741] - IndexOutOfBoundsException when calling
PDSeparation.setAlternateColorSpace
[PDFBOX-2742] - PDFSplit ignores global resources
[PDFBOX-2743] - Can't create PDF with PDIndexed colorspace
[PDFBOX-2745] - PDPageXYZDestination zoom property can't be set lower than 100%
[PDFBOX-2767] - ClassCastException in PDDocument.addSignature
[PDFBOX-2769] - NPE when saving encrypted file
[PDFBOX-2772] - EI token lost for rewrite
[PDFBOX-2773] - ClassCastException in PDDocumentCatalog.java:339
[PDFBOX-2778] - PDF to Image conversion fails with Invalid code word
encountered
[PDFBOX-2781] - Opening pdf document after encrypting it with PDFBox throws
IllegalBlockSizeException
[PDFBOX-2786] - PDPageDestination page index off by one
[PDFBOX-2788] - Seemingly good document gets semi-corrupted
[PDFBOX-2792] - Text extraction ignores bookmarks
[PDFBOX-2793] - /Dests dictionary isn't supported
[PDFBOX-2797] - PDJavascriptNameTreeNode does not support dictionaries
[PDFBOX-2799] - PDOptionalContentProperties.setGroupEnabled not working
[PDFBOX-2801] - SecurityHandler does not tolerate plain-text COSString
[PDFBOX-2811] - Infinite loop within RandomAccessBuffer
[PDFBOX-2812] - NPE in PDColorSpaceFactory.createColorSpace with PDICCBased
[PDFBOX-2819] - invalid ICC Profile when reading from a byte array
[PDFBOX-2823] - StringIndexOutOfBoundsException when doing
DateConverter.parseDate()
[PDFBOX-2837] - PDFBox creates files with EBCDIC code on z/OS
[PDFBOX-2847] - mergeDocumentsNonSeq does not utilize scratchFile
[PDFBOX-2853] - CCITT: Background is rendered as transparent color
[PDFBOX-2867] - Correct use of Float.NaN

Improvement

[PDFBOX-2744] - Add validation check for setNonStrokingColor and
setStrokingColor


Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.txt file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/pdfbox/KEYS.

About Apache PDFBox
---

Apache PDFBox is an open source Java library for working with PDF documents.
This project allows creation of new PDF documents, manipulation of existing
documents and the ability to extract content from documents. Apache PDFBox
also includes several command line utilities. Apache PDFBox is published
under the Apache License, Version 2.0.

For more information, visit http://pdfbox.apache.org/

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.

For more information, visit http://www.apache.org/

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



PDFBox 1.8.10 and JIRA

2015-07-23 Thread Andreas Lehmkühler
Hi,

due to the newest PDFBox 1.8.10 release I've closed all resolved 1.8.10 related
issues in a bulk operation without email notification to avoid an email flood.

I've also created a new version 1.8.11.

P.S.:
There was a small delay when announcing the new version as the CMS build was
stuck and I wasn't able to update the download page. 

BR
Andreas

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



Re: [RESULT][VOTE] Release Apache PDFBox 1.8.10

2015-07-22 Thread Andreas Lehmkühler


 Tilman Hausherr thaush...@t-online.de hat am 21. Juli 2015 um 19:16
 geschrieben:
 
 
 Am 21.07.2015 um 18:56 schrieb Andreas Lehmkuehler:
  Hi,
 
  Am 18.07.2015 um 18:16 schrieb Andreas Lehmkuehler:
  Please vote on releasing this package as Apache PDFBox 1.8.10.
 
+1 Rey Malahay (*)
+1 Tilman Hausherr
+1 Maruan Sahyoun
+1 Andreas Lehmkühler
 
 Wheew! That was close.
Indeed :-(

BR
Andreas

 Tilman
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: PDFBox 1.8.10 release

2015-07-16 Thread Andreas Lehmkühler


 Tilman Hausherr thaush...@t-online.de hat am 16. Juli 2015 um 07:13
 geschrieben:
 
 
 Am 15.07.2015 um 16:20 schrieb Allison, Timothy B.:
  Initial run on 1.8.10 is posted here:
  https://issues.apache.org/jira/browse/TIKA-1588
 
  Results: no surprises
 
  That run was done before PDFBOX-2853 was completed.
 
  Rerun now or wait for more changes in 1.8.10?
 
 No need, PDFBOX-2853 was about rendering only. So I'd say the 1.8.10 
 release can go ahead.
 
 Tilman

@Tim, @Tilman thanks fpr double checking.

I'm going to prepare the relase next weekend.

BR
Andreas
 
 
 
 
  -Original Message-
  From: Tilman Hausherr [mailto:thaush...@t-online.de]
  Sent: Thursday, July 09, 2015 2:31 PM
  To: dev@pdfbox.apache.org
  Subject: Re: PDFBox 1.8.10 release
 
  Am 30.06.2015 um 12:20 schrieb Andreas Lehmkühler:
  Hi,
 
  there are again a number of solved issues and I'm thinking about a new
  bugfix release. How about a new one next week, maybe later if someone
  wants to get some addtional things done before?
  Next open issue is PDFBOX-2853. The actual patch works fine and improves
  several images. However the same patch at another place doesn't, so I'd
  like a 2nd opinion.
 
  Tilman
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: Performance of the trunkversion

2015-07-14 Thread Andreas Lehmkühler

 Manfred Pock pock.manf...@gmail.com hat am 14. Juli 2015 um 12:15
 geschrieben:
 
 
 Yes, the input is a inputstream. I can try it direct from file.
 
 But in general we get the pdf from an document management system as stream.
 Does make sense that i save the pdf to file before?
If possible, yes. As I already said, we need random access to the pdf and
InputStream doesn't support seek operations so that we have to copy the whole
stream to a file or to memory.

 Why is there so an big performance difference beetween the version from 
 May and the current version, if we use it with useScratchFiles = true ?
I'm not sure, but the reason seems to be the altered scratchfile handling. I've
to double check that.

BR
Andreas

 regarts, Manfred
 
 Am 14.07.2015 um 12:02 schrieb Andreas Lehmkühler:
  Hi,
 
  Manfred Pock pock.manf...@gmail.com hat am 14. Juli 2015 um 11:39
  geschrieben:
 
 
  Ok, we load the pdf with useScratchFiles = true, if we load them with
  false the performance is better, but a little bit slower than the old one.
  What do you use as input, a stream or a real file? If the latter you should
  use
  the load method with the file parameter.
 
  PDFBox needs ramdom access to the pdf and if a stream is provided PDFBox
  copies
  the data to a file (lower memory usage, slower performance) or to the memory
  (higher memory usage, better performance).
 
  BR
  Andreas
 
 
  But now it need more memory. I cannot load some pdfs with the current
  version with the same java-memory configuration.
 
  Am 14.07.2015 um 11:26 schrieb Manfred Pock:
  Hi,
 
  we use the Pdfbox-trunkversion to render pdf's, currently we use the
  version from 12. May 2015.
 
  Today i have done an update to the current version and have test it.
  It seems to be that it need now much more time to render pdf's, it
  depends of the size of the pdf.
 
  for example you can try this one:
 
  http://cloud.directupload.net/15bu
 
  It need five times more then the version from May 2015.
 
  regarts, Manfred
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: Performance of the trunkversion

2015-07-14 Thread Andreas Lehmkühler
Hi,

 Manfred Pock pock.manf...@gmail.com hat am 14. Juli 2015 um 11:39
 geschrieben:
 
 
 Ok, we load the pdf with useScratchFiles = true, if we load them with 
 false the performance is better, but a little bit slower than the old one.
What do you use as input, a stream or a real file? If the latter you should use
the load method with the file parameter.

PDFBox needs ramdom access to the pdf and if a stream is provided PDFBox copies
the data to a file (lower memory usage, slower performance) or to the memory
(higher memory usage, better performance). 

BR
Andreas


 But now it need more memory. I cannot load some pdfs with the current 
 version with the same java-memory configuration.
 
 Am 14.07.2015 um 11:26 schrieb Manfred Pock:
  Hi,
 
  we use the Pdfbox-trunkversion to render pdf's, currently we use the 
  version from 12. May 2015.
 
  Today i have done an update to the current version and have test it. 
  It seems to be that it need now much more time to render pdf's, it 
  depends of the size of the pdf.
 
  for example you can try this one:
 
  http://cloud.directupload.net/15bu
 
  It need five times more then the version from May 2015.
 
  regarts, Manfred
 

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



Re: calling protect() after setAllSecurityToBeRemoved(true)

2015-07-13 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 11. Juli 2015 um 19:56
 geschrieben:
 
 
 Hi
 
  Am 11.07.2015 um 19:44 schrieb Tilman Hausherr thaush...@t-online.de:
  
  Yesterday user Roberto had a problem where a file wasn't saved with
  encryption. The cause turned out to be that he had called
  
  setAllSecurityToBeRemoved(true)
  
  and then
  
  protect(...)
  
  I didn't find it by looking at his code, only after debugging in save().
  
  Although the javadoc of both calls is clear, I see a risk that this happens
  again, e.g. when people combine existing code.
  
  What should be do? Options:
  
  1. nothing
  2. mention the risk in javadoc
  3. if allSecurityToBeRemoved is true in protect(), call LOG.warn(call
  setAllSecurityToBeRemoved(false) before saving or file won't be encrypted);
  4. if allSecurityToBeRemoved is true in protect(), throw an
  IllegalStateException
  5. set allSecurityToBeRemoved to false when protect() is called
  
  I'm for options 3 or 4.
 
 I'd go for option 5 together with a warning as the call to protect() shows the
 intention and add that to the javadocs.
+1

BR
Andreas

 BR
 Maruan
 
 
  
  Tilman
  
  
  
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
  
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org
 

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



Re: Apache PDFBox July 2015 board report due

2015-07-13 Thread Andreas Lehmkühler
Hi,

sorry for my tardiness ...

 Tilman Hausherr thaush...@t-online.de hat am 1. Juli 2015 um 20:13
 geschrieben:
 
 
 Am 01.07.2015 um 20:03 schrieb Andreas Lehmkuehler:
  Hi,
 
  find attached a quick draft of the board report we're expected to 
  submit this
  month. It's based upon the report template which can be found at [1]
 
  @Tilman
  Please provide a status about GSoC 2015
 
 Project PDFBOX-2530 improve PDFDebugger is doing nicely, many useful 
 code contributions by the student have been committed, and benefits of 
 the improved PDFDebugger are already being felt. The best is that the 
 activities of the student have motivated other committers to provide 
 additional improvements, so the whole thing is now a group effort that 
 is expanded beyond the original targets.
@Tilman: Thanks for your input. I've added it to the draft as you certainly
already saw ;-)

BR
Andreas

 Tilman
 
 
 
  Any further comments, objections or additions?
 
 
  draft
 
  Report from the Apache PDFBox project [Andreas Lehmkühler]
 
  ## Description:
 The Apache PDFBox library is an open source Java tool for working with
 PDF documents.
 
  ## Activity:
 
   - the work on our next major release 2.0.0 is an ongoing effort
   - our plan to cut a first release candidate in April didn't come true
   - we are down to round about 25 tickets for 2.0.0
 
  ## Issues:
 
   - there are no issues requiring board attention at this time
 
  ## PMC/Committership changes:
 
   - Currently 16 committers and 16 PMC members in the project.
   - No new PMC members added in the last 3 months
   - Last PMC addition was John Hewson at Tue Feb 11 2014
   - No new committers added in the last 3 months
   - Last committer addition was John Hewson at Fri Feb 07 2014
 
  ## Releases:
 
   - Last release was 1.8.9 on Sat Mar 28 2015
 
  ## Mailing list activity:
 
   - us...@pdfbox.apache.org:
  - 496 subscribers (up 15 in the last 3 months):
  - 579 emails sent to list (572 in previous quarter)
 
   - dev@pdfbox.apache.org:
  - 148 subscribers (down -2 in the last 3 months):
  - 2609 emails sent to list (3650 in previous quarter)
 
 
  ## JIRA activity:
 
   - 110 JIRA tickets created in the last 3 months
   - 97 JIRA tickets closed/resolved in the last 3 months
 
  /draft
 
  BR
  Andreas Lehmkühler
 
  [1] https://reporter.apache.org/?pdfbox
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: Broken Build

2015-07-10 Thread Andreas Lehmkühler
Hi,

 Andreas Lehmkühler andr...@lehmi.de hat am 30. Juni 2015 um 11:54
 geschrieben:

 SNIP

  Infra is still thinking about the configuration they want to use. The
  current 
  configuration doesn't work with jdk6 so that I've reconfigured our builds to
  use 
  jdk7. As there isn't any jdk including unlimited security the tests will
  fail.
 I've set up a new build job [1] using java 6 incl. unlimited security to
 ensure
 that everything works. The new job doesn't deploy to the nexus repository. The
 ailing build is still active as it is used to deploy the SNAPSHOT artifacts to
 the nexus repos.
Infra now provided jdk7 including umlimited security on all (for now it doesn't
work everywhere but at least on ubuntu3 ;-)) jenkins slaves now. Therefore I've
configured our trunk build to use that jdk, so the encryption tests won't fail
anymore.

I'm planning to setup the animal sniffer maven plugin to ensure java6 api
compatibility, so that we can get rid of the extra jdk6 based build.
 
BR 
Andreas

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



2.0.0. RC was Re: PDFBox 2.0.0 release

2015-07-07 Thread Andreas Lehmkühler
Hi,

 Andreas Lehmkühler andr...@lehmi.de hat am 6. Juli 2015 um 11:55
 geschrieben:
 
 
 Hi,
 
 
 I'd like to do a 2.0.0 release rather sooner than later and I guess I'm not
 the
 only one ;-)
 
 We are down to 24 issues marked with Fix Version 2.0.0.
 
 @Assignees: please have a look at your issues and verify if we really should
 wait for them to be resolved first or if those could be moved to a later
 release
 (2.1.0 or 3.0.0)
 
 To start with a release candidate would be another option, but I'd prefer to
 release 2.0.0.
 
 WDYT?

As there seems to be a majority supporting a release candidate I'd like to find
out what exactly a possible RC would be so that we are all on the same page:

- is it feature complete? IMHO, yes
- is the api stable? IMHO, yes
- do we create a branch or just release from a tag? IMHO, we should branch,
especially if the api is meant to be stable
- we won't push the RC to maven central but would provide a possibility to
download the RC. This is a common approach in other apache projects


How long do we wait until releasing the final 2.0? We might define some
rule/goal for that.

What exactly will be the difference between the RC and the final release? (there
are not that much open tickets left, so that I presume it won't be that big)

I'm in favour of a final release without an RC. Our release process is quite
lean so that it wouldn't hurt to much to release a 2.0.x bugfix release.

BR
Andreas

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



PDFBox 2.0.0 release

2015-07-06 Thread Andreas Lehmkühler
Hi,


I'd like to do a 2.0.0 release rather sooner than later and I guess I'm not the
only one ;-)

We are down to 24 issues marked with Fix Version 2.0.0.

@Assignees: please have a look at your issues and verify if we really should
wait for them to be resolved first or if those could be moved to a later release
(2.1.0 or 3.0.0)

To start with a release candidate would be another option, but I'd prefer to
release 2.0.0.

WDYT?

BR
Andreas Lehmkühler

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



Re: PDFBox 1.8.10 release

2015-07-02 Thread Andreas Lehmkühler
Hi,

 Tilman Hausherr thaush...@t-online.de hat am 1. Juli 2015 um 21:22
 geschrieben:
 
 
 Am 30.06.2015 um 12:20 schrieb Andreas Lehmkühler:
  Hi,
 
  there are again a number of solved issues and I'm thinking about a new
  bugfix release. How about a new one next week, maybe later if someone
  wants to get some addtional things done before?
 
 I have only one thing I'd like to test, with Tim Allison, before a 
 release: there's a line in PDTextStripper
I'm not in a hurry ... 

 
 if ((wordSpacing == 0) || (wordSpacing == Float.NaN))
 
 however wordSpacing == Float.NaN is always false. So I'd like to find 
 out if there is any difference in using what the developer probably 
 intended, which is
 
 if ((wordSpacing == 0) || (|Float.isNaN(|wordSpacing)))
 
 (BCC to Tim)
 
 Tilman


BR
Andreas

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



PDFBox 1.8.10 release

2015-06-30 Thread Andreas Lehmkühler
Hi,

there are again a number of solved issues and I'm thinking about a new
bugfix release. How about a new one next week, maybe later if someone
wants to get some addtional things done before?

WDYT?

BR
Andreas Lehmkühler

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



Re: Broken Build

2015-06-30 Thread Andreas Lehmkühler
Hi,

 Andreas Lehmkuehler andr...@lehmi.de hat am 21. Juni 2015 um 14:03
 geschrieben:
 
 
 Hi,
 
 Am 17.06.2015 um 06:38 schrieb Andreas Lehmkuehler:
  Hi,
 
  Am 12.06.2015 um 12:17 schrieb Andreas Lehmkühler:
  Hi,
 
  John Hewson j...@jahewson.com hat am 11. Juni 2015 um 19:43 geschrieben:
 
 
  Our build has been failing for about a day now, with this message:
 
  [WARNING] Could not transfer metadata
  org.apache.pdfbox:pdfbox-parent:2.0.0-SNAPSHOT/maven-metadata.xml from/to
  apache.snapshots.https
  (https://repository.apache.org/content/repositories/snapshots): peer not
  authenticated
 
  Anybody know why?
  Tilman and I already tried to find out the reason. No answer on builds@ so
  far,
  but it seems jdk related. I've configured the build to use 1.7 and
  everything
  works so far, but the tests useing strong encryption.
 
  I've created a ticket too
 
  https://issues.apache.org/jira/browse/BUILDS-85
  Infra reconfigured nexus so that one can use java 6 again. The build is back
  to
  normal.
 Infra is still thinking about the configuration they want to use. The current 
 configuration doesn't work with jdk6 so that I've reconfigured our builds to
 use 
 jdk7. As there isn't any jdk including unlimited security the tests will fail.
I've set up a new build job [1] using java 6 incl. unlimited security to ensure
that everything works. The new job doesn't deploy to the nexus repository. The
ailing build is still active as it is used to deploy the SNAPSHOT artifacts to
the nexus repos.

BR 
Andreas

[1]
https://builds.apache.org/user/lehmi/my-views/view/PDFBox/job/PDFBox-trunk%20(JDK%201.6.0%20unlimited%20security)/

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



Re: Broken Build

2015-06-12 Thread Andreas Lehmkühler
Hi,

 John Hewson j...@jahewson.com hat am 11. Juni 2015 um 19:43 geschrieben:
 
 
 Our build has been failing for about a day now, with this message:
 
 [WARNING] Could not transfer metadata
 org.apache.pdfbox:pdfbox-parent:2.0.0-SNAPSHOT/maven-metadata.xml from/to
 apache.snapshots.https
 (https://repository.apache.org/content/repositories/snapshots): peer not
 authenticated
 
 Anybody know why?
Tilman and I already tried to find out the reason. No answer on builds@ so far,
but it seems jdk related. I've configured the build to use 1.7 and everything
works so far, but the tests useing strong encryption.

I've created a ticket too

https://issues.apache.org/jira/browse/BUILDS-85


 
 — John
 

BR
Andreas

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



Re: [jira] [Resolved] (PDFBOX-2790) Syntax error in DOAP file release section

2015-05-08 Thread Andreas Lehmkühler
Hi, 

@Tilman: thanks for the fast fix.

The doap file isn't related to a specific version. It is used to automagically 
provide some information for people.a.o , only the trunk version is needed.

IMHO you might remove the fixed version and close the ticket.

BR, Andreas

Am 8. Mai 2015 19:26:59 GMT+01:00, schrieb Tilman Hausherr (JIRA) 
j...@apache.org:

[
https://issues.apache.org/jira/browse/PDFBOX-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tilman Hausherr resolved PDFBOX-2790.
-
   Resolution: Fixed
Fix Version/s: 2.0.0

 Syntax error in DOAP file release section
 -

 Key: PDFBOX-2790
 URL:
https://issues.apache.org/jira/browse/PDFBOX-2790
 Project: PDFBox
  Issue Type: Bug
  Components: Documentation
Affects Versions: 2.0.0
 Environment:
http://svn.apache.org/repos/asf/pdfbox/trunk/doap_PDFBox.rdf
Reporter: Sebb
Assignee: Tilman Hausherr
  Labels: DOAP
 Fix For: 2.0.0


 DOAP files can contain details of multiple release Versions, however
each must be listed in a separate release section, for example:
 {code}
 release
   Version
 nameApache XYZ/name
 created2015-02-16/created
 revision1.6.2/revision
   /Version
 /release
 release
   Version
 nameApache XYZ/name
 created2014-09-24/created
 revision1.6.1/revision
   /Version
 /release
 {code}
 Please can the project DOAP be corrected accordingly?
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Re: encryption as JIRA component

2015-04-30 Thread Andreas Lehmkühler
Hi,

 Tilman Hausherr thaush...@t-online.de hat am 30. April 2015 um 08:28
 geschrieben:
 
 
 Hi all,
 
 I propose that we add a component crypto as possible in the field 
 Component/s:. Often encryption is assigned Writing, but that doesn't 
 including reading and decrypting stuff.
Good idea. I've just added a component Crypto to JIRA.


 Tilman
 
 **

BR
Andreas Lehmkühler

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



Re: Build failed in Jenkins: PDFBox-trunk #1997

2015-04-17 Thread Andreas Lehmkühler
Hi,

we are not responsible for the recent build issues. I'm in contact with infra
and another committer already created a ticket BUILDS-72. 


BR
Andreas


 Apache Jenkins Server jenk...@builds.apache.org hat am 17. April 2015 um
 11:01 geschrieben:
 
 
 See https://builds.apache.org/job/PDFBox-trunk/1997/changes
 
 Changes:
 
 [msahyoun] PDFBOX-2758 fix setting title attribute
 
 [msahyoun] PDFBOX-2758 add Link annotation to FDF
 
 [msahyoun] PDFBOX-2758 initialize additional FDFAnnotations when importing
 from FDF/XFDF
 
 --
 [...truncated 1622 lines...]
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/TrailerValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/XRefValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/BookmarkValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/AbstractProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/AcroFormValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/CatalogValidationProcess.java
 A preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/SinglePageValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/ShaddingPatternValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/ActionsValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/DestinationValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/GraphicObjectPageValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/TilingPatternValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/FontValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/ExtGStateValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/AnnotationValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/reflect/ResourcesValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/StreamValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/PageTreeValidationProcess.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/process/EmptyValidationProcess.java
 A preflight/src/main/java/org/apache/pdfbox/preflight/metadata
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/metadata/PDFAIdentificationValidation.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/metadata/XpacketParsingException.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/metadata/RDFAboutAttributeConcordanceValidation.java
 AU

 preflight/src/main/java/org/apache/pdfbox/preflight/metadata/SynchronizedMetaDataValidation.java
 AU
preflight/src/main/java/org/apache/pdfbox/preflight/PreflightPath.java
 A preflight/src/main/appended-resources
 A preflight/src/main/appended-resources/META-INF
 AUpreflight/src/main/appended-resources/META-INF/NOTICE.txt
 AUpreflight/src/main/appended-resources/META-INF/LICENSE.txt
 A preflight/src/main/resources
 A preflight/src/test
 A preflight/src/test/java
 A preflight/src/test/java/org
 A preflight/src/test/java/org/apache
 A preflight/src/test/java/org/apache/pdfbox
 A preflight/src/test/java/org/apache/pdfbox/preflight
 AUpreflight/src/test/java/org/apache/pdfbox/preflight/TestIsartor.java
 A preflight/src/test/java/org/apache/pdfbox/preflight/integration
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/integration/TestInvalidFiles.java
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/integration/TestIsartorValidation.java
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/integration/AbstractInvalidFileTester.java
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/integration/TestValidFiles.java
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/TestValidDirectory.java
 AUpreflight/src/test/java/org/apache/pdfbox/preflight/Benchmark.java
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/TestInvalidDirectory.java
 AU

 preflight/src/test/java/org/apache/pdfbox/preflight/TestPreflightConfiguration.java
 A preflight/src/test/java/org/apache/pdfbox/preflight/parser
 AU

 

TravisCI

2015-04-16 Thread Andreas Lehmkühler
Hi,

https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci

@John
Is there anything to move elsewehere so that we can participate?

BR
Andreas Lehmkühler

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



Re: Apache PDFBox April 2015 board report due

2015-04-08 Thread Andreas Lehmkühler
Hi,


 Andreas Lehmkuehler andr...@lehmi.de hat am 31. März 2015 um 18:29
 geschrieben:
 
 
 Hi,
 
 find attached a quick draft of the board report we're expected to submit this
 month. It's based upon the report template which can be found at [1]
 
 @Tilman
 Please provide a status about GSoC 2015
 
 
 Any further comments, objections or additions?
I've submitted the report as is + Tilmans GSoC comment.

BR
Andreas
 
 
 draft
 
 Report from the Apache PDFBox project [Andreas Lehmkühler]
 
 ## Description:
 The Apache PDFBox library is an open source Java tool for working with
 PDF documents.
 
 ## Activity:
 
   - Apache™ PDFBox™ named an Open Source Partner Organization of the PDF
 Association, see http://s.apache.org/Wsf for further details
   - there is a steady stream of contributions and bug reports from the
 community
   - we've just released another bugfix release 1.8.9
   - the work on our next major release 2.0 is an ongoing effort
   - we are planning to cut a first release candidate in April
 
 ## Issues:
 
   - there are no issues requiring board attention at this time
 
 ## PMC/Committership changes:
 
   - Currently 16 committers and 16 PMC members in the project.
   - No new PMC members added in the last 3 months
   - Last PMC addition was John Hewson at Tue Feb 11 2014
   - No new committers added in the last 3 months
   - Last committer addition was John Hewson at Fri Feb 07 2014
 
 ## Releases:
 
   - 1.8.9 was released on Sat Mar 28 2015
 
 ## Mailing list activity:
 
   - us...@pdfbox.apache.org:
  - 480 subscribers (down -9 in the last 3 months):
  - 589 emails sent to list (344 in previous quarter)
 
   - dev@pdfbox.apache.org:
  - 151 subscribers (up 2 in the last 3 months):
  - 3710 emails sent to list (4297 in previous quarter)
 
 
 ## JIRA activity:
 
   - 153 JIRA tickets created in the last 3 months
   - 196 JIRA tickets closed/resolved in the last 3 months
 
 /draft
 
 BR
 Andreas Lehmkühler
 
 [1] https://reporter.apache.org/?pdfbox
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: Apache PDFBox April 2015 board report due

2015-04-08 Thread Andreas Lehmkühler
Hi,

 Tilman Hausherr thaush...@t-online.de hat am 31. März 2015 um 19:16
 geschrieben:
 
 
 Am 31.03.2015 um 18:29 schrieb Andreas Lehmkuehler:
  Hi,
 
  find attached a quick draft of the board report we're expected to 
  submit this
  month. It's based upon the report template which can be found at [1]
 
  @Tilman
  Please provide a status about GSoC 2015
 
 PDFBox participates in GSoC2015 with issue PDFBOX-2530, mentored by 
 Tilman Hausherr. There have been two applications. The participating 
 student will be announced on 27.4.2015.
Thanks, I've added your comment to the report

BR
Andreas

 
 
 
 Tilman
 
 
 
  Any further comments, objections or additions?
 
 
  draft
 
  Report from the Apache PDFBox project [Andreas Lehmkühler]
 
  ## Description:
 The Apache PDFBox library is an open source Java tool for working with
 PDF documents.
 
  ## Activity:
 
   - Apache™ PDFBox™ named an Open Source Partner Organization of the PDF
  Association, see http://s.apache.org/Wsf for further details
   - there is a steady stream of contributions and bug reports from the 
  community
   - we've just released another bugfix release 1.8.9
   - the work on our next major release 2.0 is an ongoing effort
   - we are planning to cut a first release candidate in April
 
  ## Issues:
 
   - there are no issues requiring board attention at this time
 
  ## PMC/Committership changes:
 
   - Currently 16 committers and 16 PMC members in the project.
   - No new PMC members added in the last 3 months
   - Last PMC addition was John Hewson at Tue Feb 11 2014
   - No new committers added in the last 3 months
   - Last committer addition was John Hewson at Fri Feb 07 2014
 
  ## Releases:
 
   - 1.8.9 was released on Sat Mar 28 2015
 
  ## Mailing list activity:
 
   - us...@pdfbox.apache.org:
  - 480 subscribers (down -9 in the last 3 months):
  - 589 emails sent to list (344 in previous quarter)
 
   - dev@pdfbox.apache.org:
  - 151 subscribers (up 2 in the last 3 months):
  - 3710 emails sent to list (4297 in previous quarter)
 
 
  ## JIRA activity:
 
   - 153 JIRA tickets created in the last 3 months
   - 196 JIRA tickets closed/resolved in the last 3 months
 
  /draft
 
  BR
  Andreas Lehmkühler
 
  [1] https://reporter.apache.org/?pdfbox
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: PDFBox AcroForms and Barcode

2015-03-27 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 27. März 2015 um 09:02
 geschrieben:
 
 
 Hi,
 
 to enhance the coverage of acroforms wrt to the PDF specification we'd need to
 support barcode fields. A lib we could use as a base is Barcode4J [1] which is
 ASL licensed. As it has features and dependencies we don't need/want I'd think
 we'd need to rip it apart and reuse what's needed and add what's missing.
 
 The other option is adding that as a dependency and add a custom Canvas
 implementation but this means that we'd also need Avalon … - which would add a
 lot to PDFBox. So I'd tend towards taking the code as a base.
 
 How could we proceed?
I'm not familiar with that acroform option. What exactly do we have to
implement? Transforming a text into a barcode I guess, but what output format,
bitmap?

BR
Andreas

 BR
 Maruan
 
 [1] http://barcode4j.sourceforge.net
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: PDFBox AcroForms and Barcode

2015-03-27 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 27. März 2015 um 09:02
 geschrieben:
 
 
 Hi,
 
 to enhance the coverage of acroforms wrt to the PDF specification we'd need to
 support barcode fields. A lib we could use as a base is Barcode4J [1] which is
 ASL licensed. As it has features and dependencies we don't need/want I'd think
 we'd need to rip it apart and reuse what's needed and add what's missing.
 
 The other option is adding that as a dependency and add a custom Canvas
 implementation but this means that we'd also need Avalon … - which would add a
 lot to PDFBox. So I'd tend towards taking the code as a base.
 
 How could we proceed?
Barcode4J contains a lot of ancient software. IMHO it would be a good idea to
strip it down to the needed parts to avoid some old stuff if possible. Or we
should try to update Barcode4J to use newer versions of the dependencies.

BR
Andreas

 BR
 Maruan
 
 [1] http://barcode4j.sourceforge.net
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: PDFBox 1.8.9 release

2015-03-23 Thread Andreas Lehmkühler


 Andreas Lehmkühler andr...@lehmi.de hat am 23. März 2015 um 09:03
 geschrieben:
 
 
 Hi,
 
  Tilman Hausherr thaush...@t-online.de hat am 22. März 2015 um 22:46
  geschrieben:
  
  
  Am 22.03.2015 um 15:53 schrieb Maruan Sahyoun:
   Am 22.03.2015 um 14:55 schrieb Tilman Hausherr thaush...@t-online.de:
  
   He already did... I need to have another look (hopefully tonight), and
   there was also some dialog between Maruan and Tim about acroforms and I'm
   not sure what the result is - whether it is OK or whether something needs
   to be done.
   the result is fine with 1.8.9 - the diff compared to the 1.8.8 output is
   because the 1.8.8 output was wrong as the same content was repeated
   multiple
   times although there was only one field.
  
   {quote}
   Therefore, we have another improvement with 1.8.9.
   {quote}
  
  Yeah, I did read that, but then the dialog went on... oh well. So the 
  only difference that remains now are weird differences depending on 
  wether Tim uses  single-thread or multi-thread. And as I said, I 'm 
  unable to investigate that. I'm satisfied that the texts are identical 
  in my tests.
 I've waited for some nice result sheet as we got last time, so that I thought
 the test isn't finished yet. However, we don't need a fancy report, it was
 just
 a wrong expection of mine. To sum it up we are all good here and I'm going to
I've just found the conversation in TIKA-1575, it seems that everything is ok.
:-)

BR
Andreas
 cut the release tomorrow evening round about 36 hours from now if nobody
 objects.
 
 BR
 Andreas
 
  
  Tilman
  
  
   Maruan
  
   Tilman
  
   Am 22.03.2015 um 14:38 schrieb Andreas Lehmkuehler:
   Hi,
  
   Am 12.03.2015 um 18:57 schrieb Allison, Timothy B.:
   Thank you, Tilman, for pinging me on this.  I should have results by
   tomorrow.
   @Tim, just a friednly reminder, any updates on the test results?
  
   BR
   Andreas
  
   Best,
  
   Tim
  
   -Original Message-
   From: Tilman Hausherr [mailto:thaush...@t-online.de]
   Sent: Thursday, March 12, 2015 1:39 PM
   To: dev@pdfbox.apache.org
   Subject: Re: PDFBox 1.8.9 release
  
   +1
  
   I'll ask Tim Allison to run his mass tests.
  
   Tilman
  
   Am 11.03.2015 um 12:12 schrieb Andreas Lehmkühler:
   Hi,
  
   there are again a number of solved issues and I'm thinking about a new
   bugfix release. How about a new one next week, maybe later if someone
   wants to get some addtional things done before?
  
   WDYT?
  
   BR
   Andreas Lehmkühler
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
   For additional commands, e-mail: dev-h...@pdfbox.apache.org
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
   For additional commands, e-mail: dev-h...@pdfbox.apache.org
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
   For additional commands, e-mail: dev-h...@pdfbox.apache.org
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
   For additional commands, e-mail: dev-h...@pdfbox.apache.org
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
   For additional commands, e-mail: dev-h...@pdfbox.apache.org
  
  
  
  
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: PDFBox 1.8.9 release

2015-03-23 Thread Andreas Lehmkühler
Hi,

 Tilman Hausherr thaush...@t-online.de hat am 22. März 2015 um 22:46
 geschrieben:
 
 
 Am 22.03.2015 um 15:53 schrieb Maruan Sahyoun:
  Am 22.03.2015 um 14:55 schrieb Tilman Hausherr thaush...@t-online.de:
 
  He already did... I need to have another look (hopefully tonight), and
  there was also some dialog between Maruan and Tim about acroforms and I'm
  not sure what the result is - whether it is OK or whether something needs
  to be done.
  the result is fine with 1.8.9 - the diff compared to the 1.8.8 output is
  because the 1.8.8 output was wrong as the same content was repeated multiple
  times although there was only one field.
 
  {quote}
  Therefore, we have another improvement with 1.8.9.
  {quote}
 
 Yeah, I did read that, but then the dialog went on... oh well. So the 
 only difference that remains now are weird differences depending on 
 wether Tim uses  single-thread or multi-thread. And as I said, I 'm 
 unable to investigate that. I'm satisfied that the texts are identical 
 in my tests.
I've waited for some nice result sheet as we got last time, so that I thought
the test isn't finished yet. However, we don't need a fancy report, it was just
a wrong expection of mine. To sum it up we are all good here and I'm going to
cut the release tomorrow evening round about 36 hours from now if nobody
objects.

BR
Andreas

 
 Tilman
 
 
  Maruan
 
  Tilman
 
  Am 22.03.2015 um 14:38 schrieb Andreas Lehmkuehler:
  Hi,
 
  Am 12.03.2015 um 18:57 schrieb Allison, Timothy B.:
  Thank you, Tilman, for pinging me on this.  I should have results by
  tomorrow.
  @Tim, just a friednly reminder, any updates on the test results?
 
  BR
  Andreas
 
  Best,
 
  Tim
 
  -Original Message-
  From: Tilman Hausherr [mailto:thaush...@t-online.de]
  Sent: Thursday, March 12, 2015 1:39 PM
  To: dev@pdfbox.apache.org
  Subject: Re: PDFBox 1.8.9 release
 
  +1
 
  I'll ask Tim Allison to run his mass tests.
 
  Tilman
 
  Am 11.03.2015 um 12:12 schrieb Andreas Lehmkühler:
  Hi,
 
  there are again a number of solved issues and I'm thinking about a new
  bugfix release. How about a new one next week, maybe later if someone
  wants to get some addtional things done before?
 
  WDYT?
 
  BR
  Andreas Lehmkühler
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: PDColorSpace.toRGBImageAWT() very slow

2015-03-20 Thread Andreas Lehmkühler
Hi,


 Tilman Hausherr thaush...@t-online.de hat am 19. März 2015 um 23:30
 geschrieben:
 
 
 I'm testing preflight on the Rackspace server of Tim Allison. Preflight 
 is very slow, and I narrowed this to
 PDColorSpace.toRGBImageAWT(), there to the line
 
op.filter(src, dest);
 
 Initialization of a CMYK based PDIndexed colorspace takes between 1 and 
 4 seconds :-( On my W7 system, it takes about 50ms.
 
 Java installed on the server:
 
 java version 1.7.0_75
 OpenJDK Runtime Environment (rhel-2.5.4.2.el7_0-x86_64 u75-b13)
 OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)
According to [1] it seems to be a regression within newer versions 1.7.0_25 of
the OpenJDK

BR
Andreas

[1]
https://bugs.openjdk.java.net/browse/JDK-8041125?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab
 
 
 Tilman
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org


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



Re: Remove commented out code

2015-03-17 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 17. März 2015 um 10:50
 geschrieben:
 
 
 Hi,
 
 we have a number of classes where the is commented out code which was
 commented out many years ago. I'd propose to remove that for 2.0. WDYT?
Remove it, as nothing gets lost due to the fact that everything still resides
within the svn repositiory.

 Maruan

BR
Andreas Lehmkühler

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



PDFBox 1.8.9 release

2015-03-11 Thread Andreas Lehmkühler
Hi,

there are again a number of solved issues and I'm thinking about a new
bugfix release. How about a new one next week, maybe later if someone
wants to get some addtional things done before?

WDYT?

BR
Andreas Lehmkühler

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



Re: Remove ant build?

2015-03-06 Thread Andreas Lehmkühler
Hi,

 Daniel Wilson williamstonconsult...@gmail.com hat am 5. März 2015 um 23:16
 geschrieben:
 
 
 Yes, it is needed for IKVM.  But I was just informed that the IKVM build is
 considered an unsupported 3rd-party version.
As Tilman already said, there wasn't any descision to stop supporting it, but as
none of the active committers uses .NET there wasn't any real support for it.
Additionally we never shipped any official .NET binary.

There was a proposal to include the IKVM build in maven but I'm still waiting
for some answers and I didn't find some time to test it myself.

 As far as I can tell, it is also needed for the TestPDFToImage junit test.
 That is the testimage target in the ant build.
 
 Btw, I DID get the ant build to produce a working version of PDFBox
 yesterday.  I simply needed to download the appropriate binaries from the
 maven repo.
We still have a jenkins ant build, which works well. 

Im just curious, as I build some unofficial .NET versions of PDFBox in the past.
What PDFBox version did you build, 1.8.8 or trunk? What version of IKVM did you
use? 

BR
Andreas Lehmkühler

 
 On Thu, Mar 5, 2015 at 2:55 PM, Tilman Hausherr thaush...@t-online.de
 wrote:
 
  I've never used it.
 
  Isn't it needed for the users of IKVM ?
 
  Tilman
 
  Am 05.03.2015 um 20:46 schrieb John Hewson:
 
  Based on discussions on the users lists, it looks like our ant build
  doesn’t actually produce working builds of PDFBox. I think we should remove
  the ant build in 2.0, we don’t need two build systems, and clearly none of
  us are maintaining it.
 
  WDYT?
 
  — John
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
  For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
 

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



Re: Build Unstable

2015-03-04 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 4. März 2015 um 14:08
 geschrieben:
 
 
 Hi,
 
 we are getting this message
 
 java.lang.NoClassDefFoundError: Could not initialize class
 org.apache.pdfbox.pdmodel.graphics.color.PDDeviceRGB
 
 Ideas?
Seems to be some Jenkins issue. It already happened some builds ago. Let's just
wait until the next one.

 BR
 Maruan

BR
Andreas Lehmkühler

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



Re: SonarQube configuration

2015-01-21 Thread Andreas Lehmkühler
Hi,

 Andreas Lehmkühler andr...@lehmi.de hat am 21. Januar 2015 um 08:53
 geschrieben:
 
 
 Hi,
 
  Tilman Hausherr thaush...@t-online.de hat am 20. Januar 2015 um 20:08
  geschrieben:
  
  
  Andreas, do you have the power to change configurations in SonarQube? My 
  wishes:
 No, unfortunately not, we have to contact infra. Do you like to do so or
 should
 I?
We have to contact builds@ not infra.

  - that the run is at 1 AM instead of 8:39 AM, this way the people who 
  use it (who all work on DE timezone) can see the latest improvements / 
  issues in the morning (currently, they appear at about 10 AM)
 +1
 
  - that the time machine keeps a additional snapshot of day-3 and 
  day-7, additional to currently day-1, day-30. Reason: this way new 
  improvements / issues won't be lost if one forgets to look at it.
 I''m not familiar with the configuration details of sonar. Is this supported
 of
 just your wish?
 
  - change the title (currently it is something generic)
 What title?
 
  Tilman
 
 
 BR
 Andreas Lehmkühler


Re: SonarQube configuration

2015-01-20 Thread Andreas Lehmkühler
Hi,

 Tilman Hausherr thaush...@t-online.de hat am 20. Januar 2015 um 20:08
 geschrieben:
 
 
 Andreas, do you have the power to change configurations in SonarQube? My 
 wishes:
No, unfortunately not, we have to contact infra. Do you like to do so or should
I?

 - that the run is at 1 AM instead of 8:39 AM, this way the people who 
 use it (who all work on DE timezone) can see the latest improvements / 
 issues in the morning (currently, they appear at about 10 AM)
+1

 - that the time machine keeps a additional snapshot of day-3 and 
 day-7, additional to currently day-1, day-30. Reason: this way new 
 improvements / issues won't be lost if one forgets to look at it.
I''m not familiar with the configuration details of sonar. Is this supported of
just your wish?

 - change the title (currently it is something generic)
What title?

 Tilman


BR
Andreas Lehmkühler


Re: Apache PDFBox January 2015 board report due

2015-01-14 Thread Andreas Lehmkühler
Hi,

 Andreas Lehmkuehler andr...@lehmi.de hat am 10. Januar 2015 um 13:50
 geschrieben:
 
 
 Hi,
 
 find attached a quick draft of the board report we're expected to submit this
 month.
I've submitted our report and added a private notice about our PDF Association
liason.

Thanks for your input/review.

BR
Andreas Lehmkühler


Re: Apache PDFBox January 2015 board report due

2015-01-14 Thread Andreas Lehmkühler
Hi,

 John Hewson j...@jahewson.com hat am 13. Januar 2015 um 19:52 geschrieben:
 
 
 On 10 Jan 2015, at 04:50, Andreas Lehmkuehler andr...@lehmi.de wrote:
  
  Hi,
  
  find attached a quick draft of the board report we're expected to submit
  this
  month.
  
  @John
  Any news about your GSoC project?
 
 Yes, my student is still around and is working on getting the Windows build
 working. Bundling native binaries with PDFBox is going to be tricky but we
 should be able to reduce it to a single plugin jar. In theory we could use
 Apache’s builedbot instances to do cross-platform C++ builds to generate a
 multi-binary jar. I’ve set this as a 2.1 issue, because the release process
 surrounding this is quite tricky for us - the the OCR plugin does currently
 work.
Thanks for the information. I didn't add anything about GSoC as there weren't
any news.

BR
Andreas Lehmkühler
 
  
  Any further comments, objections or additions?
  
  
  draft
  
  The Apache PDFBox library is an open source Java tool for working with PDF
  documents.
  
  
  General Comments
  
  
  There are no issues that require Board attention.
  
  Community
  -
  
  There is a steady stream of contributions and bug reports from the
  community.
  
  John Hewson and Tilman Hausherr were added as committers and PMC members to
  our ranks in February 2014.
  
  493 (481 last report) subscribers on the user@ list
  149 (155 last report) subscribers on the dev@ list
  
  Releases
  
  
  Version 1.8.8 was released on 13nd of December 2014. It is an incremental
  bugfix release based on PDFBox 1.8.x.
  
  
  Development:
  
  
  The work on our next major release is an ongoing effort. The main topics
  are:
  
  - switch to java 1.6
  - enhance the parser
  - code cleanup
  - enhance rendering
  - enhance font handling
  - add unicode support
  - reduce memory footprint
  
  The long-awaited new major release is still under construction and there is
  still a lot to do. Most of the bigger parts are done so that we see the
  light at the end of the tunnel.
  
  /draft
  
  BR
  Andreas Lehmkühler



Re: Apache PDFBox January 2015 board report due

2015-01-12 Thread Andreas Lehmkühler
Hi,

those information is not required, but I'm going add the following sentence:

170 JIRA tickets were created and 233 were resolved in the past 3 months.

Or do you have something different in mind?

BR
Anreas Lehmkühler

 Tilman Hausherr thaush...@t-online.de hat am 10. Januar 2015 um 16:07
 geschrieben:
 
 
 I wonder if it would make sense to include some statistic about issues 
 opened vs. issues resolved/closed. For example, a statistic like this
 
 https://issues.apache.org/jira/browse/PDFBOX/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
 
 looks very nice, it means we're getting forward, while another such as 
 this one
 
 https://issues.apache.org/jira/browse/IMAGING/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
 
 means they're falling behind (but still making a good effort).
 
 Tilman
 
 Am 10.01.2015 um 13:50 schrieb Andreas Lehmkuehler:
  Hi,
 
  find attached a quick draft of the board report we're expected to 
  submit this
  month.
 
  @John
  Any news about your GSoC project?
 
 
  Any further comments, objections or additions?
 
 
  draft
 
  The Apache PDFBox library is an open source Java tool for working with 
  PDF
  documents.
 
 
  General Comments
  
 
  There are no issues that require Board attention.
 
  Community
  -
 
  There is a steady stream of contributions and bug reports from the 
  community.
 
  John Hewson and Tilman Hausherr were added as committers and PMC 
  members to our ranks in February 2014.
 
  493 (481 last report) subscribers on the user@ list
  149 (155 last report) subscribers on the dev@ list
 
  Releases
  
 
  Version 1.8.8 was released on 13nd of December 2014. It is an 
  incremental bugfix release based on PDFBox 1.8.x.
 
 
  Development:
  
 
  The work on our next major release is an ongoing effort. The main 
  topics are:
 
  - switch to java 1.6
  - enhance the parser
  - code cleanup
  - enhance rendering
  - enhance font handling
  - add unicode support
  - reduce memory footprint
 
  The long-awaited new major release is still under construction and 
  there is still a lot to do. Most of the bigger parts are done so that 
  we see the light at the end of the tunnel.
 
  /draft
 
  BR
  Andreas Lehmkühler



Re: Apache PDFBox January 2015 board report due

2015-01-12 Thread Andreas Lehmkühler
Hi,

we shouldn't put to much information/details into our report as the board
members 
have to approve a lot of reports in preparation of a monthly meeting (this month

there are about 80 reports), but I'm going to add some brief information on the 
mentioned topics.

 Maruan Sahyoun sahy...@fileaffairs.de hat am 11. Januar 2015 um 18:02
 geschrieben:
 
 
 Tilman, Andreas,
 
 good idea. In addition we should include some of the metrics from the Sonar
 Reports
 
 a) because we made some progress there (mostly because of your efforts) and
 b) we provide feedback that such tools, provided by the ASF to us, are very
 valuable and used by the projects
 
 I'd also include the much better test coverage with the corpora testbed both
 for PDFBox 'core' as well as Preflight.
 
 Above topics could be under a 'Software Quality' header
 
 Maybe it's also worth noting the joint efforts with TIKA to show cross project
 efforts. These have been very useful I think.


Software Quality


There is an ongoing effort to improve PDFBox based on the analysis of different
tools
such as SonarQube, FindBugs and others. Only last month we reduced the number of
issues
as reported SonarQube by 20%.

We joined our forces with the Tika project. Tim Allison ran some tests on their
huge pool
of test files pdfs ( 50.000 pdfs) to
- avoid regressions when preparing the 1.8.8 bugfix release
- get clearance for updating Tika to use PDFBox 1.8.8
- find differences/improvements comparing the new major release 2.0 to the
current released version 1.8.x
- avoid regressions when switching the parser
- find cases for improvements/unsupported features and corner case pdfs not
exactly following the pdf specs


  
 
 BR
 
 Maruan

BR
Andreas Lehmkühler

 
 Am 10.01.2015 um 16:07 schrieb Tilman Hausherr thaush...@t-online.de:
 
  I wonder if it would make sense to include some statistic about issues
  opened vs. issues resolved/closed. For example, a statistic like this
  
  https://issues.apache.org/jira/browse/PDFBOX/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
  
  looks very nice, it means we're getting forward, while another such as this
  one
  
  https://issues.apache.org/jira/browse/IMAGING/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
  
  means they're falling behind (but still making a good effort).
  
  Tilman
  
  Am 10.01.2015 um 13:50 schrieb Andreas Lehmkuehler:
  Hi,
  
  find attached a quick draft of the board report we're expected to submit
  this
  month.
  
  @John
  Any news about your GSoC project?
  
  
  Any further comments, objections or additions?
  
  
  draft
  
  The Apache PDFBox library is an open source Java tool for working with PDF
  documents.
  
  
  General Comments
  
  
  There are no issues that require Board attention.
  
  Community
  -
  
  There is a steady stream of contributions and bug reports from the
  community.
  
  John Hewson and Tilman Hausherr were added as committers and PMC members to
  our ranks in February 2014.
  
  493 (481 last report) subscribers on the user@ list
  149 (155 last report) subscribers on the dev@ list
  
  Releases
  
  
  Version 1.8.8 was released on 13nd of December 2014. It is an incremental
  bugfix release based on PDFBox 1.8.x.
  
  
  Development:
  
  
  The work on our next major release is an ongoing effort. The main topics
  are:
  
  - switch to java 1.6
  - enhance the parser
  - code cleanup
  - enhance rendering
  - enhance font handling
  - add unicode support
  - reduce memory footprint
  
  The long-awaited new major release is still under construction and there is
  still a lot to do. Most of the bigger parts are done so that we see the
  light at the end of the tunnel.
  
  /draft
  
  BR
  Andreas Lehmkühler
  



Re: Sharing COS objects between COSDocuments

2015-01-08 Thread Andreas Lehmkühler


 John Hewson j...@jahewson.com hat am 8. Januar 2015 um 00:38 geschrieben:
 
 
 
  On 7 Jan 2015, at 15:01, Leonard Rosenthol lrose...@adobe.com wrote:
  
  I admit to never actually looking a the PDFBox Cos implementation, but 
  every other implementation that I’ve worked with (and it’s been quite a 
  few) have a VERY deep connection between the object and the source 
  document.  This is necessary in order to enable various features such as 
  “on-demand read” (especially important for large arrays and streams), 
  incremental updates and more.
  
  It’s your library, but I would personally strongly recommended NOT going 
  in this direction…
 
 Thanks, however I’m not proposing any changes to how PDFBox works. We
 already do on-demand reading for COS streams. When I say that there
 is nothing about a COS object that is specific to a given document, I mean
 only that there’s no problem sharing our Java COSStream instances between
 two or more COSDocument instances. This is somewhat similar to the issue
 of sharing PDPage instances between threads in Java (not safe). It’s a
 specific detail of PDFBox, rather than something to do with COS in general.
What about concurrent accesses and I'm not talking about multiple threads.
One could import a pdf to another and alter parts of the resulting one or 
the source pdf which may lead to broken docs.


BR
Andreas Lehmkühler


Re: PDFBox Docs

2015-01-08 Thread Andreas Lehmkühler


 Maruan Sahyoun sahy...@fileaffairs.de hat am 8. Januar 2015 um 12:18
 geschrieben:
 
 
 Am 08.01.2015 um 11:51 schrieb Maruan Sahyoun sahy...@fileaffairs.de:
 
  Am 08.01.2015 um 11:44 schrieb Andreas Lehmkühler andr...@lehmi.de:
  
  Hi,
  
  Maruan Sahyoun sahy...@fileaffairs.de hat am 1. Januar 2015 um 21:52
  geschrieben:
  
  
  the docs shall reside in pdfbox-docs from where they will be pulled onto
  the
  website or looked at directly at github. 
  
  The publishing process to our website is not yet in place as there is no
  new
  content. I'm looking to get the redesign of the website done to
  accommodate
  for the old 1.8 and new 2.0 release.
  
  The Apache Drill project seems to use something which could be interesting
  for
  us as well, see the posting on dev@community
  
  http://markmail.org/message/vtb3or4tf7bb2hid
  
  
  very nice idea
 
 I looked into that in more detail. This would replace the Apache CMS for most
 parts as this will be using jekyll to generate the html from the sources which
 means that all source files would be in there.
This means that we have to move the whole site to github? Or could we start with
a part of it, as planned for the docs?

 Other than that I do like the layout they have.
I don't want to start a discussion about our layout ;-) but theirs is ok.

BR
Andreas Lehmkühler

P.S.: It looks like others are also interested in that solution, DeviceMap just
asks for some pointers  I'll continue tracing the thread

  
  BR
  Andreas Lehmkühler
  
  
  Maruan
  
  Am 01.01.2015 um 19:38 schrieb John Hewson j...@jahewson.com:
  
  Hi All,
  
  We’re getting closer to 2.0 being ready and I’m thinking about writing
  some
  docs, but currently the situation seems to be worse than it was before
  the
  docs stated moving to GitHub - where are our canonical docs and how can I
  contribute to them? 
  
  All I see on GitHub is some old 1.8 stuff and an incomplete cookbook for
  forms. Is this content live anywhere? Is there a pay to preview it?
  
  -- John
  
  
  



Re: PDFBox Docs

2015-01-08 Thread Andreas Lehmkühler


 Maruan Sahyoun sahy...@fileaffairs.de hat am 8. Januar 2015 um 12:52
 geschrieben:
 
 
 
 Am 08.01.2015 um 12:39 schrieb Andreas Lehmkühler andr...@lehmi.de:
 
  
  
  Maruan Sahyoun sahy...@fileaffairs.de hat am 8. Januar 2015 um 12:18
  geschrieben:
  
  
  Am 08.01.2015 um 11:51 schrieb Maruan Sahyoun sahy...@fileaffairs.de:
  
  Am 08.01.2015 um 11:44 schrieb Andreas Lehmkühler andr...@lehmi.de:
  
  Hi,
  
  Maruan Sahyoun sahy...@fileaffairs.de hat am 1. Januar 2015 um 21:52
  geschrieben:
  
  
  the docs shall reside in pdfbox-docs from where they will be pulled onto
  the
  website or looked at directly at github. 
  
  The publishing process to our website is not yet in place as there is no
  new
  content. I'm looking to get the redesign of the website done to
  accommodate
  for the old 1.8 and new 2.0 release.
  
  The Apache Drill project seems to use something which could be
  interesting
  for
  us as well, see the posting on dev@community
  
  http://markmail.org/message/vtb3or4tf7bb2hid
  
  
  very nice idea
  
  I looked into that in more detail. This would replace the Apache CMS for
  most
  parts as this will be using jekyll to generate the html from the sources
  which
  means that all source files would be in there.
  This means that we have to move the whole site to github? Or could we start
  with
  a part of it, as planned for the docs?
 
 we can use that to only generate the docs. I can do a similar setup to see how
 that would work for us - would need to replicate some of the html template so
 it also works standalone.
 
 Shall I?
It depends on the effort and the time you want to spend on that. We should try
it if it is worth doing it.


 
  
  Other than that I do like the layout they have.
  I don't want to start a discussion about our layout ;-) but theirs is ok.
  
 
 Wasn't meant to be interpreted this way!
 
  BR
  Andreas Lehmkühler
  
  P.S.: It looks like others are also interested in that solution, DeviceMap
  just
  asks for some pointers  I'll continue tracing the thread
  
  
  BR
  Andreas Lehmkühler
  
  
  Maruan
  
  Am 01.01.2015 um 19:38 schrieb John Hewson j...@jahewson.com:
  
  Hi All,
  
  We’re getting closer to 2.0 being ready and I’m thinking about writing
  some
  docs, but currently the situation seems to be worse than it was before
  the
  docs stated moving to GitHub - where are our canonical docs and how can
  I
  contribute to them? 
  
  All I see on GitHub is some old 1.8 stuff and an incomplete cookbook
  for
  forms. Is this content live anywhere? Is there a pay to preview it?
  
  -- John
  
  
  
  



Re: PDFBox Docs

2015-01-08 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 1. Januar 2015 um 21:52
 geschrieben:
 
 
 the docs shall reside in pdfbox-docs from where they will be pulled onto the
 website or looked at directly at github. 
 
 The publishing process to our website is not yet in place as there is no new
 content. I'm looking to get the redesign of the website done to accommodate
 for the old 1.8 and new 2.0 release.

The Apache Drill project seems to use something which could be interesting for
us as well, see the posting on dev@community

http://markmail.org/message/vtb3or4tf7bb2hid

BR
Andreas Lehmkühler

 
 Maruan
 
 Am 01.01.2015 um 19:38 schrieb John Hewson j...@jahewson.com:
 
  Hi All,
  
  We’re getting closer to 2.0 being ready and I’m thinking about writing some
  docs, but currently the situation seems to be worse than it was before the
  docs stated moving to GitHub - where are our canonical docs and how can I
  contribute to them? 
  
  All I see on GitHub is some old 1.8 stuff and an incomplete cookbook for
  forms. Is this content live anywhere? Is there a pay to preview it?
  
  -- John
  



JIRA bulk change

2015-01-05 Thread Andreas Lehmkühler
Hi,

I've closed 18 JIRA tickets in a bulk change without email notification.

Those were already resolved using one of the following resolutions:

- Won't fix
- Not a problem
- Cannot reproduce
- Invalid

I removed the fix version of some of those tickets as there wasn't any fix.

BR
Andreas Lehmkühler


[VOTE] Release Apache PDFBox 1.8.8

2014-12-10 Thread Andreas Lehmkühler
Hi,

a candidate for the PDFBox 1.8.8 release is available at:

 https://dist.apache.org/repos/dist/dev/pdfbox/1.8.8/

The release candidate is a zip archive of the sources in:

 http://svn.apache.org/repos/asf/pdfbox/tags/1.8.8/

The SHA1 checksum of the archive is a9a298d0679bd95053aadad8acfaeac71268a510.

Please vote on releasing this package as Apache PDFBox 1.8.8.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 PDFBox PMC votes are cast.

 [ ] +1 Release this package as Apache PDFBox 1.8.8
 [ ] -1 Do not release this package because...

Here is my +1

BR
Andreas Lehmkühler


Re: PDFBox 1.8.8. release

2014-12-10 Thread Andreas Lehmkühler
Hi,

it took more time than expected to get the release candidate out of the door due
to some 
svn issues with the new dist repo.

BR
Andreas Lehmkühler

 Andreas Lehmkuehler andr...@lehmi.de hat am 23. November 2014 um 17:14
 geschrieben:
 
 
 Hi,
 
 Am 11.11.2014 um 12:15 schrieb Andreas Lehmkühler:
  Hi,
 
  Andreas Lehmkühler andr...@lehmi.de hat am 3. November 2014 um 11:52
  geschrieben:
 
 
  Hi,
 
  there are again a number of solved issues and I'm thinking about a new
  bugfix release. How about a new one next week, maybe later if someone
  wants to get some addtional things done before?
  Looks like I won't have the time this week to cut the release, sorry.
  I'm not sure if I'll find some time when attending ApacheCon in Budapest
  next
  week,
  but I should have some cycles in the last week of november.
 
  This will buy us some time to fix some of the encryption/decryption issues.
 I'm going to cut the release tomorrow in the evening, round about 24 hours
 from 
 now. Any objections?
 
 
 BR
 Andreas Lehmkühler


Created new version 1.8.9 in JIRA

2014-12-09 Thread Andreas Lehmkühler
Hi,

maybe a little bit to early, but I've created a new 1.8.9 version in JIRA.
Obviously Tilman already works on 2 issues fitting in this version.

BR
Andreas Lehmkühler


Re: PDFBox 1.8.8. release

2014-12-07 Thread Andreas Lehmkühler
Hi,


IMO it's time to cut the new release. I plan to do so tomorrow evening, round
about 34 hours from now. 

Any objections?

BR
Andreas Lehmkühler

 Andreas Lehmkuehler andr...@lehmi.de hat am 23. November 2014 um 17:14
 geschrieben:
 
 
 Hi,
 
 Am 11.11.2014 um 12:15 schrieb Andreas Lehmkühler:
  Hi,
 
  Andreas Lehmkühler andr...@lehmi.de hat am 3. November 2014 um 11:52
  geschrieben:
 
 
  Hi,
 
  there are again a number of solved issues and I'm thinking about a new
  bugfix release. How about a new one next week, maybe later if someone
  wants to get some addtional things done before?
  Looks like I won't have the time this week to cut the release, sorry.
  I'm not sure if I'll find some time when attending ApacheCon in Budapest
  next
  week,
  but I should have some cycles in the last week of november.
 
  This will buy us some time to fix some of the encryption/decryption issues.
 I'm going to cut the release tomorrow in the evening, round about 24 hours
 from 
 now. Any objections?
 
 
 BR
 Andreas Lehmkühler


Re: Where is the SVN repository only for PDFBox project ?

2014-11-26 Thread Andreas Lehmkühler
Hi,

 Yosuke Yamatani s151...@center.wakayama-u.ac.jp hat am 26. November 2014 um
 10:23 geschrieben:
 
 
 Dear sir/madam
 
 Hello, I’m Yosuke Yamatani.
 I’m a graduate student at Wakayama University, Japan.
 I study software evolution in OSS projects through the analysis of SVN
 repositories.
 I found the entire ASF repository, but I would like to mirror the SVN
 repository only for your project.
 Could you let me know how to get your repository ?
The PDFBox repo is part of the ASF repo and can be found here:

http://svn.apache.org/repos/asf/pdfbox/

Be aware that our infra-team implements strict rules accessing the repo
frequently:

http://www.apache.org/dev/version-control.html#poll

Abusing that rules will automatically lead to an IP-ban.


If you are simply looking for the source code you may alternatively the source
code of each released version available here:

http://pdfbox.apache.org/download.cgi

 Sincerely yours.
 Yosuke


BR
Andreas Lehmkühler


RE: PDFBox 1.8.8. release

2014-11-24 Thread Andreas Lehmkühler
Hi,

 Allison, Timothy B. talli...@mitre.org hat am 24. November 2014 um 13:10
 geschrieben:
 
 
 Let me know when to hit run...
Thanks for the offer, there is just one thing related to PDFBOX-2430 I'd like to
fix this evening .. 

BR
Andras Lehmkühler

 
 -Original Message-
 From: Andreas Lehmkuehler [mailto:andr...@lehmi.de] 
 Sent: Sunday, November 23, 2014 12:27 PM
 To: dev@pdfbox.apache.org
 Subject: Re: PDFBox 1.8.8. release
 
 Hi,
 
 Am 23.11.2014 um 17:55 schrieb Tilman Hausherr:
  Hi.
 
  I'd prefer to wait for the tests of Tim Allison... unless you want to live
  with
  the risk that he does the tests, and that we find a big problem within
  that 3
  day voting period...
 Good point.
 
  I haven't asked him to do these tests yet, because so much work was done on
  both
  parsers.
 I guess I'm done with parser changes at least in the 1.8 branch
 
  Tilman
 
 BR
 Andreas Lehmkühler
 
 
  Am 23.11.2014 um 17:14 schrieb Andreas Lehmkuehler:
  Hi,
 
  Am 11.11.2014 um 12:15 schrieb Andreas Lehmkühler:
  Hi,
 
  Andreas Lehmkühler andr...@lehmi.de hat am 3. November 2014 um 11:52
  geschrieben:
 
 
  Hi,
 
  there are again a number of solved issues and I'm thinking about a new
  bugfix release. How about a new one next week, maybe later if someone
  wants to get some addtional things done before?
  Looks like I won't have the time this week to cut the release, sorry.
  I'm not sure if I'll find some time when attending ApacheCon in Budapest
  next
  week,
  but I should have some cycles in the last week of november.
 
  This will buy us some time to fix some of the encryption/decryption
  issues.
  I'm going to cut the release tomorrow in the evening, round about 24 hours
  from now. Any objections?
 
 
  BR
  Andreas Lehmkühler
 



Re: PDFBox 1.8.8. release

2014-11-11 Thread Andreas Lehmkühler
Hi,

 Andreas Lehmkühler andr...@lehmi.de hat am 3. November 2014 um 11:52
 geschrieben:
 
 
 Hi,
 
 there are again a number of solved issues and I'm thinking about a new
 bugfix release. How about a new one next week, maybe later if someone 
 wants to get some addtional things done before?
Looks like I won't have the time this week to cut the release, sorry.
I'm not sure if I'll find some time when attending ApacheCon in Budapest next
week,
but I should have some cycles in the last week of november.

This will buy us some time to fix some of the encryption/decryption issues.

BR
Andreas Lehmkühler


PDFBox 1.8.8. release

2014-11-03 Thread Andreas Lehmkühler
Hi,

there are again a number of solved issues and I'm thinking about a new
bugfix release. How about a new one next week, maybe later if someone 
wants to get some addtional things done before?

WDYT?

BR
Andreas Lehmkühler


Re: repository for jai_imageio

2014-10-31 Thread Andreas Lehmkühler
Hi,

we can't use our release channels to push third party artifacts to meven
central.

The correct way is to open an issue here [1]. But according to [2] they won't
push those artifats to the repo.

BR
Andreas Lehmkühler

[1] https://issues.sonatype.org/browse/MVNCENTRAL/
[2] https://issues.sonatype.org/browse/MVNCENTRAL-341

 John Hewson j...@jahewson.com hat am 30. Oktober 2014 um 23:14 geschrieben:
 
 
 Could we push our own copy to e.g. maven central?
 
 -- John
 
  On 30 Oct 2014, at 14:04, Tilman Hausherr thaush...@t-online.de wrote:
  
  That one doesn't work... that is a link to maven central, to
  http://central.maven.org/maven2/com/sun/media/jai_imageio/1.1/
  and it has only the javadocs :-(
  
  Tilman
  
  Am 30.10.2014 um 21:32 schrieb John Hewson:
  What about http://mvnrepository.com/artifact/com.sun.media/jai_imageio ?
  
  — John
  
  On 30 Oct 2014, at 13:31, John Hewson j...@biblific.com wrote:
  
  Am 30.10.2014 um 20:37 schrieb Andreas Lehmkuehler:
  Hi,
  
  Am 30.10.2014 um 20:29 schrieb Tilman Hausherr:
  Does anybody know a maven repository for jai_imageio? Currently we use
  http://repository.mygrid.org.uk/ but that site is getting very
  unreliable.
  Why do we use that specific version from mygrid?
  The problem isn't the version, the problem is the repository... we need a
  repository because we don't want to have that file permanently in the
  build for legal reason. So it is only temporarly loaded by maven for
  testing.
  
  In the meantime I found
  http://repo.spring.io/repo/com/sun/media/jai_imageio/
  but haven't tested it yet.
  
  Tilman
  
  Tilman
  BR
  Andreas Lehmkühler
 


Re: repository for jai_imageio

2014-10-31 Thread Andreas Lehmkühler


 Tilman Hausherr thaush...@t-online.de hat am 31. Oktober 2014 um 09:04
 geschrieben:
 
 
 Here's a possible solution
 http://sahits.ch/blog/blog/2011/03/28/java-advanced-imaging-with-maven/
 
 but I haven't tested it yet. Many of the poms from the repositories we 
 have seen, point to an URL that doesn't work.
Sounds promising!

BR
Andreas Lehmkühler


Re: download link broken

2014-10-22 Thread Andreas Lehmkühler
Hi,

I didn't do anything neither to break the download link nor to repair it. ;-)

I guess there was some hickup somewhere in the infrastructure 

BR
Andreas Lehmkühler

 Tilman Hausherr thaush...@t-online.de hat am 22. Oktober 2014 um 08:14
 geschrieben:


 Now it works.

 Tilman

 Am 21.10.2014 um 21:10 schrieb Tilman Hausherr:
  https://pdfbox.apache.org/download.cgi shows this:
 
  #!/bin/sh
  # Wrapper script around mirrors.cgi script
  # (we must change to that directory in order for python to pick up the
  #  python includes correctly)
  cd /www/www.apache.org/dyn/mirrors
  /www/www.apache.org/dyn/mirrors/mirrors.cgi $*
 
 



RE: 2.0

2014-10-22 Thread Andreas Lehmkühler
Hi Tim,

first of all thanks for the offer, this is highly appreciated!

I already have a first fix for PDFBOX-2441, but there is another issue. I hope
to fix it soon.

I'm just curious, do you run that comparisons manually or do you plan to
implement some more or less automatic test which can be started without that
much effort?

BR
Andreas Lehmkühler

 Allison, Timothy B. talli...@mitre.org hat am 21. Oktober 2014 um 22:19
 geschrieben:


 Hi Tilman,
   Sounds good.  Should I wait for PDFBOX-2441?

 -Original Message-
 From: Tilman Hausherr [mailto:thaush...@t-online.de]
 Sent: Tuesday, October 21, 2014 1:42 PM
 To: dev@pdfbox.apache.org
 Subject: Re: 2.0

 Hi Tim,

 2.0 doesn't seem to be released soon... what might be useful again is a
 comparison between seq v non-seq, Andreas recently resolved an issue
 (PDFBOX-2250) that improves the nonSeq parser a lot. Although this isn't
 fully done, a follow-up issue PDFBOX-2441
 https://issues.apache.org/jira/browse/PDFBOX-2441 has been opened
 which will improve a few more complex files.

 Tilman



 Am 21.10.2014 um 13:00 schrieb Allison, Timothy B.:
  Been too busy over in Tika-land...just noticing this now.
 
  Let me know which comparisons you'd like to run (2.0 v 1.8.x or seq v
  non-seq).  I won't have time to integrate 2.0 into our Tika PDFParser any
  time soon (Jeremy Anderson on TIKA-1285 has already started this), but I
  could easily write a lightweight wrapper around PDFBox's TextStripper +
  metadata inside of the tika-batch/tika-eval framework.
 
  Cheers,
 
         Tim
  
  From: Andreas Lehmkühler [andr...@lehmi.de]
  Sent: Wednesday, October 15, 2014 6:20 AM
  To: dev@pdfbox.apache.org
  Subject: Re: 2.0
 
  Hi,
 
 
  Maruan Sahyoun sahy...@fileaffairs.de hat am 15. Oktober 2014 um 09:32
  geschrieben:
 
 
  What about keeping both for the 2.0 release and phase the old one out for 3
  but making the NonSequential the default parser.
  Would also give us some time to work with Tim (TIKA) on the test suite.
  I agree, that's the only thing we can manage in a timely manner.
 
 
  Maybe we could simplify the variations of PDDocument.load to something like
 
  PDDocument.load(input, raf, enforce, useLegacyParser) or
  PDDocument.load(input, raf, enforce, withSignatureSupport) .
 
  and introduce PDDocument.load(input) to use the NonSequential
 
 
  WDYT?
  Good idea, I've already created PDFBOX-2430 for this.
 
  Maruan
 
  BR
  Andreas Lehmkühler
  Am 15.10.2014 um 09:18 schrieb Timo Boehme timo.boe...@ontochem.com:
 
  Hi,
 
  the difference between the parsers stems from the fact that the old parser
  can cope with a completely broken xref table because it uses the objects
  as
  it finds them on its sequential way. What we need (as I proposed before)
  is
  a repair mechanism scanning the file for object start/end to be used for
  re-creating the xref table.
  I will see if I can find some time to do this.
 
  The only other stopper is as Andreas has pointed out the signing. I'm not
  familiar with this and don't known what needs to be done here.
 
 
  Best,
  Timo
 
 
  Am 14.10.2014 um 21:18 schrieb Tilman Hausherr:
  Here are some:
 
  055/055794.pdf
  082/082463.pdf
  108/108362.pdf
  113/113223.pdf
  115/115458.pdf
  115/115463.pdf
  122/122393.pdf
  129/129416.pdf
  133/133423.pdf
  148/148020.pdf
  152/152012.pdf
  161/161466.pdf
 
  to be found here:
  http://digitalcorpora.org/corp/nps/files/govdocs1/zipfiles/
 
  Tilman
 
  Am 14.10.2014 um 21:06 schrieb John Hewson:
  Unless somebody provides us with a list of those files, then I think
  this is an unreasonable request. As long as we continue to leave the
  old parser in PDFBox, we won't get the bug reports which we need to
  fix the new parser, and the situation will never resolve itself.
  Falling back to the old parser is just as bad - we won't get bug
  reports.
 
  -- John
 
  On 14 Oct 2014, at 07:39, Tilman Hausherr thaush...@t-online.de wrote:
 
  I prefer that the old parser not be removed, because there are many
  files that can only be parsed by the old parser. This came out in a
  large scale test with TIKA.
 
  The best idea (in my current opinion) is to use the nonSeq parser
  first, and the old parser if there is an exception.
 
  Tilman
 
  Am 14.10.2014 um 09:45 schrieb Timo Boehme:
  Hi,
 
  Am 14.10.2014 um 07:22 schrieb John Hewson:
  Hi,
  John Hewson j...@jahewson.com hat am 10. Oktober 2014 um 20:05
  geschrieben:
 
 
           - Parsing (Andreas?)
  I guess we won't get a complete new parser in 2.0, but I try to
  improve the XRef
  and the COSStream stuff
  It would be great if we could get rid of the old parser and switch
  to the non-sequential
  parser, WDYT?
  I would also propose to completely remove the old parser. That way
  we are more flexible in parsing streams etc. since parts of the
  non-sequential parser are a compromise to work side-by-side with the
  old parser.
  Possibly there are a small

Re: AcroForms appearance generation and 1.8

2014-10-22 Thread Andreas Lehmkühler
Hi,

 Maruan Sahyoun sahy...@fileaffairs.de hat am 22. Oktober 2014 um 10:03
 geschrieben:


 Hi,

 I started making some adjustments to how the appearance is calculated for
 various field types for PDFBOX-2333. Although some of this could be made
 available to 1.8 if it doesn’t break the public API I’m not planning to do so.

 WDYT?
I agree, we shouldn't put to much new features/improvements into 1.8, so that
people don't feel to cosy using it instead of migrating to 2.0 once it's
available.

 BR
 Maruan

BR
Andreas Lehmkühler


Re: 2.0

2014-10-15 Thread Andreas Lehmkühler


 Timo Boehme timo.boe...@ontochem.com hat am 15. Oktober 2014 um 09:18
 geschrieben:


 Hi,

 the difference between the parsers stems from the fact that the old
 parser can cope with a completely broken xref table because it uses the
 objects as it finds them on its sequential way. What we need (as I
 proposed before) is a repair mechanism scanning the file for object
 start/end to be used for re-creating the xref table.
 I will see if I can find some time to do this.
I already have a working prototype but I'm not yet happy with the
implementation.

 The only other stopper is as Andreas has pointed out the signing. I'm
 not familiar with this and don't known what needs to be done here.
Me neither.

 Best,
 Timo

BR
Andreas Lehmkühler

 Am 14.10.2014 um 21:18 schrieb Tilman Hausherr:
  Here are some:
 
  055/055794.pdf
  082/082463.pdf
  108/108362.pdf
  113/113223.pdf
  115/115458.pdf
  115/115463.pdf
  122/122393.pdf
  129/129416.pdf
  133/133423.pdf
  148/148020.pdf
  152/152012.pdf
  161/161466.pdf
 
  to be found here:
  http://digitalcorpora.org/corp/nps/files/govdocs1/zipfiles/
 
  Tilman
 
  Am 14.10.2014 um 21:06 schrieb John Hewson:
  Unless somebody provides us with a list of those files, then I think
  this is an unreasonable request. As long as we continue to leave the
  old parser in PDFBox, we won’t get the bug reports which we need to
  fix the new parser, and the situation will never resolve itself.
  Falling back to the old parser is just as bad - we won’t get bug reports.
 
  -- John
 
  On 14 Oct 2014, at 07:39, Tilman Hausherr thaush...@t-online.de wrote:
 
  I prefer that the old parser not be removed, because there are many
  files that can only be parsed by the old parser. This came out in a
  large scale test with TIKA.
 
  The best idea (in my current opinion) is to use the nonSeq parser
  first, and the old parser if there is an exception.
 
  Tilman
 
  Am 14.10.2014 um 09:45 schrieb Timo Boehme:
  Hi,
 
  Am 14.10.2014 um 07:22 schrieb John Hewson:
  Hi,
  John Hewson j...@jahewson.com hat am 10. Oktober 2014 um 20:05
  geschrieben:
 
 
          - Parsing (Andreas?)
  I guess we won't get a complete new parser in 2.0, but I try to
  improve the XRef
  and the COSStream stuff
  It would be great if we could get rid of the old parser and switch
  to the non-sequential
  parser, WDYT?
  I would also propose to completely remove the old parser. That way
  we are more flexible in parsing streams etc. since parts of the
  non-sequential parser are a compromise to work side-by-side with the
  old parser.
  Possibly there are a small number of functions for which the old
  parser is still needed - e.g. signing?
 
 
  Best,
  Timo
 
 
 
 


 --

   Timo Boehme
   OntoChem GmbH
   H.-Damerow-Str. 4
   06120 Halle/Saale
   T: +49 345 4780474
   F: +49 345 4780471
   timo.boe...@ontochem.com

 _

   OntoChem GmbH
   Geschäftsführer: Dr. Lutz Weber
   Sitz: Halle / Saale
   Registergericht: Stendal
   Registernummer: HRB 215461
 _



<    1   2   3   4   >