Maven 2.x Project Info Reports Plugin

Create a new report to show how to include the module in different build systems

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.5
  • Fix Version/s: 2.5
  • Component/s: dependency-info
  • Labels:
    None
  • Number of attachments :
    1

Description

Different Maven Repositories usually show an info section to show how to include the found artifact in different build systems (Maven, Ivy, ...), it would be nice having it directly in the documentation site as well

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MPIR-250 dependency-info packaging information broken: displays "${project.packaging"

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MPIR-249 new dependency-info report not added to goals index page

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Simone Tripodi added a comment -

fixed on r1206503

Show
Simone Tripodi added a comment - fixed on r1206503
Hide
Permalink
Simone Tripodi added a comment -

fixed on trunk

Show
Simone Tripodi added a comment - fixed on trunk
Hide
Permalink
Christian Schlichtherle added a comment - - edited

Nice report. However, it doesn't always seem to work, at least not for packaging type "pom". Note the corrupt type information in the attached screenshot.

Show
Christian Schlichtherle added a comment - - edited Nice report. However, it doesn't always seem to work, at least not for packaging type "pom". Note the corrupt type information in the attached screenshot.
Hide
Permalink
Simone Tripodi added a comment -

Thanks for reporting Christian, looks like the project.packaging property was a corrupted, see modifications on r1369732

Do you have any chance to test it against latest snapshot? You may have to rebuilt it locally first.

TIA!

Show
Simone Tripodi added a comment - Thanks for reporting Christian, looks like the project.packaging property was a corrupted, see modifications on r1369732 Do you have any chance to test it against latest snapshot? You may have to rebuilt it locally first. TIA!
Hide
Permalink
Christian Schlichtherle added a comment -

Thank you very much for the quick fix. I'm afraid building Maven components is beyond me - sorry!

Show
Christian Schlichtherle added a comment - Thank you very much for the quick fix. I'm afraid building Maven components is beyond me - sorry!
Hide
Permalink
Simone Tripodi added a comment -

You are welcome!

I may can help you on leading how to test it:

  • get into the directory and run mvn install;
  • in your project's pom.xml file, upgrade the maven-project-info-reports-plugin declared version to 2.6-SNAPSHOT;
  • open the shell in your project's location and run mvn site.

HTH!

Show
Simone Tripodi added a comment - You are welcome! I may can help you on leading how to test it: open the shell and run svn co https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin ; get into the directory and run mvn install ; in your project's pom.xml file, upgrade the maven-project-info-reports-plugin declared version to 2.6-SNAPSHOT ; open the shell in your project's location and run mvn site . HTH!

People

  • Assignee:
    Simone Tripodi
    Reporter:
    Simone Tripodi
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: