[mojo-dev] [jira] (MCLIRR-53) Change of return type can't be ignored in some cases

Thu, 15 Nov 2012 02:26:35 -0800

Issue Type: Bug Bug
Affects Versions: 2.5
Assignee: Unassigned
Attachments: fluent-methods-support.patch
Created: 15/Nov/12 4:23 AM
Description:

If a method returns the defining class instance or a subclass of the defining class, a return type change cannot be ignored on it.

Example:

class A {
   class B {}

   A m() {
      return null;
   }

   B n() {
     return null;
   }
}
class A {
   String m() {
      return null;
   }

   String n() {
      return null;
   }
}
<difference>
   <className>A</className>
   <differenceType>7006</differenceType>
   <method>A m()</method>
   <to>java.lang.String</to>
</difference>

<difference>
   <className>A</className>
   <differenceType>7006</differenceType>
   <method>A$B n()</method>
   <to>java.lang.String</to>
</difference>

I expanded the MCLIRR-48 tests to include the above scenario.

Note that the patch will produce an integration test failure unless the patch from MCLIRR-52 is applied, too. This is because, for some reason, I needed to change the executed phases of the integration tests from clean,verify to clean,install for the setup-MCLIRR-48 artifact to be available during the later phase of the integration tests. This change then exposes the java1.4->java5 conversion error described in MCLIRR-52.
Project: Maven 2.x Clirr Plugin
Priority: Major Major
Reporter: Lukas Krejci
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to