RE: Writing a Java 6-only integration test

2013-02-01 Thread Robert Munteanu
 -Original Message-
 From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
 Sent: Thursday, January 31, 2013 6:44 PM
 To: dev@sling.apache.org
 Subject: Re: Writing a Java 6-only integration test
 
 On Thu, Jan 31, 2013 at 5:42 PM, Felix Meschberger fmesc...@adobe.com
 wrote:
  ...I think we discussed this already. But maybe we should just come to a
 conclusion, that Sling requires Java 6
 
 We could probably use JUnit categories to segregate tests...but I was going
 to say the exact same thing, it's probably safe to drop Java 5 now.
 
 -Bertrand

I've submitted a patch with SLING-2721 which updates just the requirements for 
the integrationtest module to run on Java 6. Let's see where that takes us...

Robert

[1]: https://issues.apache.org/jira/browse/SLING-2721


Writing a Java 6-only integration test

2013-01-31 Thread Robert Munteanu
Hi,

I've noticed that JAXB marshaling works out of the box, given that the proper 
framework extension bundles are available. Since IIUC this has been a tricky 
issue, I'd like to make sure that we keep this functionality working, by 
creating an integration test.

I wanted to add it to org.apache.sling.launchpad.test-services, but that 
project requires Java 1.5, and JAXB and its annotations are only present in 
Java 1.6 and later. What would be the best way to set up a Java 1.6-only 
integration test?

Robert


Re: Writing a Java 6-only integration test

2013-01-31 Thread Felix Meschberger
Hi

I think we discussed this already. But maybe we should just come to a 
conclusion, that Sling requires Java 6.

WDYT ?

Regards
Felix

Am 31.01.2013 um 10:39 schrieb Robert Munteanu:

 Hi,
 
 I've noticed that JAXB marshaling works out of the box, given that the proper 
 framework extension bundles are available. Since IIUC this has been a tricky 
 issue, I'd like to make sure that we keep this functionality working, by 
 creating an integration test.
 
 I wanted to add it to org.apache.sling.launchpad.test-services, but that 
 project requires Java 1.5, and JAXB and its annotations are only present in 
 Java 1.6 and later. What would be the best way to set up a Java 1.6-only 
 integration test?
 
 Robert



Re: Writing a Java 6-only integration test

2013-01-31 Thread Bertrand Delacretaz
On Thu, Jan 31, 2013 at 5:42 PM, Felix Meschberger fmesc...@adobe.com wrote:
 ...I think we discussed this already. But maybe we should just come to a 
 conclusion, that Sling requires Java 6

We could probably use JUnit categories to segregate tests...but I was
going to say the exact same thing, it's probably safe to drop Java 5
now.

-Bertrand