urm-core

Automatically generate class diagram from your code

License	The Apache Software License, Version 2.0
GroupId	com.iluwatar.urm
ArtifactId	urm-core
Last Version	2.0.0
Release Date	Aug 15, 2020
Type	jar
Description	urm-core Automatically generate class diagram from your code
Project URL	http://maven.apache.org

Download urm-core

Filename	Size
urm-core-2.0.0.pom
urm-core-2.0.0.jar	4 MB
urm-core-2.0.0-sources.jar	19 KB
urm-core-2.0.0-javadoc.jar	135 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.iluwatar.urm/urm-core/ -->
<dependency>
    <groupId>com.iluwatar.urm</groupId>
    <artifactId>urm-core</artifactId>
    <version>2.0.0</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.iluwatar.urm/urm-core/
implementation 'com.iluwatar.urm:urm-core:2.0.0'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.iluwatar.urm/urm-core/
implementation ("com.iluwatar.urm:urm-core:2.0.0")

Apache Buildr

'com.iluwatar.urm:urm-core:jar:2.0.0'

Apache Ivy

<dependency org="com.iluwatar.urm" name="urm-core" rev="2.0.0">
  <artifact name="urm-core" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.iluwatar.urm', module='urm-core', version='2.0.0')
)

Scala SBT

libraryDependencies += "com.iluwatar.urm" % "urm-core" % "2.0.0"

Leiningen

[com.iluwatar.urm/urm-core "2.0.0"]

Dependencies

compile (1)

Group / Artifact	Type	Version
net.sf.qualitycheck : quality-test	jar	1.3

test (4)

Group / Artifact	Type	Version
junit : junit	jar	4.13
org.hamcrest : hamcrest-all	jar	1.3
nl.jqno.equalsverifier : equalsverifier	jar	3.4.1
org.mockito : mockito-all	jar	1.10.19

Project Modules

There are no modules declared in this project.

UML Reverse Mapper

Automatically generate class diagram from your code.

Using reflection, UML Reverse Mapper scans your packages that contain your code. It builds the class relations and can output as a Graphviz .dot file, a PlantUML .puml file or a Mermaid .mmd file.

The tool is available in command line version (urm-core) and Maven plugin (urm-maven-plugin).

Using from the command-line

Build the urm-core project with mvn clean package and grab the generated artifact urm-core.jar. Then you need the archive that will be analyzed. In this example we use abstract-factory.jar and assume the package name to be com.iluwatar.abstractfactory. Place the jar-files in the same directory and execute the following command.

java -cp abstract-factory.jar:urm-core.jar com.iluwatar.urm.DomainMapperCli -p com.iluwatar.abstractfactory -i com.iluwatar.abstractfactory.Castle

This will scan all the classes under the package com.iluwatar.abstractfactory except Castle that was marked to be ignored and output the markup to your console output. By default PlantUML presenter is used, but it can be changed with switch -s graphviz or -s mermaid. If you want to write it to file use switch -f filename. If you need to scan multiple packages use format -p "com.package1, com.package2". Note that under Windows OS the classpath separator is ; instead of :

Using the Maven plugin

Add to your pom.xml the following:

<build>
  <plugins>
    <plugin>
      <groupId>com.iluwatar.urm</groupId>
      <artifactId>urm-maven-plugin</artifactId>
      <version>2.0.0</version>
      <configuration>
        <!-- if outputDirectory is not set explicitly it will default to your build dir -->
        <outputDirectory>${project.basedir}/etc</outputDirectory>
        <packages>
          <param>com.mycompany.mypackage</param>
          <param>com.mycompany.other_package</param>
        </packages>
        <ignores>
          <param>com.mycompany.mypackage.MyClass</param>
          <param>com.mycompany.other_package.OtherClass</param>
        </ignores>
        <includeMainDirectory>true</includeMainDirectory>
        <includeTestDirectory>false</includeTestDirectory>
        <presenter>graphviz</presenter>
      </configuration>
      <executions>
        <execution>
          <phase>process-classes</phase>
          <goals>
            <goal>map</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
  </plugins>
</build>

• packages configuration parameter contains a list of packages that should be included in the class diagram
• ignores configuration parameter contains a list of types that should be excluded from the class diagram
• Dependencies list should contain the artifacts where the classes are found. See https://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_dependencies_Tag
• includeMainDirectory configuration parameter indicates to include classes of src/main/java directory. Default value of includeMainDirectory is true.
• includeTestDirectory configuration parameter indicates to include classes of src/test/java directory. Default value of includeTestDirectory configuration parameter is false.
• presenter parameter control which presenter is used. Can be graphviz, plantuml or mermaid.

When process-classes life-cycle phase gets executed, the class diagram will be saved to the location specified by outputDirectory parameter. If not specified the file is saved to /target/${project.name}.urm.dot or /target/${project.name}.urm.puml. Use this file with your local or online tools to show your class diagram.

Showcases

Here are some class diagrams generated with the urm-maven-plugin.

Deploy Instructions

Performing a Release Deployment

mvn clean deploy -P release

Release notes

• 2.0.0

  • Add support for Mermaid presenter #39
  • Update to Java 11 #42 and #56

• 1.4.8

  • Update dependencies to latest versions #21
  • Work on Java 11 compatibility #18
  • Create directories for the output file, if they don't exist

• 1.4.7

  • Update README.md instruction #20
  • Presenter can not be chosen via command line parameter #22
  • Presenter can not be chosen via plugin parameters #23

Versions

Version
2.0.0 Aug 15, 2020
1.4.8 Dec 7, 2019
1.4.7 Nov 5, 2019
1.4.6 Nov 3, 2019