Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement cleaner builder API for PDF rendering. #14

Closed
danfickle opened this issue Mar 27, 2016 · 1 comment
Closed

Implement cleaner builder API for PDF rendering. #14

danfickle opened this issue Mar 27, 2016 · 1 comment

Comments

@danfickle
Copy link
Owner

No description provided.

danfickle added a commit that referenced this issue Mar 27, 2016
Examples in readme for fluent api and pluggable HTTP client - #13
@danfickle
Copy link
Owner Author

The complete API with documentation is available in the source at PdfRendererBuilder

burka pushed a commit to burka/openhtmltopdf that referenced this issue Apr 26, 2024
As it's now, the artifacts from the dev releases overwrite the properly
released ones. Hence, we're switching to using the commit SHA as the
artifact version and release version.

It's also unnecessary and confusing to create proper GitHub releases for
the dev ones, where the point is merely to have the artifacts published
and available for local downstream development.

I don't think we have landed a versioning scheme nor proper release
process, so I'm not sure whether we should stick to using SHA version
for the released versions, but that's more a part of the danfickle#13 discussion.

The flatten plugin is required for using this property-based versioning
in a multi-module project. Without it, the version in the subproject
won't be replaced with the property.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant