From: | "Markus KARG" <markus(at)headcrashing(dot)eu> |
---|---|
To: | "'List'" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: [pgjdbc] chore: migrate the build to Maven (#322) |
Date: | 2015-06-20 20:07:34 |
Message-ID: | 004801d0ab94$bf8a5d50$3e9f17f0$@eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
If the ANT build uses a properties file to adapt the build to the needs of the local user, we can copy that behaviour in Maven using the exact same file, see this Stack Overflow posting: http://stackoverflow.com/questions/7144620/reading-properties-file-from-maven-pom-file.
From: Vladimir Sitnikov [mailto:notifications(at)github(dot)com]
Sent: Samstag, 20. Juni 2015 15:18
To: pgjdbc/pgjdbc
Cc: Markus KARG
Subject: Re: [pgjdbc] chore: migrate the build to Maven (#322)
Yes, IMO changing the coords is a non-starter this would affect many
automated builds,
I completely forgot the pgjdbc already has maven coordinates. Shame on me.
Build properties are within pom.xml so additional files not really needed now.
In fact, the name of the database I use for testing does not match test/test/test pattern. It was somewhat useful for me to have my local values in the build.local.properties, so I do not have to provide the exact values each time.
It needs to be confirmed as working but @davecramer <https://github.com/davecramer> already has a process for existing build.
Sure. Committers should pick a way of publishing that will work for them the best.
—
Reply to this email directly or view it on GitHub <https://github.com/pgjdbc/pgjdbc/pull/322#issuecomment-113768436> . <https://github.com/notifications/beacon/ABn3t7h_8pUjLEVy9pjAiLAA2EoP89fsks5oVV9qgaJpZM4FCDIg.gif>
From | Date | Subject | |
---|---|---|---|
Next Message | Markus KARG | 2015-06-20 20:11:20 | Re: [pgjdbc] Check code style via automated tool (#295) |
Previous Message | Markus KARG | 2015-06-20 16:59:05 | Re: [pgjdbc] chore: migrate the build to Maven (#322) |