[Bug 56952] Move JasperInitializer into separate jar

2014-09-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56952 --- Comment #4 from romain.manni-bucau --- Hi just for memories in TomEE we deactivate the default one to provide our own one: http://svn.apache.org/repos/asf/tomee/tomee/trunk/tomee/tomee-catalina/src/main/java/org/apache/tomee/jasper/Tom

[Bug 56952] Move JasperInitializer into separate jar

2014-09-15 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56952 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 56952] Move JasperInitializer into separate jar

2014-09-13 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56952 --- Comment #2 from Jan Bartel --- Hi Mark, I can totally understand that - I'm against jar proliferation in jetty too :). In fact, we created a feature for Jetty to define a pattern for SCIs to ignore for just this purpose. Just thought i

[Bug 56952] Move JasperInitializer into separate jar

2014-09-12 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56952 --- Comment #1 from Mark Thomas --- I'm not overly keen on adding an additional JAR to the distrbution to address this. Does Jetty not have a configuration option to skip the processing of selected container provided SCIs? Alternatively co