That TestPDFToImage is excluded by default makes sense for the reasons stated. I love the improvements you've made to it, though! I knew when I added it so many years ago that there had to be a better way to compare the images than I was doing, but I couldn't find it.
And it has been several years since I've been an active committer. It wasn't too long after the project came over from SourceForge to Apache that it was doing well enough that my employer didn't want to pay me for more work on it. And ... I didn't get to it much on my own time. Now, I built version 2.0.0 (trunk) to a JAR yesterday using ant. With a bit of manual fetching of dependencies, that worked pretty well. And maybe if I'd understood the maven actions within the ant build file better, I could have tweaked it to get it to do it automaticly. It really looks like it's very close to being correct. In January, I built version 1.8.8 to .Net using IKVM 7.4. Actually ... using my own fork of IKVM v7.4, not because I needed to add stuff to IKVM to get the build but because I needed it to run my subclassed PageDrawer later on. My fork is at https://github.com/BlackLocust/ikvm/tree/v7.4 and it really has minimal changes from standard IKVM 7.4. Because you have made so many rendering improvements in 2.0, I am working now on getting it to compile using IKVM. Subclassing PageDrawer is what's not supported ... so ... I'll be making more changes to my IKVM fork to be able to render in .Net. If there's interest in continuing to support the ant build, at least in the interest of the IKVM version, I would be happy to merge my build file changes back. On Fri, Mar 6, 2015 at 3:16 AM, Andreas Lehmkühler <andr...@lehmi.de> wrote: > Hi, > > > Daniel Wilson <williamstonconsult...@gmail.com> hat am 5. März 2015 um > 23:16 > > geschrieben: > > > > > > Yes, it is needed for IKVM. But I was just informed that the IKVM build > is > > considered an unsupported 3rd-party version. > As Tilman already said, there wasn't any descision to stop supporting it, > but as > none of the active committers uses .NET there wasn't any real support for > it. > Additionally we never shipped any official .NET binary. > > There was a proposal to include the IKVM build in maven but I'm still > waiting > for some answers and I didn't find some time to test it myself. > > > As far as I can tell, it is also needed for the TestPDFToImage junit > test. > > That is the testimage target in the ant build. > > > > Btw, I DID get the ant build to produce a working version of PDFBox > > yesterday. I simply needed to download the appropriate binaries from the > > maven repo. > We still have a jenkins ant build, which works well. > > Im just curious, as I build some unofficial .NET versions of PDFBox in the > past. > What PDFBox version did you build, 1.8.8 or trunk? What version of IKVM > did you > use? > > BR > Andreas Lehmkühler > > > > > On Thu, Mar 5, 2015 at 2:55 PM, Tilman Hausherr <thaush...@t-online.de> > > wrote: > > > > > I've never used it. > > > > > > Isn't it needed for the users of IKVM ? > > > > > > Tilman > > > > > > Am 05.03.2015 um 20:46 schrieb John Hewson: > > > > > >> Based on discussions on the users lists, it looks like our ant build > > >> doesn’t actually produce working builds of PDFBox. I think we should > remove > > >> the ant build in 2.0, we don’t need two build systems, and clearly > none of > > >> us are maintaining it. > > >> > > >> WDYT? > > >> > > >> — John > > >> > > >> > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org > > > For additional commands, e-mail: dev-h...@pdfbox.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org > For additional commands, e-mail: dev-h...@pdfbox.apache.org > >
