0e22a6fa0228d8fc2dd5380acb60b4d823fb1232 in pdfbox-docs's branch
refs/heads/master from Maruan Sahyoun
[ https://gitbox.apache.org/repos/asf?p=pdfbox-docs.git;h=0e22a6fa ]
PDFBOX-5475: fix typo; closes #9
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/ja
not an abbreviation)
{{*Observed:* via. javadoc.io}}
{{*Expected:* via javadoc.io}}
Otherwise it looks great, thank you!
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.o
breviation)
{{*Observed:* via. javadoc.io}}
{{*Expected:* via javadoc.io}}
Otherwise it looks great, thank you!
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[V
ate Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https://issues.apache.org/jira/
[
https://issues.apache.org/jira/browse/PDFBOX-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573459#comment-17573459
]
Tilman Hausherr commented on PDFBOX-5475:
-
> Update Javadocs to latest 2.0.26 rele
for the effort!
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https://issues.apache.org/
ate Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https://issues.apache.org/jira/
43f616556e2ef21f24980cb79ab271fd97353b01 in pdfbox-docs's branch
refs/heads/master from Maruan Sahyoun
[ https://gitbox.apache.org/repos/asf?p=pdfbox-docs.git;h=43f61655 ]
PDFBOX-5475: mention javadoc.io
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/ja
ocs (javadoc.io)" ?
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https://iss
know if there are further
issues
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https:/
d30e695d51487953d5384d23a46128c35ab44622 in pdfbox-docs's branch
refs/heads/master from Maruan Sahyoun
[ https://gitbox.apache.org/repos/asf?p=pdfbox-docs.git;h=d30e695d ]
PDFBOX-5475: update documentation to build website to match new tooling
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apac
331632236eedeab4909a3d2dd119646750aa35dd in pdfbox-docs's branch
refs/heads/master from Maruan Sahyoun
[ https://gitbox.apache.org/repos/asf?p=pdfbox-docs.git;h=33163223 ]
PDFBOX-5475: use javadoc.io as a base for API docs; make URLs dynamic for
documentation
> Update Javadocs to latest 2.0.26 rele
. It seems they rely on the javadocs
which are released along with new versions. I can't see any reason not to use
it. But we should mentioned it on our website, so that users are not suprised
beeing redirected to somewhere else.
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.or
/doc/org.apache.pdfbox/pdfbox/2.0.26/index.html]
That service is also used e.g. by Apache Camel and would help us simplifying
the build as they depend on the -javadoc.jar only
> Update Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/ja
ate Javadocs to latest 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https://issues.apache.org/jira/
[
https://issues.apache.org/jira/browse/PDFBOX-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maruan Sahyoun reassigned PDFBOX-5475:
--
Assignee: Maruan Sahyoun
> Update Javadocs to latest 2.0.26 rele
est 2.0.26 release on
> pdfbox.apache.org/docs/[VERSION]/javadocs/
> --
>
> Key: PDFBOX-5475
> URL: https://issues.apache.org/jira/browse/PDFBOX-5475
>
James Daily created PDFBOX-5475:
---
Summary: Update Javadocs to latest 2.0.26 release on
pdfbox.apache.org/docs/[VERSION]/javadocs/
Key: PDFBOX-5475
URL: https://issues.apache.org/jira/browse/PDFBOX-5475
Am 17.04.22 um 20:25 schrieb Tilman Hausherr:
new regression tests results at
https://home.snafu.de/tilman/tmp/reports_pdfbox_2.0.25_vs_2.0.26.tar.xz
IMHO we're fine now!
Thanks for the fast re-test!
I'm going to cut the 2.0.26 release tomorrow
Andreas
Tilman
new regression tests results at
https://home.snafu.de/tilman/tmp/reports_pdfbox_2.0.25_vs_2.0.26.tar.xz
IMHO we're fine now!
Tilman
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail:
Am 15.04.2022 um 10:42 schrieb Tilman Hausherr:
Am 14.04.2022 um 08:59 schrieb Tilman Hausherr:
I will rerun the tests myself on the long weekend, if I have the time.
https://home.snafu.de/tilman/tmp/reports_pdfbox_2.0.25_vs_2.0.26.tar.xz
This time I looked at
Am 14.04.2022 um 08:59 schrieb Tilman Hausherr:
I will rerun the tests myself on the long weekend, if I have the time.
https://home.snafu.de/tilman/tmp/reports_pdfbox_2.0.25_vs_2.0.26.tar.xz
-
To unsubscribe, e-mail:
Am 14.04.2022 um 08:13 schrieb Andreas Lehmkuehler:
Cool, thanks for the feedback. I've set the ticket to resolved.
Do we need to re-run the tests?
BTW, what about PDFBOX-5394? Is there anything left to do? Do we have
to wait for the feedback of the user?
I've set that one to resolved.
I
Cool, thanks for the feedback. I've set the ticket to resolved.
Do we need to re-run the tests?
BTW, what about PDFBOX-5394? Is there anything left to do? Do we have to wait
for the feedback of the user?
Andreas
Am 13.04.22 um 08:29 schrieb Tilman Hausherr:
Yeah, PDFBOX-5413 fixes that one
Yeah, PDFBOX-5413 fixes that one as well.
Tilman
Am 12.04.2022 um 19:26 schrieb Tilman Hausherr:
Only one left: 7LRS5U6CAFMN2P6JPTZVNBUW6XOFYH4M.pdf .
There is some sort of problem with an incremental save, a part of the
multi-content stream is missing / has a new object number. Lets wait
Only one left: 7LRS5U6CAFMN2P6JPTZVNBUW6XOFYH4M.pdf .
There is some sort of problem with an incremental save, a part of the
multi-content stream is missing / has a new object number. Lets wait
whether it is related to PDFBOX-5413 .
(The other one, HOAZTST4E26NPA7HL72WCIVMNRQ3E4M5.pdf is an
Only
commoncrawl3/7L/7LRS5U6CAFMN2P6JPTZVNBUW6XOFYH4M
commoncrawl3/HO/HOAZTST4E26NPA7HL72WCIVMNRQ3E4M5
have a different text extraction
With the other two it's attachment file names or doc info.
Tilman
Am 12.04.2022 um 08:16 schrieb Tilman Hausherr:
After having looked at the content
After having looked at the content differences and trying to rule out
the /Names differences, there are 4 files with content in
TOP_10_MORE_IN_A that feel suspicious and IMHO need investigation.
commoncrawl3/7L/7LRS5U6CAFMN2P6JPTZVNBUW6XOFYH4M
govdocs1/365/365260.pdf
Thanks Tim!
Looks like there are 5 new exceptions left.
I'm going to check the first two ones
commoncrawl3/ZC/ZCY5MCL7KI6QXVMXUZ2AJKXICQIT4TL4
commoncrawl3/WY/WYPJNTD5KQNODSXWK4GABURXRTTD5P4H
The others are thrown within Jempbox
Andreas
Am 11.04.22 um 12:40 schrieb Tim Allison:
Yes. Sorry. That's my fault. I did something stupid in 2.3.0 and then
fixed it in 2.4.0-SNAPSHOT (TIKA-3711).
On Mon, Apr 11, 2022 at 1:35 PM Tilman Hausherr
wrote:
> Am 11.04.2022 um 12:40 schrieb Tim Allison:
>
> https://corpora.tika.apache.org/base/reports/tika-2.4-20220410.tgz
>
> Haven't
Am 11.04.2022 um 12:40 schrieb Tim Allison:
https://corpora.tika.apache.org/base/reports/tika-2.4-20220410.tgz
Haven't had a chance to review. Hot off the vm.
Thanks Tim!
I looked at govdocs1/198/198191.pdf , this one has "high: 1 |
quality.joboptions: 1" more in A. This is a name of a
https://corpora.tika.apache.org/base/reports/tika-2.4-20220410.tgz
Haven't had a chance to review. Hot off the vm.
On Sun, Apr 10, 2022 at 9:58 AM Tim Allison wrote:
>
> Will try to kick off today…first thing Monday morning (EDT) at the latest.
>
> On Sun, Apr 10, 2022 at 9:05 AM Andreas
Will try to kick off today…first thing Monday morning (EDT) at the latest.
On Sun, Apr 10, 2022 at 9:05 AM Andreas Lehmkuehler
wrote:
> Am 09.04.22 um 19:00 schrieb Tilman Hausherr:
> > testFlattenPDFBOX2469Filled also fails in 2.0 (it is disabled by
> default).
> I've fixed all new tickets.
Am 09.04.22 um 19:00 schrieb Tilman Hausherr:
testFlattenPDFBOX2469Filled also fails in 2.0 (it is disabled by default).
I've fixed all new tickets. PDFBOX-5413 fixes the issue with the disabled
flatten test.
@Tim Is there any chance to re-run the tests?
Andreas
testFlattenPDFBOX2469Filled also fails in 2.0 (it is disabled by default).
testFlattenPDFBOX2469Filled(org.apache.pdfbox.pdmodel.interactive.form.PDAcroFormFlattenTest)
Time elapsed: 1.083 s <<< ERROR!
java.io.IOException: javax.crypto.BadPaddingException: Given final block
not properly
to cut the 2.0.26 release next
Saturday, the
day after tomorrow, if nobody objects.
Andreas
P.S.: I'm targeting a new 3.0.0 alpha release once the 2.0.26 release is
out
-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
t; > Sounds great! Should I rerun the regression tests today?
> >
> > On Thu, Apr 7, 2022 at 1:41 AM Andreas Lehmkuehler wrote:
> >
> >> Hi,
> >>
> >> sorry for the delay. I'm planning to cut the 2.0.26 release next
> >> Saturday, t
Yes, please
Thanks in advance
Andreas
07.04.2022 11:44:38 Tim Allison :
> Sounds great! Should I rerun the regression tests today?
>
> On Thu, Apr 7, 2022 at 1:41 AM Andreas Lehmkuehler wrote:
>
>> Hi,
>>
>> sorry for the delay. I'm planning to cut the 2
Sounds great! Should I rerun the regression tests today?
On Thu, Apr 7, 2022 at 1:41 AM Andreas Lehmkuehler wrote:
> Hi,
>
> sorry for the delay. I'm planning to cut the 2.0.26 release next
> Saturday, the
> day after tomorrow, if nobody objects.
>
> Andreas
>
> P.S.
Hi,
sorry for the delay. I'm planning to cut the 2.0.26 release next Saturday, the
day after tomorrow, if nobody objects.
Andreas
P.S.: I'm targeting a new 3.0.0 alpha release once the 2.0.26 release is out
if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next Monday?
Andreas
from starting our next 1.x and 2.x releases on Tika, and it would be
great to incorporate 2.0.26. No problem at all if 2.0.26 is slated
for later
Tilman
Am 10.03.2022 um 19:05 schrieb Andreas Lehmkuehler:
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up
yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few
weeks out
How about
um 19:05 schrieb Andreas Lehmkuehler:
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next
et is quite new, but the issue itself was introduced in 2018 with
> >>>> 2.0.12. ;-)
> >>>>
> >>>> However, I'll have a look at the proposed solution.
> >>>>
> >>>> Andreas
> >>>>>
> >>>>> Til
out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next Monday?
Andreas
from starting our next 1.x and 2.x releases on Tika, and it would be
great
gt;>
> >>>
> >>>>
> >>>> WDYT?
> >>>>
> >>>> Andreas
> >>>>
> >>>>>
> >>>>> Tilman
> >>>>>
> >>>>> Am 10.03.2022 um 19:05 schrieb And
:05 schrieb Andreas Lehmkuehler:
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next
um 19:05 schrieb Andreas Lehmkuehler:
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release
t;>>
> >>> Am 10.03.2022 um 19:05 schrieb Andreas Lehmkuehler:
> >>>> Am 09.03.22 um 17:07 schrieb Tim Allison:
> >>>>> All,
> >>>>>
> >>>>> I've been out of the office for a bit and haven't caught up y
Tilman
WDYT?
Andreas
Tilman
Am 10.03.2022 um 19:05 schrieb Andreas Lehmkuehler:
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're
caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next Monday?
Andreas
from starting our next 1.x and 2.x releases on Tika, and it would be
great to incorporate 2.0.26. No problem at all
Allison:
> > > > All,
> > > >
> > > > I've been out of the office for a bit and haven't caught up
> > > > yet.
> > > > Apologies if I've missed the discussion.
> > > >
> > > > Are there plans for a 2.0.26 release?
schrieb Andreas Lehmkuehler:
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next Monday
for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next Monday?
Andreas
from starting our next 1.x and 2.x releases on Tika, and it would be
great to incorporate 2.0.26. No problem at all if 2.0.26 is slated
for later.
Thank you!
Cheers,
Tim
On Fri
Am 09.03.22 um 17:07 schrieb Tim Allison:
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
How about cutting the release next Monday?
Andreas
from starting
All,
I've been out of the office for a bit and haven't caught up yet.
Apologies if I've missed the discussion.
Are there plans for a 2.0.26 release? We're probably a few weeks out
from starting our next 1.x and 2.x releases on Tika, and it would be
great to incorporate 2.0.26. No problem
56 matches
Mail list logo