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.
The main functionality that matters is:
* Take all of the classes in the application: APPLICATION_CLASSES
* Take all of the classes exposed to the application from the app server: MODULE_CLASSES
* Take all of the classes that are part of your Java platform: JAVA_PLATFORM_CLASSES
(These are all classes provided to the Application) AVAILABLE
* Take all of the classes referenced in the application
(These are all classes consumed by the Application) CONSUMED
Create the following reports:
CONSUMED - AVAILABLE = That will show you if your application is likely to have a classloader issue.
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
Intersection of APPLICATION_CLASSES & JAVA_PLATFORM_CLASSES = The JAR files you can and should drop from your application
In order to do this, we would have to have an index of Java Classes:
* For all versions of Java JDK : 1.6+
* For all versions of JBoss EAP 6.X
* Indexed to include the module providing the class
Brad Davis
Senior Manager, Red Hat Consulting
Email: bdavis@redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter@gmail.com>
To: "Marek Novotny" <mnovotny@redhat.com>, "Windup-dev List" <windup-dev@lists.jboss.org>, "Marc Zottner" <mzottner@redhat.com>, "Robb Greathouse" <rgreatho@redhat.com>, "Tobias Hartwig" <thartwig@redhat.com>, "Brad Davis" <bdavis@redhat.com>
Sent: Thursday, July 23, 2015 4:36:10 PM
Subject: Re: [windup-dev] Fwd: Re: Tattletale future?
I guess in principle I'm fine with forking Tattletale into our repo, and
publishing it under a different artifact, but in reality, I don't know that
it's at all useful. I think we might better spend our time figuring out why
people want it (if they want it) and then deciding if it's worth
maintaining it.
Do we have any users that actually use this feature? Robb, why did you want
Tattletale? Marc? Brad? Tobias? Thoughts?
~Lincoln
On Thu, Jul 23, 2015 at 2:04 AM, Marek Novotny <mnovotny@redhat.com> wrote:
> Hi windup devs,
>
> I asked Jesper what is the plan with tattletale and below is his response.
>
> I think we probably need replace the features by merging it into our
> codebase or just fork tattletale as its future is stalled and that means
> our fork won't need updates from upstream/original tattletale stream.
>
> Are you fine with that? I am asking due this related issue
> https://issues.jboss.org/browse/WINDUP-699, but there will be probably
> more reasons, list your own if you have any ;)
>
> -------- Forwarded Message --------
> Subject: Re: Tattletale future?
> Date: Wed, 22 Jul 2015 10:39:07 -0400
> From: Jesper Pedersen <jpederse@redhat.com>
> Organization: JBoss, by Red Hat
> To: mnovotny@redhat.com
>
> Hi,
>
> On 07/22/2015 10:30 AM, Marek Novotny wrote:
> > I was looking in Tattletale github repository and it seems it is a long
> > time from the last commit
>
> Project has been dead for 3 years now.
>
> > and PRs are were waiting in a queue.
> >
>
> Likely because they are incomplete or wrong - but whatever works for
> people. I'm not spending time on it though.
>
> > What's the plan for Tattletale project?
> >
>
> There are no plans to activate the project again.
>
> Best regards,
> Jesper
>
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."