Maven 2 & 3

Create a CLIRR/JarDiff setup for 2.0.x and 3.0.x

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0.10, 2.1.0-M1
  • Component/s: Bootstrap & Build
  • Labels:
    None
  • Number of attachments :
    0

Description

It may not only be for the core but also the plugin tools that have been separated.

Issue Links

This issue duplicates:
MNG-3011 Generating API differences between 2.0.x and 2.1 Minor Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Siveton added a comment -

In mojo land, we have both plugins but only clirr-maven-plugin was released, the other one is in the sandbox.
I propose to configure only the clirr report in the maven-parent: this report will be available here [1]. WDYT?

[1] http://maven.apache.org/ref/current

Show
Vincent Siveton added a comment - In mojo land, we have both plugins but only clirr-maven-plugin was released, the other one is in the sandbox. I propose to configure only the clirr report in the maven-parent: this report will be available here [1]. WDYT? [1] http://maven.apache.org/ref/current
Hide
Permalink
Brett Porter added a comment -

seems like a good place to start.

Show
Brett Porter added a comment - seems like a good place to start.
Hide
Permalink
Vincent Siveton added a comment -

added clirr report in the maven-parent (r609317)

Show
Vincent Siveton added a comment - added clirr report in the maven-parent (r609317)
Hide
Permalink
Brian Fox added a comment -

is this resolved then?

Show
Brian Fox added a comment - is this resolved then?
Hide
Permalink
Brett Porter added a comment -

we should run it once before the release to check the API is still compatible.

This should really be automated, but that's a much bigger issue and not one for targeting at a particular release.

Show
Brett Porter added a comment - we should run it once before the release to check the API is still compatible. This should really be automated, but that's a much bigger issue and not one for targeting at a particular release.
Hide
Permalink
John Casey added a comment -

confirmed that this is running in ci, release, and reporting profiles.

Show
John Casey added a comment - confirmed that this is running in ci, release, and reporting profiles.
Hide
Permalink
John Casey added a comment -

Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

Show
John Casey added a comment - Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.