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 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,

Re: Fixing build issues in 1.x but not 2.x

2015-06-03 Thread Nathan Bubna
VELOCITY-862 would probably still apply to the 2.x branch, i suspect. Moving on with 1.8 sounds sensible to me. On Tue, Jun 2, 2015 at 7:46 PM, Mike Kienenberger mkien...@gmail.com wrote: I hope it's not a problem, but I'm only applying the build process fixes to the 1.x branch and not the

[jira] [Reopened] (VELOCITY-862) Rebuilding parser using javacc 4.1 loses Node import

2015-06-03 Thread Mike Kienenberger (JIRA)
[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened VELOCITY-862: Reopening at Nathan's suggestion that we may want to apply this to 2.x Rebuilding