From: hal.hildebrand at me.com (Hal Hildebrand) Date: Sun, 13 Jan 2013 20:04:42 -0800 Subject: [Pljava-dev] Source code move to Git In-Reply-To: <50F3762E.7030500@2ndQuadrant.com> References: <50F27A01.2090003@tada.se> <50F2FAEA.6090809@tada.se> <2C6DA4B8-9C38-4AEF-97FA-BEDB1839861D@me.com> <50F3762E.7030500@2ndQuadrant.com> Message-ID: <8EBAEA33-06CB-4F2E-B7D3-D2F51474734C@me.com> You can execute anything from Maven using the exec maven plugin (http://mojo.codehaus.org/exec-maven-plugin/). There's a specialization for executing Ant, if that's useful (https://maven.apache.org/plugins/maven-antrun-plugin/). So, the mechanics of integrating Make aren't especially difficult. The bigger difficulty, from my POV, is setting up the environment correctly. Having done this a couple of times, it still seems like quite the chore to actually build the C portion of pl/java. I'm not sure if that's just inherent difficulty or if there's something that can be done to make the process painless. I'm guessing the former because that's the way C programs roll. In any event, however, it'll be easy to add a Maven module for building the C portion. I just didn't do it right off the bat because I wanted to get the Java portion squared away first, and the fact that I do most of my development on the Mac and I have had no luck getting pl/java to build on the Mac so I'll have to switch to Linux to get that portion squared away. On Jan 13, 2013, at 7:06 PM, Craig Ringer wrote: > On 01/14/2013 09:20 AM, Hal Hildebrand wrote: >> Okay, first pull request in. This is just the initial structural refactoring to a maven build, no source changes. >> >> Doesn't refactor src/test, doesn't refactor C. > > The builds use PGXS for the C code, and I think that's the right approach. Maybe we can run the pgxs makefiles from Maven? > -- > Craig Ringer http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services -------------- next part -------------- An HTML attachment was scrubbed... URL: