Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect changes to inner modules #143

Merged

Conversation

szeiger
Copy link
Contributor

@szeiger szeiger commented Nov 18, 2016

Updated version of #128 to fix #127

@szeiger szeiger added this to the 0.1.12 milestone Nov 28, 2016
@SethTisue
Copy link
Collaborator

SethTisue commented Nov 29, 2016

review by @retronym (as per team meeting) — on a fast track for 2.11.9 + 2.12.1

@retronym
Copy link
Contributor

LGTM, but needs a rebase.

dotta and others added 2 commits November 30, 2016 12:32
…abs#127

The former implementation of PackageInfo#accessibleClasses expects that for any
module `Foo` compiled by scalac, both `Foo.class` and `Foo$.class` classfiles
are produced. Because `Foo$.class` and `Foo.class` are essentially mirrors, and
users never access directly `Foo$.class`, MiMa only traverses the `Foo.class`. This
works well for top-level modules, but it breaks for inner modules, because no
mirror class is created for inner modules (only the module class is created).

The fix consist in treating inner modules differently, hence making sure inner
modules are part of the set returned by PackageInfo#accessibleClasses.
@szeiger szeiger force-pushed the issue/127-removing-inner-object branch from 446df27 to 615b35a Compare November 30, 2016 11:42
@szeiger szeiger merged commit 014b33f into lightbend-labs:master Nov 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

mima failed to detect a removed inner object of an object
4 participants