Redback core issue with jdk 1.7 as prerequisite

2014-04-10 Thread Olivier Lamy
Hi,
So we use a pretty old jpox stack which do bytecode enhancement with bcel.
This generate bad bytecode when compiling with 1.7 (if compiler target 1.7)

Solutions I have in mind:
* stay as today not having 1.7 as prerequisite for redback core
(that's what I just did) (compiler target/source 1.6)
* moving to a new technology (openjpa?)

Regarding the last option, does it mean reusing same database model or
using a new one but with  a data migration tooling?

Thoughts?

Cheers
-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy


Re: Jdk 1.7 as prerequisite?

2014-04-03 Thread Chris Graham
Oracle's 8 may have been released (all of a week ago), I'm not sure about
other platforms, AIX, HP-UX etc. Oracles JDK 6 may be EOL'd but IBM's isn't.

Just creating an awareness. :)

-Chris


On Wed, Apr 2, 2014 at 8:16 PM, Eric Barboni eric.barb...@irit.fr wrote:

 +1.
 My favorite is diamond
 ListMyLongType = new ArrayList(); == save your finiger but also known
 as Type inference of generic instance creation
 Eric

 -Message d'origine-
 De : Adrien Lecharpentier [mailto:adrien.lecharpent...@gmail.com]
 Envoyé : mercredi 2 avril 2014 07:58
 À : dev@archiva.apache.org
 Objet : Re: Jdk 1.7 as prerequisite?

 +1 I'm OK with that.
 -- Adrien
 Le 2 avr. 2014 07:53, Olivier Lamy ol...@apache.org a écrit :

  On 2 April 2014 16:46, Adrien Lecharpentier
  adrien.lecharpent...@gmail.com wrote:
   I think it is a good idea as 1.8 has been released, but do we need
   any features of 1.7 in archiva?
 
  maybe String in switch and try-with-resources (maybe nio2 could
  improve scanning)
 
  But 1.6 is EOL and maybe good idea to modernise and use those new
 syntaxes.
 
 
   -- Adrien
   Le 2 avr. 2014 01:13, Olivier Lamy ol...@apache.org a écrit :
  
   Hi,
  
   So all is in the subject?
   Someone has a very huge/blocker issue with moving to 1.7?
  
   If none, I will change in 72H (and bumping version to 2.1.0)
  
  
   Cheers
   --
   Olivier Lamy
   Ecetera: http://ecetera.com.au
   http://twitter.com/olamy | http://linkedin.com/in/olamy
  
 
 
 
  --
  Olivier Lamy
  Ecetera: http://ecetera.com.au
  http://twitter.com/olamy | http://linkedin.com/in/olamy
 




RE: Jdk 1.7 as prerequisite?

2014-04-02 Thread Eric Barboni
+1. 
My favorite is diamond 
ListMyLongType = new ArrayList(); == save your finiger but also known as 
Type inference of generic instance creation
Eric

-Message d'origine-
De : Adrien Lecharpentier [mailto:adrien.lecharpent...@gmail.com] 
Envoyé : mercredi 2 avril 2014 07:58
À : dev@archiva.apache.org
Objet : Re: Jdk 1.7 as prerequisite?

+1 I'm OK with that.
-- Adrien
Le 2 avr. 2014 07:53, Olivier Lamy ol...@apache.org a écrit :

 On 2 April 2014 16:46, Adrien Lecharpentier 
 adrien.lecharpent...@gmail.com wrote:
  I think it is a good idea as 1.8 has been released, but do we need 
  any features of 1.7 in archiva?

 maybe String in switch and try-with-resources (maybe nio2 could 
 improve scanning)

 But 1.6 is EOL and maybe good idea to modernise and use those new syntaxes.


  -- Adrien
  Le 2 avr. 2014 01:13, Olivier Lamy ol...@apache.org a écrit :
 
  Hi,
 
  So all is in the subject?
  Someone has a very huge/blocker issue with moving to 1.7?
 
  If none, I will change in 72H (and bumping version to 2.1.0)
 
 
  Cheers
  --
  Olivier Lamy
  Ecetera: http://ecetera.com.au
  http://twitter.com/olamy | http://linkedin.com/in/olamy
 



 --
 Olivier Lamy
 Ecetera: http://ecetera.com.au
 http://twitter.com/olamy | http://linkedin.com/in/olamy




Jdk 1.7 as prerequisite?

2014-04-01 Thread Olivier Lamy
Hi,

So all is in the subject?
Someone has a very huge/blocker issue with moving to 1.7?

If none, I will change in 72H (and bumping version to 2.1.0)


Cheers
-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy


Re: Jdk 1.7 as prerequisite?

2014-04-01 Thread Adrien Lecharpentier
+1 I'm OK with that.
-- Adrien
Le 2 avr. 2014 07:53, Olivier Lamy ol...@apache.org a écrit :

 On 2 April 2014 16:46, Adrien Lecharpentier
 adrien.lecharpent...@gmail.com wrote:
  I think it is a good idea as 1.8 has been released, but do we need any
  features of 1.7 in archiva?

 maybe String in switch and try-with-resources (maybe nio2 could
 improve scanning)

 But 1.6 is EOL and maybe good idea to modernise and use those new syntaxes.


  -- Adrien
  Le 2 avr. 2014 01:13, Olivier Lamy ol...@apache.org a écrit :
 
  Hi,
 
  So all is in the subject?
  Someone has a very huge/blocker issue with moving to 1.7?
 
  If none, I will change in 72H (and bumping version to 2.1.0)
 
 
  Cheers
  --
  Olivier Lamy
  Ecetera: http://ecetera.com.au
  http://twitter.com/olamy | http://linkedin.com/in/olamy
 



 --
 Olivier Lamy
 Ecetera: http://ecetera.com.au
 http://twitter.com/olamy | http://linkedin.com/in/olamy