From: ch at lathspell.de (Christian Hammers) Date: Mon, 11 Feb 2013 15:46:34 +0100 Subject: [Pljava-dev] Building pljava.so with maven-nar-plugin? In-Reply-To: <5118873A.1090802@tada.se> References: <20130111204013.00e19939@james.intern> <20130112234738.03b606b1@james.intern> <50F29266.5070408@tada.se> <50F29372.7080808@tada.se> <20130206023102.1b94cc01@james.intern> <51120BE7.6020109@tada.se> <20130207170645.080294f4@james.intern> <20130208015920.58709bae@james.intern> <20130211034102.740dcda8@james.intern> <5118873A.1090802@tada.se> Message-ID: <20130211154634.0b906b8d@james.intern> Hi I just did so! I noticed tough that your repository still has a module "pljava" with uncompilable Java sources. It seems that I based my repo on the Hellblazer fork. It's propably better if you go through his commits and apply them one by one as they contain lots of code changes. bye, -christian- Am Mon, 11 Feb 2013 06:52:58 +0100 schrieb Thomas Hallgren : > Hi Christian, > > Please submit a pull-request whenever you're happy with it. > > - thomas > > On 2013-02-11 03:41, Christian Hammers wrote: > > Hello > > > > My fork (see last mail) has been improved and now calls an ant task > > that converts the pg_config output to a properties file which gets > > then read by the Maven pom.xml. So no hardcoded version numbers > > anymore. > > > > "sudo mvn deploy" inside the pljava-so/ directoy now copies the > > generated library to /usr/lib/postgres/.../pljava.so. > > > > bye, > > > > -christian- > > > > _______________________________________________ > > Pljava-dev mailing list > > Pljava-dev at pgfoundry.org > > http://lists.pgfoundry.org/mailman/listinfo/pljava-dev > > _______________________________________________ > Pljava-dev mailing list > Pljava-dev at pgfoundry.org > http://lists.pgfoundry.org/mailman/listinfo/pljava-dev