1.8-SNAPSHOT as version for 1.x pom.xml?

2015-06-02 Thread Mike Kienenberger
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 @@ org.apache.velocity veloc

Re: 1.8-SNAPSHOT as version for 1.x pom.xml?

2015-06-02 Thread Sergiu Dumitriu
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:

Re: 1.8-SNAPSHOT as version for 1.x pom.xml?

2015-06-02 Thread Mike Kienenberger
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 wrote: > 1.7 is definitely wrong, since a non -SNAPSHOT version should only be > present in a tagged release. So yes, that needs to be

Re: 1.8-SNAPSHOT as version for 1.x pom.xml?

2015-06-02 Thread Sergiu Dumitriu
+1 for no. On 06/02/2015 10:57 PM, Mike Kienenberger 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, Sergiu Dumitriu > wrote: >> 1.7 is definitely wrong, since a non -SNAPSHOT ver

Re: 1.8-SNAPSHOT as version for 1.x pom.xml?

2015-06-03 Thread Nathan Bubna
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 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, Sergiu Dumitriu