Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Maven Info on the plugin site for more information.

This plugin add features related to Maven jobs info. Adds columns configurable in views (version, dependencies, modules, ...) and extract information from Maven jobs (update name and description from POM, ...)

Tested On

Jenkins: 1.500, 1.509.4
Chrome: 30
Internet Explorer: 10
Firefox: 24


Column: Selected Module Last Version

Shows last build version.

If you move mouse over the version, an info panel is shown.

This panel shows main module's info and all modules grouped by groupId. If a module has different version then it's also shown between brackets.

Main module is shown in bold italic .

Column: Selected Dependencies

Show version of selected dependencies.

If you move the mouse pointer over the version, an info panel is also shown.

Only one version by column. If there is more than one version by dependency, then the column is marked with an asterisk ( * ) and all the versions are shown in the info panel.

This panel shows versions of selected dependencies grouped by groupId.

Column: Maven Modules (Short)

Show project modules.

Column: Maven Modules (Version)

Show project module versions.

Column: Maven Dependencies (within groupId)

Show project dependencies within project groupId

Column: Maven Dependencies

Show all project dependencies

Column: Maven Modules (Full)

Show all project module info

Assign name from POM

Updates project Visible Name automatically from main module pom.xml (from tag <name>)

You can configure a template to generate name using the Token Macro Plugin in Job configuration page :

It's useful to show checked out branch or some other label.

By default module name is used.

Assign description from POM

Updates project Description automatically from pom.xml (from tag <description>)

You can configure a template to generate description using the Token Macro Plugin in Job configuration page :

By default "<pre>$MAIN_DESCRIPTION</pre>" is used.

Wish list

  • Last Release and Last Release dependencies columns
  • Exclude artifacts from selected dependencies column (multi pattern)


This plugin has some configuration at Job level.

You can find it at section:

It also haves a plugin configuration at Jenkins Configuration page:

Select main module

If project is a multi-module project then you can select which module is used to extract info (main module). If no module is specified or found then root module is used as main module.

It's useful if your root module has different version or if you want to focus only on one module.

To select a module as main module you can use a "module selector".

A module selector is a pattern of the form "groupId:artifactId". Both groupId and artifactId can contain wildcards (*). If groupId or artifactId is empty, they are treated as *.

So, valid expressions are "*:my-artifact", ":my-artifact*", "*.plugin:main", ...

If more than one module is selected, modules are sorted lexicographically and first one is selected.

You can configure the main module selector in Job configuration page (advaced options):

Select interesting dependencies

You can select which dependencies are interesting for you in a project.

It's useful to focus on some dependencies or dependency group (e.g.: commons-io version in all modules, spring framework dependencies, ...)

You can configure the dependencies selector in Job configuration page (advaced options):

Hide Snapshots

You can hide the annoying suffix "-SANPSHOT" of snapshot versions to improve version readability.

This can be done checking the checkbox at Plugin's Configuration section:

If you check it, versions will be shown without the suffix and using an alternate style:

instead of

Versions styles (CSS)

You can change the style of versions to improve readability.

As example, you can use green for releases and italic red for snapshots.

To do that you have two textboxes at Plugin's Configuration section:

Versions are rendered inside an <span> : E.g: <span>1.0.0</span>

CSS code entered here will apply only to this span.

Note: if you leave empty snapshot version style and hide snapshots is checked, a default style is applied.

Template Variables

In addition to Token Macro Plugin and extensions variables, templates can use the following variables:






Main module's name



Main module's description


Version 0.2.0

Version 0.1.3

Version 0.1.2

  • (info) Hide snapshots feature
  • (info) Assign style (css) to version columns
  • (info) Delay before showing info panels
  • (error) NoSuchElementException showing dependencies version
  • (smile) Improved readability of old columns (pre 0.0.5)

Version 0.1.1

  • (info) Column: Selected Dependencies Version
  • (error) Main Module Pattern not applied on Jenkins restart
  • (info) More verbose exception on POM parse error
  • (info) More verbose exception on pattern parse error
  • (info) Configurable caption for newest columns

Version 0.0.5

  • (info) Column: Selected Module Last Version
  • (info) Assign name from POM
  • (info) Assign description from POM
  • (smile) Changed default visibility of columns

Version 0.0.4 & previous

  • Column: Maven Modules (Short)
  • Column: Maven Modules (Version)
  • Column: Maven Dependencies (within groupId)
  • Column: Maven Dependencies
  • Column: Maven Modules (Full)


  1. Unknown User (michael.wenig@ww-informatik.de)

    Actually there is no component 'maven-info' in jira.

    If you have a maven multi-module-project the versions column displays the same version several times (for each module).

    Is there any development currently?

  2. Unknown User (michaelajr)

    Current version of hudson (1.392), shows all columns on the "All" view - and there is no way to edit! I am forced to disable this plugin until this issue is resolved.

    1. Unknown User (michaelajr)

      I was able to make an "All (Modified)" tab without the columns and set it as the default tab. So I guess this is not a huge deal.

  3. Unknown User (m2spring)

    It should be configurable to have the additional columns in the All view.

  4. Unknown User (dankirkd)

    The 0.1.2 update isn't being picked up by Jenkins which still lists it at 0.1.1

    1. Unknown User (dankirkd)

      It is now.

  5. Unknown User (dankirkd)

    I'm noticing with version 0.1.1 that the "Selected Dependencies" and "Selected Module Last Version" columns will not work unless you do a save of the job's configuration first.

    1. Unknown User (dankirkd)

      Still a problem with 0.1.2

      1. Unknown User (emenaceb)

        It should be fixed in version 0.2.0

  6. Unknown User (dankirkd)

    Version styles don't consider disabled jobs.  I think these shouldn't override the greyed out text color for disabled jobs as they currently do.

    Also, it would be really nice if the "Interesting Dependencies Pattern" could be set globally for all jobs as this, in our case, would be set to a dependency used by a ton of jobs.

    1. Unknown User (emenaceb)

      What about configuring it in view's configutation page? 

      1. Unknown User (dankirkd)

        If that were an option I think it would be fine.

  7. Unknown User (rrialq)

    It should be great if you add an option to assign the build name, including the version declared at pom. Something as:

    Assign build name from POM

    Default value should be: $MAVEN_NAME-$MAVEN_VERSION

    Where MAVEN_VERSION is the version of the (main) module.