Am 20.08.2017 um 16:01 schrieb Andreas Lehmkuehler:
Am 20.08.2017 um 15:49 schrieb Maruan Sahyoun:
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?
Both strategies have their advantages/disadvantages. An independent
source tree
gives us the following advantages:
- cut independent releases of both jbig2 and PDFBox
- cut a first jbig2 apache release right after the integration
without waiting
for the 3.0 release of PDFBox
I'd go for an independent release. If we release inbetween we can
always update the dependency in pdfbox. And we don't add a timing
dependency for jbig2 on pdfbox where there isn't one.
Could we potentially have jbig2 in a git repo. Might be easier as the
current active developers are used to working with git.
Should be possible. I have to check if we have to have a svn repo
first to be moved or if we can just ask for an empty repo and add the
source after that.
I hate git, but maybe this could bring the advantage that we could
import the entire existing versioning?
Tilman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
