When it's more work to open the issue than fix it, just fix it. :)
On Tue, Jun 2, 2015 at 7:57 PM, Mike Kienenberger mkien...@gmail.com
wrote:
Do you think we need to open issues for trivial obviously-broken build
issues like this?
I'm going to guess no.
On Tue, Jun 2, 2015 at 10:56 PM,
My maven knowledge is tragically small.
Do we need to make the following change for the 1.x pom.xml?
Index: pom.xml
===
--- pom.xml(revision 1683209)
+++ pom.xml(working copy)
@@ -33,7 +33,7 @@
Do you think we need to open issues for trivial obviously-broken build
issues like this?
I'm going to guess no.
On Tue, Jun 2, 2015 at 10:56 PM, Sergiu Dumitriu
sergiu.dumit...@gmail.com wrote:
1.7 is definitely wrong, since a non -SNAPSHOT version should only be
present in a tagged release.
1.7 is definitely wrong, since a non -SNAPSHOT version should only be
present in a tagged release. So yes, that needs to be changed.
On 06/02/2015 10:52 PM, Mike Kienenberger wrote:
My maven knowledge is tragically small.
Do we need to make the following change for the 1.x pom.xml?
Index:
