Re: [Pljava-dev] PL/Java build/installation rework ready to merge

From: Chapman Flack <chap(at)anastigmatix(dot)net>
To:
Subject: Re: [Pljava-dev] PL/Java build/installation rework ready to merge
Date: 2015-12-19 20:09:30
Message-ID: 5675B97A.7020709@anastigmatix.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pljava-dev

On 12/19/15 11:59, Chapman Flack wrote:

> - issue 75 - probably a real bug, probably not hard to fix.

I meant #65.

> - declare a source file encoding in the pom.xml; Maven warns if it isn't
> set, and anyone _using_ PL/Java can now learn how to set it from our
> documentation, so it's just a matter of taking our own medicine. I've
> checked: UTF-8 covers all current source files.
>
> - rename the packaging subproject to pljava-packaging as proposed on this
> list http://lists.pgfoundry.org/pipermail/pljava-dev/2015/002355.html
> All the other modules have a pljava- prefix and that seems good, as the
> Maven repository namespace is org.postgresql, which has to be shared
> with pgjdbc. (Will require chasing down references in the docs.)
>
> - remove msvc-build-notes.txt (there's a whole MSVC section in the new docs)
>
> - add notes to Deployer and install.sql that they are now unnecessary,
> redirecting to the current installation docs.
>
> - add support for 9.1+ CREATE EXTENSION so it is also
> a workable way to intall. (No longer that much easier than installing
> without it, but would have the benefit of familiarity.)
>
> - Rototill the sources changing PGSQL_*_VER conditionals to use
> PG_VERSION_NUM directly. It appeared in PG 8.2 and we are not trying
> to support earlier versions. I earlier simplified the build process to
> depend on PG_VERSION_NUM anyway, but found that #include order in some
> files made that error prone. It will be safer and more readable to just
> make the change throughout.
>
> - Add COMMENT ON in the code that creates the sqlj schema and objects in it.
> Not a big deal, but seems a bit unpolished to have no comments on those
> objects.
>
> - scour the wiki content for the most obviously obsolete info, version
> references to PG 8.0.3 and Java 1.4, etc., which can be replaced with
> links to the /one/ page of version targets in the new docs. Not the
> time for a significant rewrite of anything in there, just removal of
> obvious wrong info.
>
> - same for the historical documents in the docs/ subdirectory.
>
> - Release notes would be good. 1.4.3 came out in September 2011.
> There's a lot to talk about since then.
>
> - I propose some annotation keyword changes, as I think 1.5.0 will be
> the first numbered release featuring the annotation support, so there
> will probably never be a better time to improve some keywords if
> appropriate. I'll compose a separate e-mail about that.
>
> Comments and suggestions about this list of things welcome.
_______________________________________________
Pljava-dev mailing list
Pljava-dev(at)lists(dot)pgfoundry(dot)org
http://lists.pgfoundry.org/mailman/listinfo/pljava-dev

In response to

Browse pljava-dev by date

  From Date Subject
Next Message Peter Henderson 2015-12-21 01:11:31 Re: [Pljava-dev] annotation keyword changes before 1.5.0 (?)
Previous Message Chapman Flack 2015-12-19 17:56:39 [Pljava-dev] annotation keyword changes before 1.5.0 (?)