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.
Sounds like a reasonable solution as preflight wasn't yet
Hi,
Am 23.05.2012 23:17, schrieb Jukka Zitting:
Hi,
On Wed, May 23, 2012 at 11:03 PM, Leleu Ericeric.leleu@gmail.com 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
in the pdfbox-reactor
pom file.
Doing this, the source code will be present in the tagged version, but they
will not have preflight jar in the repository with the version 1.7.
It's may not be the best way to achieve that but it is probably the easiest
way...
2 - Include the preflight module in the 1.7
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 including
Hi,
On Wed, May 23, 2012 at 11:03 PM, Leleu Eric eric.leleu@gmail.com 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
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 Warning in the README.txt explains why the module
isn't
deployed in 1.7.
Sounds like
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 Warning in the README.txt explains why the module
isn't
deployed in 1.7.
Sounds like
.
Here is 3 possibilities :
1 - Exclude the preflight module from the release and work with the current
code without compatibility with the old version.
Any suggestions how to do that easily?
2 - Include the preflight module in the 1.7 release, the new implementation
will be create in new
the easiest
way...
2 - Include the preflight module in the 1.7 release, the new
implementation
will be create in new packages. They will have no more modifications of
the
old implementation that will be marked as deprecated. Expect bug fix
nothing will be done on old version, only new
way...
2 - Include the preflight module in the 1.7 release, the new
implementation
will be create in new packages. They will have no more modifications of
the
old implementation that will be marked as deprecated. Expect bug fix
nothing will be done on old version, only new implementation
without compatibility with the old version.
2 - Include the preflight module in the 1.7 release, the new implementation
will be create in new packages. They will have no more modifications of the
old implementation that will be marked as deprecated. Expect bug fix
nothing will be done on old version
11 matches
Mail list logo