Am 14.01.2018 um 15:22 schrieb Andreas Lehmkuehler:
Am 09.01.2018 um 22:56 schrieb Tilman Hausherr:
From what I see, the move from 1.7 was made just because "jdk6 is deprecated":
https://github.com/levigo/jbig2-imageio/commit/70778022d9a674de6a7114cf1d1b6168b1fc1fe2
However pdfbox 2.* supports jdk 1.6. Could we set the jbig2 plugin to 1.6 too?
It builds and tests when I change the pom.xml with 1.6. A search finds no "try
with resources" or "diamond operator".
I had this "idea" because of this issue:
https://issues.apache.org/jira/browse/PDFBOX-4059
This was a newbie who had trouble setting up his command line, but for some
untold reason he wanted to use 1.6 so he couldn't use the 2.0 version of the
plugin. He ended up using 1.6.4.
As long as there is no real need to change the minimum requirement we should
fall back to java 6, at least for the first apache version of the plugin, so
that we can use it in combination with PDFBox 2.0.x
There are some other points we have to discuss before releasing the plugin:
- what about a code formatter? Should we just use the pdfbox definitions or
should we define something different? How about using checkstyle?
- we are going to release a 3.0.0 version of the plugin which will lead to a
3.0-branch. What would be the next version for the trunk 3.1.x or 4.0.x?
I reconsidered my own question. Due to the fact that the ImageIO plugin API is
stable we don't have to create a separate branch. We can simply use 3.0.1-SNAPSHOT
Andreas
Andreas
Tilman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
