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 <[email protected]> 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 [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
