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

Prune doc references to unsupported PG versions #505

Merged
merged 2 commits into from
Oct 20, 2024

Conversation

jcflack
Copy link
Contributor

@jcflack jcflack commented Oct 6, 2024

17b7d7c (PR #450) dropped conditional code for PostgreSQL before 9.5, the oldest version to be supported by PL/Java 1.6.x. References to older PostgreSQL versions in the docs, however, were not pruned then. Remove those now.

The docs also mentioned some paths and other details that changed with the new build system in 1.6; bring those up to date. Also, link to the page on pljava.policy from a couple more places that only touched on policy generally. These changes are not strictly about pre-9.5 PostgreSQL versions, but are details that were similarly overlooked in the PL/Java 1.5 to 1.6 transition.

jcflack added 2 commits April 11, 2024 17:39
17b7d7c (PR #450) dropped conditional code for PostgreSQL
before 9.5, the oldest version to be supported by PL/Java 1.6.x.
References to older PostgreSQL versions in the docs, however,
were not pruned then. Remove those now.

The docs also mentioned some paths and other details that changed
with the new build system in 1.6; bring those up to date. Also,
link to the page on pljava.policy from a couple more places that
only touched on policy generally. These changes are not strictly
about pre-9.5 PostgreSQL versions, but are details that were
similarly overlooked in the PL/Java 1.5 to 1.6 transition.
The build system introduced in 1.6 fixed the "Windows might
get -Dpljava.libjvmdefault wrong" issue. Also, by no longer
trying to capture compiler/linker messages and classify them,
it has fixed the "Not all [ERROR]s are errors" issue.

In 1.6, both the pljava and pljava-api jars must be present
in $SHAREDIR/pljava at runtime. So a package maintainer may
choose to include the API jar additionally in a -devel package
that places it where users' development tools will expect, but
may not omit it from the base package that installs it where
the runtime needs it.
@jcflack jcflack merged commit 2fd5391 into REL1_6_STABLE Oct 20, 2024
10 checks passed
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

Successfully merging this pull request may close these issues.

1 participant