Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of rmannibucau@gmail.com
 designates 209.85.215.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABH8ernC4PNK7zfYV61aZhp7eNp2KdxKEd9bQBi8=ZCN9djtTQ@mail.gmail.com>
References: 
 <CABH8erm=PQ=cwQMh83XEWSxaq0Y2v4OthOT9z+COMJ7-A+WKQA@mail.gmail.com>
 <1351200149.64572.YahooMailNeo@web28903.mail.ir2.yahoo.com>
 <CABH8erkCvA2LcqX0wJH+fYthN0KL4bkmHYKCpoO=wCWykFDjqw@mail.gmail.com>
 <CACLE=7MFj9Haj6=eYNSeS2dnkGrR7UjtauFerMSW1sK8tjRZeQ@mail.gmail.com>
 <A2EE2636-FE13-4FA4-9C53-CA4D2D909C60@gmail.com>
 <CACLE=7OaKHRN5fzD7ExmUpLidVBUk8rW9CM1rb01ntsVHfdruA@mail.gmail.com>
 <1351349287.17486.YahooMailNeo@web28903.mail.ir2.yahoo.com>
 <CACLE=7MuQSoTaTV9Si9S-gRnYqV1He1zY2secCr9-N5pbE7nRQ@mail.gmail.com>
 <CABH8ernC4PNK7zfYV61aZhp7eNp2KdxKEd9bQBi8=ZCN9djtTQ@mail.gmail.com>
From: Romain Manni-Bucau <rmannibucau@gmail.com>
Date: Mon, 29 Oct 2012 16:35:37 +0100
Message-ID: 
 <CACLE=7MPdSWE5jEmUKmbhoP+_F=jnBiT9Z--EcRC0my=P32q7Q@mail.gmail.com>
Subject: Re: [DISCUSS] Upgrade to use ASM 4 for our post-enhancement
 processing
To: dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=f46d04016951049d0f04cd346dec

--f46d04016951049d0f04cd346dec
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

currently tomee depends on a shade of openjpa 2.2.0 where we remove asm
dependency for xbean asm

but it would be a pain to not be able to upgrade because of it no?
(moreover we should avoid shade between ASF projects)

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.co=
m/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*


2012/10/29 Kevin Sutter <kwsutter@gmail.com>

> Hi,
> Does TomEE have a dependency on specific version(s) of OpenJPA?  Currentl=
y,
> the patch for looking for the xbean and spring shaded versions of ASM is
> only in OpenJPA Trunk.  Is TomEE really dependent on OpenJPA Trunk?  I
> would have assumed a more stable release would have been selected.
>
> I'm trying to determine the difference between your "next release" and th=
e
> "short term release" you are referencing.  That is, what release(s) would
> work for this ASM 4 upgrade as it relates to TomEE?  (BTW, we are doing a
> similar exercise with WebSphere's usage to determine the proper timeframe
> for this upgrade.)
>
> Thanks,
> Kevin
>
> On Sat, Oct 27, 2012 at 9:51 AM, Romain Manni-Bucau
> <rmannibucau@gmail.com>wrote:
>
> > well tomee don't really care but here we depend on
> > 1) xbean (should be doable)
> > 2) cxf
> >
> > that's why i proposed to do next release with xbean 3 and then try to
> > upgrade all libs
> >
> > wdyt? isnt it more pragmatic for short term releases (apache con would =
be
> > fantastic)?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> >
> > 2012/10/27 Mark Struberg <struberg@yahoo.de>
> >
> > > If ASM4 is providing functionality for java7 which the older version
> > > cannot provide then I see no reason to not work towards using ASM4 in
> > TomEE
> > > as well. This should not be a blocker for OpenJPA but more some a poi=
nt
> > > which we have to be aware of and need to handle some way.
> > >
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > From: Romain Manni-Bucau <rmannibucau@gmail.com>
> > > > To: dev@openjpa.apache.org
> > > > Cc:
> > > > Sent: Saturday, October 27, 2012 2:14 PM
> > > > Subject: Re: [DISCUSS] Upgrade to use ASM 4 for our post-enhancemen=
t
> > > processing
> > > >
> > > > Yep but it is not as easy as you say since thats internals and both
> > will
> > > > not be tested IMO
> > > > Le 27 oct. 2012 01:57, "David Blevins" <david.blevins@gmail.com>
> > > > a =E9crit :
> > > >
> > > >>  Fork is not the right word.  Patch maybe, but even that can easil=
y
> be
> > > >>  avoided.
> > > >>
> > > >>  If we had abstraction so there wasn't a hard dependency on
> > > > "ASM" we could
> > > >>  supply our own shaded version, that would be more than enough.
> > > >>
> > > >>  -David
> > > >>
> > > >>
> > > >>  On Oct 25, 2012, at 11:58 PM, Romain Manni-Bucau
> > > > <rmannibucau@gmail.com>
> > > >>  wrote:
> > > >>
> > > >>  > If so tomee will fork openjpa to use xbean asm shade...
> > > >>  >
> > > >>  > Tomee cares about size
> > > >>  > Le 26 oct. 2012 00:23, "Kevin Sutter"
> > > > <kwsutter@gmail.com> a =E9crit :
> > > >>  >
> > > >>  >> Hi Mark,
> > > >>  >> Yes, Romain raised this point to me on a separate thread.  Fro=
m
> > > > what I
> > > >>  can
> > > >>  >> tell TomEE is using OpenJPA 2.2.0.  Since your changes for
> > > > openjpa-2171
> > > >>  >> only went into trunk, I'm wondering where the dependency is
> > > > being
> > > >>  managed.
> > > >>  >> So, yes, we do need some input from the TomEE team as to wheth=
er
> > > > this
> > > >>  type
> > > >>  >> of change would affect them.
> > > >>  >>
> > > >>  >> Another alternative is to provide a shaded jar that embeds and
> > > > hides the
> > > >>  >> ASM deliverable within the OpenJPA jar.  Yes, that jar would
> grow
> > > >>  slightly
> > > >>  >> (46K), but then nobody would be wiser as to what version of AS=
M
> is
> > > > being
> > > >>  >> used.
> > > >>  >>
> > > >>  >> Anyway, let's keep the conversation going...  Thanks!
> > > >>  >>
> > > >>  >> Kevin
> > > >>  >>
> > > >>  >> On Thu, Oct 25, 2012 at 4:22 PM, Mark Struberg
> > > > <struberg@yahoo.de>
> > > >>  wrote:
> > > >>  >>
> > > >>  >>> Hi Kevin!
> > > >>  >>>
> > > >>  >>> We must also make sure to not hit a major incompat with tomee
> > > > and other
> > > >>  >>> systems.
> > > >>  >>> I'll ping David and Romain so they can test this a bit.
> > > >>  >>>
> > > >>  >>> LieGrue,
> > > >>  >>> strub
> > > >>  >>>
> > > >>  >>>
> > > >>  >>>
> > > >>  >>> ----- Original Message -----
> > > >>  >>>> From: Kevin Sutter <kwsutter@gmail.com>
> > > >>  >>>> To: users@openjpa.apache.org; dev@openjpa.apache.org
> > > >>  >>>> Cc:
> > > >>  >>>> Sent: Thursday, October 25, 2012 3:15 PM
> > > >>  >>>> Subject: [DISCUSS] Upgrade to use ASM 4 for our
> > > > post-enhancement
> > > >>  >>> processing
> > > >>  >>>>
> > > >>  >>>> Hi,
> > > >>  >>>> Some of you may have noticed a recent JIRA I opened up:
> > > >>  >>>> https://issues.apache.org/jira/browse/OPENJPA-2283
> > > >>  >>>>
> > > >>  >>>> I created this for upgrading our current usage of ASM 3.2
> > > > to ASM 4.0.
> > > >>  >>>> OpenJPA uses ASM for some post-enhancement processing to
> > > > clean up the
> > > >>  >>> stack
> > > >>  >>>> map tables that are required for Java 7 validation.  Since
> > > > ASM 4 has
> > > >>  >> more
> > > >>  >>>> complete support for Java 7, I thought it would be an
> > > > easy,
> > > >>  >>>> preventative-care type of move.
> > > >>  >>>>
> > > >>  >>>> As my JIRA indicates, I have run into a couple of hiccups
> > > > with this
> > > >>  >> move
> > > >>  >>>> that I am still working through.
> > > >>  >>>>
> > > >>  >>>> But, in general, does anybody have a concern with this
> > > > upgrade?  I'm
> > > >>  >> only
> > > >>  >>>> looking to do trunk at the moment.  But, if we continue to
> > > > hit Java 7
> > > >>  >>>> validation errors in 2.2.x, then I might consider moving
> > > > it back to
> > > >>  >> 2.2.x
> > > >>  >>>> as well.
> > > >>  >>>>
> > > >>  >>>> Thanks for any input,
> > > >>  >>>> Kevin
> > > >>  >>>>
> > > >>  >>>
> > > >>  >>
> > > >>
> > > >>
> > > >
> > >
> >
>

--f46d04016951049d0f04cd346dec--