On 09/17/2014 11:30 PM, Tom Lane wrote:
> But here's the *key* reason: if pl/java is failing to stay afloat as
> an external project, that is a terrible reason for pulling it into
> core. It suggests strongly that the manpower or interest to keep it
> going simply doesn't exist.
This is really all that needs to be said, IMO. If it's not in core now,
after *several years* of existing in various states of completeness on
its own... it probably isn't going to be. If there can't be a solid
deployment process *independent* of whatever state Java is in at any
arbitrary moment, it has no business being in core.
This is clearly a third-party module effort, as are many on PGXN. That
is fine, honestly. What is wrong with something being an external
module? Why does everything, including the kitchen sink of Java, need to
be in core?
It sounds like Mr. Cowwoc has some kind of issue with the maintainers of
Pl/Java, and he should take it up with them.
--
Shaun Thomas
OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas@optionshouse.com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email