Find an alternative way to install the pljava.so in /usr/lib about pljava HOT 5 CLOSED

Hello

You're right, I forgot that there is more than just the default lifecycle:

http://maven.apache.org/ref/3.0.4/maven-core/lifecycles.html#site_Lifecycle

In our case copying the file to /usr should probably go to the "site-deploy"
phase.

bye,

-christian-

On Fri, 22 Feb 2013 01:48:24 -0800
Thomas Hallgren [email protected] wrote:

The pom.xml file of the pljava-so project contains some code that performs a copy of the pljava.so into it's final destination in /usr/lib (or /usr/lib64). It executes during the deploy phase which is unfortunate since that phase normally uploads the artifact to its remote repository.

The declaration has been commented out (by me) since it prevents the actual deploy phase from performing the upload. It also required root privileges to run. We need to find an alternative approach to installing that file under /usr.

@tada/pl-java-contributors

---

Reply to this email directly or view it on GitHub:
#6

Network Engineering & Design; Content Delivery Platform & IP

NETCOLOGNE Gesellschaft für Telekommunikation mbH
Am Coloneum 9 | 50829 Köln
Tel: 0221 2222-8711 | Fax: 0221 2222-78711
www.netcologne.de

Geschäftsführer:
Dr. Hans Konle (Sprecher)
Dipl.-Ing. Karl-Heinz Zankel
HRB 25580, AG Köln

Diese Nachricht (inklusive aller Anhänge) ist vertraulich. Sollten Sie diese
Nachricht versehentlich erhalten haben, bitten wir, den Absender (durch
Antwort-E-Mail) hiervon unverzüglich zu informieren und die Nachricht zu
löschen. Die E-Mail darf in diesem Fall weder vervielfältigt noch in anderer
Weise verwendet werden.

from pljava.

Hello,

First, thanks for getting this project updated. I'm trying to install on RHEL 6.3/postgresql 9.2.

I'm no maven expert but the site:site-deploy goal is for packaging and/or copying documentation generated by site:site. i.e it is not a place to emulate 'make install'.
I think it' s ok, and likely preferable, to leave this task out of the maven pom entirely. Maven builds and deploys the artifacts to a repository where some other toolchain can download and deploy them to a runtime system.

Maybe a related effort to build installation script(s) and/or packages would be useful? For instance, I tried my hand at a pljava-1.4.3 rpm package for postgresql 9.1 which worked nicely in my proscribed environment on AWS (meaning it would take some effort to make generally useful). It installed files, modified postgresql.conf, etc and included the bits needed to run CREATE EXTENSION.

--marty

from pljava.

We might indeed need site-deploy to update Javadoc and source code .zip files on our web page somewhen so maybe banning "make install" to an Ant build.xml is not the baddest idea.

from pljava.

"Maybe a related effort to build installation script(s) and/or packages would be useful?"

Yes, such an effort would indeed be very useful. Can you please open a separate issue for that where you outline what you think is needed?

from pljava.

yes, I will open an issue for installation-related discussion. I'm gathering initial thoughts now ...

from pljava.