Pretty sure we got rid of embedded grizzly though, I'll take a look. The pre-compiling has always been fragile.
On Sat, Jan 18, 2014 at 9:58 AM, Dave <[email protected]> wrote: > Ah. I did not know that. Sounds like Jasig is the way to go. > > - Dave > > > > > On Sat, Jan 18, 2014 at 12:04 PM, Ed Anuff <[email protected]> wrote: > > > Is it actually viable to eliminate the JSP pre-compiler and still have > > those JSPs work? We were using embedded grizzly for the standalone and > > desktop versions and it couldn't load the JSP compiler at runtime so > > pre-compiling them was the solution. > > > > > > On Sat, Jan 18, 2014 at 6:11 AM, Dave <[email protected]> wrote: > > > > > On Sat, Jan 18, 2014 at 1:46 AM, Sungju Jin <[email protected] > > > >wrote: > > > > > > > We have a compile error on Java 7 on Mac. I know it's know issue. ( > > > > https://jira.codehaus.org/browse/MJSPC-53 ) > > > > > > > > > > I ran into that same tools.jar problem and solved it by creating a > > classes > > > directory and a symbolic link. > > > > > > > > > I think we should better replace the maven plugin module( > > > > org.codehaus.mojo.jspc -> jasig.mojo.jspc ) > > > > https://github.com/Jasig/jspc-maven-plugin > > > > > > > > > I think it is a very good idea to eliminate the tools.jar problem and > the > > > Jasig looks like a reasonable way to work around this bug in Java 7 on > > Mac. > > > > > > Another alternative is to remove the JSP pre-compiler entirely. We only > > > have a couple simple JSP pages so we're not gaining much with this > > plugin. > > > > > > - Dave > > > > > >
