Passing along an email I saw related to spring framework upgrades in uPortal/portlets to make sure we spread the information far and wide and get any feedback accordingly ...
https://github.com/spring-projects/spring-framework/wiki/Migrating-from-earlier-versions-of-the-spring-framework Still working through stuff, but one thing that might help (from the above link): * * *Enforced minimum dependency versions *As of Spring Framework 4.1, several optional dependencies are required to be within the supported range: in particular, /*EhCache 2.5+, Quartz 2.1.4+, Jackson 2.1+, and ROME 1.5*+/ (see below for details about 4.x dependency declarations in the Spring Framework 4.0 section). Older versions have still been tolerated in the Spring Framework 4.0.x line for a smoother upgrade path; *as of 4.1, the intended minimum versions are being enforced. /Most importantly, don't use Quartz 1.8.x anymore; upgrade to Quartz 2.1.4+ instead! /*Note that as of Spring Framework 4.1.4, Apache HttpComponents HttpClient needs to be 4.3+ across the framework. The previous partial tolerance of old HttpClient versions had to be dropped in order to fix several configuration issues when running against 4.3+. I'm also seeing a need to update Hibernate (I'm trying 3.6.10.Final). That may also require adding/updating a bunch of other dependencies as well (Javassist, slf4j, etc). James Wennmacher - Unicon 480.558.2420 On 01/29/2015 05:07 PM, James Wennmacher wrote: > Upon reflection I think this is very reasonable. What I took from > this is: > > * Bump the portlet's major version # (my interpretation) > * Change all portlets we upgrade Spring on to build to Java 7, > document accordingly > > I like that and I can live with it. Anyone running Java 6 is probably > not updating their portlets, and they certainly have an easy upgrade > path by just switching to Java 7 without changing any other part of > their infrastructure. Works for me (and is very desirable). > > James Wennmacher - Unicon > 480.558.2420 > On 01/29/2015 04:05 PM, Drew Wills wrote: >> James et al., >> >>> On Jan 29, 2015, at 1:59 PM, James Wennmacher<jwennmac...@unicon.net> >>> wrote: >>> >>> the portlets generally must be compiled to Java 6 to be backwards >>> compatible with uPortal 4.0.x [4]. >> They have to be compiled to Java 6 to be compatible with uP 4.0 _on Java 6_. >> IIRC, running uP 4.0 on Java 7 is supported as well, so you could actually >> run a Java 7 portlet on uP 4.0 if you like. >> >> And as we advance the platform to newer versions of Java, I should think the >> portlets are free to follow suit as soon as the opportunity permits. This >> who want updates to their Java 6 portlets running in their Java 6 JVM can >> still have them — they just need to obtain a new patch release on the line >> they’re already on. We won’t shift required JVM version in a patch release. >> >> drew >> >> >> > -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
