Mark Stephens

Mark Stephens has been working with Java and PDF since 1999 and has diversified into HTML5, SVG and JavaFX.

He also enjoys speaking at conferences and has been a Speaker at user groups, Business of Software, Seybold and JavaOne conferences. He has a very dry sense of humor and an MA in Medieval History for which he has not yet found a practical use.

Java PDF library daily builds on Customer page

40 sec read

We generally have a monthly update cycle which works well. Every change is regression tested on our servers by a batch of tests and before every release we do lots of hand testing as well on our Java PDF library. This gives a nice balance between having a stable, tested version and having access to the latest.

Sometimes, however, this is not a perfect fit. We often fix issues for clients and they want to test the fix or need immediate access to the hotfix. Or we are adding a feature for a client and want to get some feedback on what they think. They need access to the latest build of our Java PDF library

So what we have done is to add a daily build to the customer page (you will need a login/password) to access it. This will be updated more or less every day and provides an easy access point to get the daily build. We still generally recommend that you use the monthly release but you can now have the best of both worlds if you want to test the latest.

Is this useful?

Mark Stephens

Mark Stephens has been working with Java and PDF since 1999 and has diversified into HTML5, SVG and JavaFX.

He also enjoys speaking at conferences and has been a Speaker at user groups, Business of Software, Seybold and JavaOne conferences. He has a very dry sense of humor and an MA in Medieval History for which he has not yet found a practical use.

4 Replies to “Java PDF library daily builds on Customer page”

      1. A maven repository doesn’t really need maven to be involved in the build. You just need to upload the built jar to a maven repository. You can either use a maven repository application like Nexus to host your repository or use a static repository just served by apache.

        http://knol.google.com/k/massimiliano-marcon/how-to-configure-a-simple-maven/3p1ffq33blj07/1# explains how to do the latter, but I don’t know how well it works or if it makes much sense if you don’t already have much experience with Maven.

        I currently have a script that downloads a daily build of jpedal and uploads it to our internal repository, along with a pom file to specify dependencies, when we need an updated build, which works pretty well for me.

Leave a Reply

Your email address will not be published. Required fields are marked *