On Sat, 2008-03-01 at 19:41 +0100, [EMAIL PROTECTED] wrote: > > - For Web apps, do not forget to compile the JSPs into .class files and > > include those in the analysis to get the real picture. > > Oooh! Oookay! No, I didn't do that yet. That's still on my list to do. > Which plugin to use for that? > This one: http://mojo.codehaus.org/jspc-maven-plugin/usage.html ? >
I have had this one to work, even though it is very pedantic about the JSP syntax (and I didn't take the time to investigate how to configure it to be more lax...) > I haven't included it yet, as it seems to be complicated / weird - Nah, it is very straightforward. > If I got it right you need a "jspweb.xml"?! and you need to adjust your > web.xml?! I would like to integrate new plugins with no adjustments to the > application itself - for two reasons - > a) political, "don't change the app while moving to mvn2" > b) I neither like a requirement to have to touch (botch) an otherwise > perfectly working application just to make it's deployment work > If you have a web.xml, that should be enough. You do not need to touch it (unless you want to start packaging the precompiled JSPs in your final war and define the servlet-mappings generated by the plugin) > Any ideas / alternatives on this? > > p.s.: When I created class files from my jsps - do I have to adjust > configuration so that dependency:analyze also analyzes those? Maybe you got > some example? > By default, the .class files it generates will be included in the analysis. -Olivier --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
