I think this is good. I will throw one more in there since I have been asked this question many times. Why is jspc not a part of the maven war plugin? It seems that jsp compiling should be a component of packaging a war. I know you have said that not everyone wants to use the jasper compiler. My answer is its still a jsp compiled on the other side...and jasper will handle, and does handle 95%, of your use cases...and right now I don't see a maven plugin for other compilers that handle jsps. In other words, you can always add in other compilers.
Jeff Brett Porter wrote: > Some of the plugins that wound up in mojo seem better suited to the main > Apache project due to a) originally coming from there b) having the core > libraries located there c) being essential to the day to day use of the > project. > > These are the ones I'm thinking of: > - build helper > - jxr report (jxr) > - surefire report (surefire) > - changes/jira/announcement report (issue stuff in sandbox) > - changelog report (scm) > > What do others think? > > The other ones I'm tossing up: > - taglist (generally useful report) > - dependency-maven-plugin (sounds generally handy in eliminating a lot > of small antrunning - would need to investigate it more). > > Cheers, > Brett
