> >
> > -1 We have code in other parts of PDFBox that should already be released.
> >
> >> 2 - Make the 1.7 release excluding the preflight module (and XMPBox ?) from
> >> the reactor pom. A Warning in the README.txt explains why the module isn't
> >> de
Hi,
Am 23.05.2012 23:17, schrieb Jukka Zitting:
Hi,
On Wed, May 23, 2012 at 11:03 PM, Leleu Eric wrote:
1 - Postpone the release until an unknown date.
-1 We have code in other parts of PDFBox that should already be released.
2 - Make the 1.7 release excluding the preflight module (and
Hi,
Am 23.05.2012 23:17, schrieb Jukka Zitting:
Hi,
On Wed, May 23, 2012 at 11:03 PM, Leleu Eric wrote:
1 - Postpone the release until an unknown date.
-1 We have code in other parts of PDFBox that should already be released.
2 - Make the 1.7 release excluding the preflight module (and
ase until an unknown date.
>>
>> -1 We have code in other parts of PDFBox that should already be released.
>>
>> > 2 - Make the 1.7 release excluding the preflight module (and XMPBox ?)
> from
>> > the reactor pom. A Warning in the README.txt explains why the
> -1 We have code in other parts of PDFBox that should already be released.
>
> > 2 - Make the 1.7 release excluding the preflight module (and XMPBox ?)
from
> > the reactor pom. A Warning in the README.txt explains why the module
isn't
> > deployed in 1.7.
>
>
Hi,
On Wed, May 23, 2012 at 11:03 PM, Leleu Eric wrote:
> 1 - Postpone the release until an unknown date.
-1 We have code in other parts of PDFBox that should already be released.
> 2 - Make the 1.7 release excluding the preflight module (and XMPBox ?) from
> the reactor pom. A Warni
Hi,
It seems that we have few choices :
1 - Postpone the release until an unknown date.
2 - Make the 1.7 release excluding the preflight module (and XMPBox ?) from
the reactor pom. A Warning in the README.txt explains why the module isn't
deployed in 1.7.
3 - Make the 1.7 release incl
rsion will change the interface
* xmpbox and jempbox should be merged (or at least one should desappear).
The schedule with these modification is not compatible with 1.7 release.
Guillaume
On Tue, May 22, 2012 at 9:19 PM, Leleu Eric wrote:
Hi,
2012/5/22 Andreas Lehmkuehler
Hi,
Am 21.05.20
han one issue linked with that:
> * Eric's new version will change the interface
> * xmpbox and jempbox should be merged (or at least one should desappear).
>
>
> The schedule with these modification is not compatible with 1.7 release.
>
>
> Guillaume
>
one issue linked with that:
* Eric's new version will change the interface
* xmpbox and jempbox should be merged (or at least one should desappear).
The schedule with these modification is not compatible with 1.7 release.
Guillaume
On Tue, May 22, 2012 at 9:19 PM, Leleu Eric wrote:
mm, last minute timing I planned to cut the release now.
>
>
I'm sorry :(
>
> The "new" preflight implementation will be more flexible and configurable.
>> But it will have significant impact on the current implementation. (New
>> interface, new way
Hi,
Am 20.05.2012 18:46, schrieb Andreas Lehmkuehler:
Am 13.05.2012 10:24, schrieb Andreas Lehmkuehler:
.
I'll volunteer as RM for the next release. What do you think about cutting the
release in one week from now on 22th? As I won't be available in the first 2
weeks of june the next reaso
on will be more flexible and configurable.
But it will have significant impact on the current implementation. (New
interface, new way to load/validate the pdf...)
Due to the 1.7 release that is coming soon, we would like to know how we
should commit the preflight modifications without "br
Hi,
On Tue, May 22, 2012 at 8:40 AM, Jukka Zitting wrote:
> I just realized that there are some related changes in Tika that I
> should port to the parser class we now have in PDFBox. I'll take care
> of that within the next few hours.
I'm done with this, so +1 to proceeding with the release.
I
Hi Andreas,
On Sun, May 20, 2012 at 6:46 PM, Andreas Lehmkuehler wrote:
> As there weren't any objections, I'll cut the release in 2 days on tuesday
> the 22th unless something (unexpected) comes up in the meantime.
I just realized that there are some related changes in Tika that I
should port t
interface, new way to load/validate the pdf...)
Due to the 1.7 release that is coming soon, we would like to know how we
should commit the preflight modifications without "breaking" the 1.7
release.
Here is 3 possibilities :
1 - Exclude the preflight module from the release and work w
Am 13.05.2012 10:24, schrieb Andreas Lehmkuehler:
.
I'll volunteer as RM for the next release. What do you think about cutting the
release in one week from now on 22th? As I won't be available in the first 2
weeks of june the next reasonable target date could be june 26th, if we need
some mo
Am 14.05.2012 10:11, schrieb Maruan Sahyoun:
...
WRT 1.7 I agree with Timo that the enhancements made so far do
validate a new release esp the new NonSequentialParser Timo created
has already proven to solve a number of issues raised. Maybe this
could be the default for the time being?
I wouldn
the new parser is - unfortunately - still in it's early state and not in any
way helpful. I wanted to complete the SimpleParser, which takes the tokens from
the PDF Lexer and creates the COS level objects this week. All this is still in
preparation for the ConformingParser.
WRT 1.7 I agree with
Hi,
Am 13.05.2012 10:24, schrieb Andreas Lehmkuehler:
Am 07.05.2012 10:50, schrieb Timo Boehme:
...
In my opinion there are already a number of improvements in current trunk
compared to 1.6 and there is no reason to not release another 1.8 before
PDFBOX-1000 is really ready. As I see it we sho
Hi,
Am 07.05.2012 10:50, schrieb Timo Boehme:
Hi,
Am 06.05.2012 16:46, schrieb Andreas Lehmkuehler:
Am 04.05.2012 15:46, schrieb Timo Boehme:
Am 03.05.2012 21:04, schrieb Michael McCandless:
Any guestimates for a 1.7.0 release?
It's been a long time (9 months) since 1.6.0... and I count ~20
On Mon, May 7, 2012 at 4:50 AM, Timo Boehme wrote:
> In my opinion there are already a number of improvements in current trunk
> compared to 1.6
+1
> and there is no reason to not release another 1.8 before
> PDFBOX-1000 is really ready. As I see it we should bump the version to 2.0
> if PDFBOX
Hi,
Am 06.05.2012 16:46, schrieb Andreas Lehmkuehler:
Am 04.05.2012 15:46, schrieb Timo Boehme:
Am 03.05.2012 21:04, schrieb Michael McCandless:
Any guestimates for a 1.7.0 release?
It's been a long time (9 months) since 1.6.0... and I count ~203
commits since 1.6.0.
There was already some
Before integrating the current work at PDFBOX-1000 I would prefer to
- make sure the lexer is using the new IO classes
- move some parts to the (new) SimpleParser as e.g. some keywords are already
handled in the lexer which is more than the lexer should do imo
regards
Maruan
Am 06.05.2012 um
Hi,
Am 04.05.2012 15:46, schrieb Timo Boehme:
Am 03.05.2012 21:04, schrieb Michael McCandless:
Any guestimates for a 1.7.0 release?
It's been a long time (9 months) since 1.6.0... and I count ~203
commits since 1.6.0.
There was already some discussion about it (see "Re: Next release(s)?" dat
On Fri, May 4, 2012 at 9:46 AM, Timo Boehme wrote:
> Am 03.05.2012 21:04, schrieb Michael McCandless:
>
>> Any guestimates for a 1.7.0 release?
>>
>> It's been a long time (9 months) since 1.6.0... and I count ~203
>> commits since 1.6.0.
>
> There was already some discussion about it (see "Re: Ne
Am 03.05.2012 21:04, schrieb Michael McCandless:
Any guestimates for a 1.7.0 release?
It's been a long time (9 months) since 1.6.0... and I count ~203
commits since 1.6.0.
There was already some discussion about it (see "Re: Next release(s)?"
dating from 2012-04-10) and it is clear that a new
Any guestimates for a 1.7.0 release?
It's been a long time (9 months) since 1.6.0... and I count ~203
commits since 1.6.0.
Mike McCandless
http://blog.mikemccandless.com
28 matches
Mail list logo
