Hi JB, thanks for taking a look at it :) removal of features would be a real downside, maybe we can come up with a "smarter" way of solving this :)
regards, Achim 2011/10/13 Jean-Baptiste Onofré <[email protected]> > Hi guys, > > I took a look on this issue. It's require some refactoring on the > pax-web-jsp, including potentially some features removing. It means a new > release of Pax Web, tests, etc. > > Regarding this and the feedback on the mailing list, I postpone this issue > to 2.2.5 and I propose to release 2.2.4 mentioning that war feature is only > Java 6 compliant. > > > Regards > JB > > On 10/12/2011 10:35 PM, Daniel Kulp wrote: > >> >> While doing some testing with 2.2.4-SNAPSHOT, I ran into another issue. >> The >> "war" feature no longer supports Java 5. You cannot install the feature >> due >> to pax-web-jsp pulling in classes only available in Java6. Since 2.2.x >> is >> supposed to support Java5, this is an issue for me. >> >> https://issues.apache.org/**jira/browse/KARAF-933<https://issues.apache.org/jira/browse/KARAF-933> >> >> >> JB is going to look a bit at pax-web tomorrow morning to see if there is >> anything that can be done. If not, we may need to do something like: >> >> 1) release note that war is Java6 only. (btw: this issue exists in >> 2.2.3 as >> well) >> >> 2) Remove jsp from the war feature and maybe add a "war-jsp" feature that >> would include it. (or something similar) >> >> 3) Rollback to pax-web-jsp 1.0.1 (last version that doesn't have the >> problem) >> >> 4) others? >> >> >> Anyway, at this point, I'd like to wait and see what JB finds out. >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > > http://blog.nanthrax.net > Talend - http://www.talend.com > -- -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
