After looking at it today with a fresh set of eyes, the dependencies all
appear to be correct. The problem seems to be that in upgrading to maven 3
and maven eclipse plugin 2.9 the built JSPs aren't in a location where
eclipse wants them. When I run it in our production mode (i.e. outside of
ecli
Hi Jan and Jesse,
Sorry to take so long getting back to you on this, but I'm still having
problems and I just upgraded to jetty 7.6.3.v20120416. Basically, I
started over from scratch with our jetty dependencies, starting with
getting a "mvn dependency:tree" for just o.e.j.osgi.boot and
o.e.j.osg
Craig,
the jetty-jsp-2.1 module is not required (can't remember precisely
when, but it was a release or so ago).
Whilst the module jetty-jsp exists, it is now just a maven convenience
for gathering all jsp related dependencies in the one pom. If you're
using osgi, then you should probably be usin
Hi Jesse,
I reported some issues with JSP awhile back (I believe against 7.5.4) and
you had mentioned using the Orbit dependencies. I had tried that and it
didn't help, but I didn't have the time to look into it further. What's
the best way to test the latest and report problems? Get the source
Hi Jesse,
I reported some issues with JSP awhile back (I believe against 7.5.4) and
you had mentioned using the Orbit dependencies. I had tried that and it
didn't help, but I didn't have the time to look into it further. What's
the best way to test the latest and report problems? Get the source
We have pushed the 7.6.2.v20120308 and 8.1.2.v20120308 releases and
they are now available for download from maven central and the usual
eclipse and codehaus download locations.
We anticipate another release that will resolve a few lingering jsp
issues related to OSGI usage so if your an osgi user
