<div dir="ltr">I think that what Jess has done with the "Unresolved classes" detection, is already a more useful start than the Tattletale reports. I'd love to see this as the basis for the new report. This can even be rectified against a server profile (such as an EAP6 snapshot) - Ondra was working on this a little while ago before we de-prioritized the server migration stuff in favor of summit prep.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 23, 2015 at 4:48 PM, Brad Davis <span dir="ltr"><<a href="mailto:bdavis@redhat.com" target="_blank">bdavis@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tattletale was useful because it provided proactive reporting on classloader issues that are common with migrations. The codebase isn't worth reusing -- he embedded most of the logic quickly into the UI code.<br>
<br>
The main functionality that matters is:<br>
* Take all of the classes in the application: APPLICATION_CLASSES<br>
* Take all of the classes exposed to the application from the app server: MODULE_CLASSES<br>
* Take all of the classes that are part of your Java platform: JAVA_PLATFORM_CLASSES<br>
(These are all classes provided to the Application) AVAILABLE<br>
<br>
* Take all of the classes referenced in the application<br>
(These are all classes consumed by the Application) CONSUMED<br>
<br>
Create the following reports:<br>
CONSUMED - AVAILABLE = That will show you if your application is likely to have a classloader issue.<br>
Intersection of APPLICATION_CLASSES & MODULE_CLASSES = The JAR files that you might be able to drop from your application if you add in the appropriate JBoss Module Configuration<br>
Intersection of APPLICATION_CLASSES & JAVA_PLATFORM_CLASSES = The JAR files you can and should drop from your application<br>
<br>
<br>
In order to do this, we would have to have an index of Java Classes:<br>
* For all versions of Java JDK : 1.6+<br>
* For all versions of JBoss EAP 6.X<br>
* Indexed to include the module providing the class<br>
<br>
<br>
<br>
<br>
Brad Davis<br>
Senior Manager, Red Hat Consulting<br>
Email: <a href="mailto:bdavis@redhat.com">bdavis@redhat.com</a> | c: <a href="tel:980.226.7865" value="+19802267865">980.226.7865</a> | <a href="http://www.redhat.com" rel="noreferrer" target="_blank">http://www.redhat.com</a><br>
<span class=""><br>
<br>
----- Original Message -----<br>
From: "Lincoln Baxter, III" <<a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@gmail.com</a>><br>
To: "Marek Novotny" <<a href="mailto:mnovotny@redhat.com">mnovotny@redhat.com</a>>, "Windup-dev List" <<a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a>>, "Marc Zottner" <<a href="mailto:mzottner@redhat.com">mzottner@redhat.com</a>>, "Robb Greathouse" <<a href="mailto:rgreatho@redhat.com">rgreatho@redhat.com</a>>, "Tobias Hartwig" <<a href="mailto:thartwig@redhat.com">thartwig@redhat.com</a>>, "Brad Davis" <<a href="mailto:bdavis@redhat.com">bdavis@redhat.com</a>><br>
Sent: Thursday, July 23, 2015 4:36:10 PM<br>
Subject: Re: [windup-dev] Fwd: Re: Tattletale future?<br>
<br>
I guess in principle I'm fine with forking Tattletale into our repo, and<br>
publishing it under a different artifact, but in reality, I don't know that<br>
it's at all useful. I think we might better spend our time figuring out why<br>
people want it (if they want it) and then deciding if it's worth<br>
maintaining it.<br>
<br>
Do we have any users that actually use this feature? Robb, why did you want<br>
Tattletale? Marc? Brad? Tobias? Thoughts?<br>
<br>
~Lincoln<br>
<br>
</span><span class="">On Thu, Jul 23, 2015 at 2:04 AM, Marek Novotny <<a href="mailto:mnovotny@redhat.com">mnovotny@redhat.com</a>> wrote:<br>
<br>
> Hi windup devs,<br>
><br>
> I asked Jesper what is the plan with tattletale and below is his response.<br>
><br>
> I think we probably need replace the features by merging it into our<br>
> codebase or just fork tattletale as its future is stalled and that means<br>
> our fork won't need updates from upstream/original tattletale stream.<br>
><br>
> Are you fine with that? I am asking due this related issue<br>
</span><span class="">> <a href="https://issues.jboss.org/browse/WINDUP-699" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WINDUP-699</a>, but there will be probably<br>
> more reasons, list your own if you have any ;)<br>
><br>
> -------- Forwarded Message --------<br>
> Subject: Re: Tattletale future?<br>
> Date: Wed, 22 Jul 2015 10:39:07 -0400<br>
</span><span class="">> From: Jesper Pedersen <<a href="mailto:jpederse@redhat.com">jpederse@redhat.com</a>><br>
> Organization: JBoss, by Red Hat<br>
</span><span class="">> To: <a href="mailto:mnovotny@redhat.com">mnovotny@redhat.com</a><br>
><br>
> Hi,<br>
><br>
> On 07/22/2015 10:30 AM, Marek Novotny wrote:<br>
> > I was looking in Tattletale github repository and it seems it is a long<br>
> > time from the last commit<br>
><br>
> Project has been dead for 3 years now.<br>
><br>
> > and PRs are were waiting in a queue.<br>
> ><br>
><br>
> Likely because they are incomplete or wrong - but whatever works for<br>
> people. I'm not spending time on it though.<br>
><br>
> > What's the plan for Tattletale project?<br>
> ><br>
><br>
> There are no plans to activate the project again.<br>
><br>
> Best regards,<br>
> Jesper<br>
><br>
><br>
><br>
> _______________________________________________<br>
> windup-dev mailing list<br>
</span>> <a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
<span class="">> <a href="https://lists.jboss.org/mailman/listinfo/windup-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br>
><br>
<br>
<br>
<br>
--<br>
Lincoln Baxter, III<br>
<a href="http://ocpsoft.org" rel="noreferrer" target="_blank">http://ocpsoft.org</a><br>
</span>"Simpler is better."<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."</div>
</div>