[GROOVY-8286] Groovy does not respect package-private modifier of Java class

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Information Provided
• Affects Version/s: 2.4.8
• Assignee: Unassigned
• Reporter: Angela Guardian
• Created: 11/Aug/17 07:46
• Updated: 05/Oct/24 19:20
• Resolved: 05/Oct/24 19:20

Description

Hi. I'm using Java (1.8) with Groovy (2.4.8) via GMavenPlus (although with the project I'm working on, we actually also programmatically compile Groovy code and add it to the class loader to mix them up). It seems however, in Groovy scripts/classes, package-private methods defined in a Java class can be called.

For example, I have a Java class Person in package org.example.people, defined like so:

package org.example.people;

public class Person {
    private String name;

    void setName(String name) {
        this.name = name;
    }

    public String getName() {
        return this.name;
    }
}

And I have a Groovy class Main in package org.example:

package org.example

import groovy.transform.CompileStatic
import org.example.people.Person

class Main {
    static void main(String[] args) {
        Person person = new Person()
        person.setName('Bob') // Shouldn't be call-able since they belong to different packages.
        println person.getName() // Prints 'Bob' to the console.
    }
}

Is this standard? Using @CompileStatic, though, throws an IllegalAccessException.

Issue Links

• relates to: GROOVY-10198 Extending a class via its superclass' metaclass changes method visibility rules