Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just converted one of our web projects from NetBeans ANT to Maven 2 in order to ease our dependency management, this has proved brilliant, however I didn’t realise that Maven will not test compile the JSP’s by default.
I found the JSPC maven plugin which does the compiling, but I don’t actually want the artefacts that it creates. I did think about using it with the ant task plugin to throw the built JSP’s away but wanted to hear if anyone else has another solution?
you can put this plugin call to separate maven profile – and call it when you need- on Hudson before deploy to test server -for example… And just mvn clean after…