[jbosstools-dev] Fwd: [m2e-dev] Fwd: Possibly critical issue with forge or m2e

Fred Bricon fbricon at gmail.com
Thu Jul 3 07:01:04 EDT 2014


FYI
---------- Forwarded message ----------
From: Igor Fedorenko <igor at ifedorenko.com>
Date: Thu, Jul 3, 2014 at 7:27 AM
Subject: Re: [m2e-dev] Fwd: [jbosstools-dev] Possibly critical issue with
forge or m2e
To: m2e-dev at eclipse.org


First and foremost, avoid truezip as a plague. This, along with couple
of other true* libraries I've looked at, constitute some of the most
complicated and overengineered pieces of code I've ever seen :-)

I have not looked at truezip sources and don't know what kind of class
lookup it uses, there was a similar problem reported in 396554 [1],
which appears to be a general problem when using TCCL with
Equinox/ContextFinder and Class.forName. There are couple of articles
linked from the bugzilla that explain the problem in more details,
probably [2] the most detailed and relevant.

In any case, I am not aware of any thread context classloader "leaks" in
m2e, so if somebody believes there is such leak please provide a quality
fix and I'll review and apply it.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=396554
[2] http://blog.bjhargrave.com/2007/07/contextfinder-in-
eclipse-is-broken.html

--
Regards,
Igor

On 2014-07-03, 0:43, Fred Bricon wrote:

> Transferring from jbosstools-dev at lists.jboss.org
> <mailto:jbosstools-dev at lists.jboss.org> to a wider audience. Does it
>
> ring a bell to anyone?
>
> ---------- Forwarded message ----------
>
> Hey all:
>
> A user found a strange bug while using astools and publishing a zipped
> project. The bug is basically that truezip ( a library we use) can't
> initialize because it can't find a class. It can't find the class
> because the thread's classloader is from plexus classrealms, and not the
> standard eclipse classloader that we'd expect.
>
> So basically, either forge or m2e is changing a worker's classloader,
> and not putting it back. This (if true) could be a critical issue, since
> that thread / worker will probably never have the proper classloader
> again for the workspace session.
>
> I encourage anyone with access to m2e or forge to look into this and
> verify their respective codebases are behaving properly with regards to
> classloaders. Feel free to look at the jira and ask any for more details
> or any questions you might have that might help in tracking this down.
>
> https://issues.jboss.org/browse/JBIDE-17700
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org  <mailto:jbosstools-dev at lists.jboss.org>
>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
>
>
> --
> "Have you tried turning it off and on again" - The IT Crowd
>
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
>  _______________________________________________
m2e-dev mailing list
m2e-dev at eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev



-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20140703/3c87459f/attachment-0001.html 


More information about the jbosstools-dev mailing list