lineruniversity.blogg.se

#69 tattletale how to#
#69 tattletale free#

# classdependson - For all classes, lists the classes a class depends on. # classdependants - For all classes, lists the classes that depends on a class. Wildcard "*" is default and generates all available reports. # Comma-separated list of reports to generate. # Comma-separated list of profiles used to determine if classes are provided by some framework or library. Only relevant to users of JBoss AS.Ĭlassloader=.classloader.NoopClassLoaderStructure # Classloader structure to use when scanning JAR files. # For complete documentation, please see: My configuration file looks like this: # JBoss Tattletale configuration file. If you like to clean up after Tattletale report generation and delete the temporary directory, add the following plug-in to the Maven profile listed above after the Tattletale plug-in: Īs previously mentioned, I rely on a separate configuration file to configure Tattletale.

Tattletale will delete the contents of this directory before generating reports, so do not chose a directory that contains files and/or folders that you do not want deleted. Note the three properties (tattletale.tempdir, tattletale.reportdir and nfigfile) in the profile – these allow you to customize the location of the temporary directory to which JAR-files are copied, the location of the directory to which generated reports are written and finally the location of the Tattletale configuration file.Ī word of warning concerning the choice of directory which to write the report to: We’ll examine this configuration file below. I have used a separate configuration file for Tattletale that enables more fine-grained configuration. If your project creates multiple JAR-files or other types of files (WAR-file(s), for instance) or use a non-standard naming scheme for the files produced, you have to modify the contents of the element. This assumes that the project creates one single JAR-file.

Copy the JAR-file of the project to the temporary directory.

While it is possible to specify multiple directories which Tattletale is to scan for JAR-files to analyze, I found it simpler to copy all the dependencies to one and the same directory.

Copy JAR-files of all dependencies to temporary directory.

Report generation consists of these steps: The Maven build profile for Tattletale report generation looks like this: This enable me to either quickly copy the Maven build profile for Tattletale report generation to a new project or to include it in a parent pom-file, if one is available.

Tattletale report generation require some preparations, as we will see, and I wanted to gather all the steps in one place.

Report generation is time-consuming and I do not want to generate reports at every build.

I want to have control over when to generate Tattletale reports.

I have chosen to create a Maven build profile for Tattletale report generation. I experienced some strange problems and became quite puzzled before I realized that there were different classes that had the same name and resided in the same package on my class-path.Īfter having run Tattletale from the command-line a couple of times, my laziness struck me once again and decided to use the Tattletale Maven plug-in to be able to generate reports routinely when building my project. What first caused me to turn to Tattletale was when I wanted to use a newer version of the Apache HTTP Client in a program that used a library that has a dependency to an older version of said HTTP client.

#69 tattletale how to#

In this article I will show how to use JBoss Tattletale from Maven and look at some of the reports produced by Tattletale.

#69 tattletale free#

It still, to my knowledge, the best free tool to discover dependencies, relations and even collisions between dependencies. JBoss Tattletale is not a new tool, in fact the latest version was released about three years ago and nothing has happened in the Git repository since.