Help

The second beta for the Tattletale, the Java dependency analyzer, 1.1 release is out.

All users should upgrade to this release.

Full release notes are here.

Build environment

The major focus of this release was to fully support the Apache Ant and Apache Maven build environments. Furthermore it is now possible to specify all configuration parameters directly in the plugins instead of using the configuration file.

See the user guide for further information about how to integrate Tatteltale into your build environment.

Apache Ant

Use the report task, like

<tattletale:report source="${jar.dir]" destination="${report.dir}"/>

Apache Maven

Use the report mojo, like

<plugin>
  <groupId>org.jboss.tattletale</groupId>
  <artifactId>tattletale-maven</artifactId>
  <!-- The version of the plugin you want to use -->
  <version>1.1.0.Beta2</version>
  <executions>
    <execution>
     <goals>
       <goal>report</goal>
     </goals>
    </execution>
  </executions>
  <configuration>
    <!-- This is the location which will be scanned for generating tattletale reports --> 
    <source>/absolutepath/to/source/dir</source>
    <!-- This is where the reports will be generated -->
    <destination>/absolute/path/to/reports/dir</destination>
  </configuration>
</plugin>

New report

This release add the

  • Circular Dependency

report, which will let you find circular dependencies within your project. The time has come to split those archives into a proper structure !

The Road Ahead

The next development cycle will focus on integration with a Hudson environment, so if you want to help drop by our forum.

For Those About to Rock, We Salute You !

[WebSite] [Download] [JIRA] [Forum]

3 comments:
 
07. Dec 2009, 22:44 CET | Link

Just thought I give it a go in an existing maven project. I added:

<plugin>
  <groupId>org.jboss.tattletale</groupId>
  <artifactId>tattletale-maven</artifactId>
  <version>1.1.0.Beta2</version>
  <executions>
    <execution>
     <goals>
       <goal>report</goal>
     </goals>
    </execution>
  </executions>
  <configuration>
    <!-- This is the location which will be scanned for generating tattletale reports --> 
    <source>${basedir}/src/main/java</source>
    <!-- This is where the reports will be generated -->
    <destination>${basedir}/target/tattletale</destination>
  </configuration>
</plugin>

After downloading the tattletale pom and jar I got:

[INFO] Internal error in the plugin manager getting plugin 'org.jboss.tattletale:tattletale-maven': Plugin 'org.jboss.tattletale:tattletale-maven:1.1.0.Beta2' has an invalid descriptor: 1) Plugin's descriptor contains the wrong version: 1.0.0-SNAPSHOT

Anything ideas?

ReplyQuote
 
08. Dec 2009, 00:31 CET | Link

Change the tattletale-maven.jar:/META-INF/plugin.xml to 1.1.0.Beta2 - instead of using SNAPSHOT. Will fix in repo. Thanks.

 
16. Dec 2009, 20:43 CET | Link
Danilo Vujovic | danilo.vujovic(AT)gs.com
I've set up the maven plugin as described, however, "mvn clean package" produces an empty report.
Which directory is the source configuration setting in the pom supposed to point to?
I expected the plugin to work out which jars from the local maven repo end up on the classpath of the module in question and then do the analysis on them, after which a report is produced. Surely, users are not expected to get maven to move all the jars to a single dir beforehand as a prerequisite to get this plugin to function.
I may be missing something here.
Thanks in advance.
Post Comment