"mvn eclipse:eclipse" do not give JSP-support in jetty project

Thorbjørn,

AFAIK, the eclipse plugin should generate eclipse build path entries for all of your dependencies. So, if you have a dependency for the jsp-api-2.1 with <scope>provided</scope>, then that should show up in the eclipse build path.

That won't allow you to compile jsps when running Jetty via a Main class, so you'd need to also have a dependency for the jsp-2.1 jar with <scope>runtime</scope>. If you've already got those dependencies on your project, but the eclipse plugin isn't generating build-path entries for them, then I think you need to raise a bug over on the Maven issue tracker.

cheers
Jan

I may not have been clear enough. I have run "mvn eclipse:eclipse in the unpacked jetty source tree, not my own code, to get Eclipse up and running on the distribution quickly.

It is the resulting projects from this, that I have noticed that the "jsp-2.1" project is not in the "jetty" project build path (to get JSP compilation at runtime, not the API).

Thorbjørn,

If you do "mvn eclipse:eclipse" at the top level of the jetty project, then the individual submodules will generate eclipse project files. You can then import each module you want into eclipse. The jsp-2.1 and jsp-api-2.1 subprojects are definintely importable into eclipse. I'm not sure what "jetty" project build path you're referring to - if you mean the eclipse project generated from modules/jetty, then it is correct that no jsp jars are on it's build path, as jsp is not required to build that submodule.

If you've got an eclipse project that you'd like to use with jetty, and you've already got jetty in eclipse, then you can select whichever jetty sub-projects you need on your classpath. A minimum is jetty, jetty-util and servlet-api-2.5. If you want to do jsp compilation at runtime, then you'll either need jsp-2.0 or jsp-2.1 and their respective api modules as well.

cheers
Jan

Please reopen if you have further comments to make.
cheers
Jan