Good luck Matt. I was deep into reading the jasper Jspc code and the JspcMojo from the plugin. Doesn't make much sense to me why it isn't working. Like I said, it looked like it was possibly something after the class files were generated.
On Mon, Dec 7, 2015 at 7:55 AM, Matt Gilman <[email protected]> wrote: > Those other JSPs are only excluded because we filter version numbers (using > maven filtering capabilities) into the path of some resources to attempt to > bust browser caches. The JSP in question does not pull in any of those > resources so it does not need to be filtered and can be pre-compiled. This > is also true for all the JSPs in src/main/webapp/WEB-INF/partials. > > I'll spend a little bit this morning trying to figure out why. If I'm > unable to, I'll go ahead with the proposed change as it only affects when > the page is compiled. > > Matt > > On Sun, Dec 6, 2015 at 11:49 PM, Tony Kurc <[email protected]> wrote: > > > I tested on CentOS 6.7 and Fedora 23. Both worked with the above change. > > Not sure why. @Matt Gilman - the plugin makes the same source code and > > seemingly the same class files on those systems. I'm a bit bamboozled, so > > if you know what might have caused this, I'd be interested to hear. I > > noticed the other jsps from src/main/webapp/WEB-INF/pages were excluded, > so > > I figured that had something to do with it. > > >
