Grouper Users - Open Discussion List

[Chris Hyzer <>]

I tested 2.1.4 (candidate) with Java7 and everything works fine for me.  
Including running tests with Java7 and oracle.

https://bugs.internet2.edu/jira/browse/GRP-878

I also tested the UI, WS, and client.  I think we should change the minimum 
requirement for Grouper to be Java7, though I think we should compile with 
java6 just in case (so we wont start using java7 language features).  If 
people still want to run on java6, it should work fine.  Is it too soon?  :)  
Also, obviously the developers should start developing/testing with Java7 as 
well.

Maybe we can discuss in the dev call on wed.

Thanks,
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Chris Hyzer
Sent: Monday, February 04, 2013 8:52 AM
To: Dominique Petitpierre
Cc: 

Subject: RE: [grouper-users] Grouper 2.1.3: errors with "gsh.sh -test -all"

Just curious... I know some of the unit tests were wonky, but does anyone run 
Grouper with Java7 right now?
Which components (UI? WS? Loader? PSP? Etc?)

Thanks,
Chris

-----Original Message-----
From: Chris Hyzer 
Sent: Sunday, February 03, 2013 11:13 AM
To: 'Dominique Petitpierre'
Cc: 

Subject: RE: [grouper-users] Grouper 2.1.3: errors with "gsh.sh -test -all"

Thanks for all your work here.  Yes, my java version is 6.  We need to 
support java 7 in Grouper 2.1.4+...

https://bugs.internet2.edu/jira/browse/GRP-878

I think it is a lot more urgent to keep java version on desktops up to date 
than servers, but I do agree that we need to support the Java version that is 
supported by Oracle...

Thanks,
Chris


-----Original Message-----
From: Dominique Petitpierre 
[mailto:]
 
Sent: Saturday, February 02, 2013 8:06 PM
To: Chris Hyzer
Cc: 

Subject: Re: [grouper-users] Grouper 2.1.3: errors with "gsh.sh -test -all"

Hi,

Thanks for your reply:

On 31/01/2013 01:29 , Chris Hyzer wrote:
> I just ran all the tests of 2.1.3 against oracle and it worked fine.

- Which version of Java did you use?

I made some further test sessions and it is now clear that, in my 
context, the varying error reports only occur with Java 7. I tried many 
combinations of java version (1.6.0_33, 1.6.0_38, 1.7.0_05, 1.7.0_11), 
oracle or hsql database, with hibernate.cache.use_query_cache set to 
true or false: errors never occurred with Java 6, and often with Java 7. 
(You'll find in annexe yet another example of reported errors).

- Has anybody else noticed this (test suite reporting errors with java 7)?

> If the tests run individually, but not in the suite, then Im not 
> concerned... there might be differences with caches and with clearing out 
> the DB all of the sudden, or other that would not happen in real life.

OK. But this is unfortunate: in my opinion unit tests should be 
deterministic, i.e. reported errors should not vary from one run to 
another in the same context, and certainly not differ if a test is run 
in a suite or individually.
If running individual tests becomes necessary to establish if errors 
reported by "-test -all" are to be taken seriously or not, it should be 
described in the installation documents (e.g. README.txt) when and how 
to run them.

I was using Java 7 because it has been available since July 2011 and 
Java 6 won't be supported after February 2013 (after two extensions, the 
original EOL was July  2012), and I did not find any information against 
it in the documentation or the Grouper user mailing list.
Refs:
Oracle Java SE Support Roadmap
    http://www.oracle.com/technetwork/java/eol-135779.html
Updated Java 6 EOL date
    https://blogs.oracle.com/henrik/entry/updated_java_6_eol_date

Maybe the requirement document should also state what is the most recent 
version of Java that has been used successfully by the developers. (cf 
https://spaces.internet2.edu/display/Grouper/Specsheet).


Best regards,
Dominique

Mr Dominique Petitpierre, user=Dominique.Petitpierre domain=unige.ch
IT Division, University of Geneva, Switzerland