Bug 517034

Description Speiger Bär 2017-05-21 14:03:41 EDT

Well this sound confusing but when i used Eclipse Juno i was able to override methodes with custom @Interfaces applied to them and Eclipse Juno was able to transfer these over to the overriden class.

When i updated to Eclipse Neon that was no longer the case, and i am really missing that feature because when i use a @Interface for a function i would like to use those at all overriden cases.

To give an example:
public class BaseClass
{
    @SideOnly(Side.CLIENT)
    public void onClientTick()
    {
    }
}


public class JunoClass extends BaseClass
{
     @Override
     @SideOnly(Side.CLIENT)
     public void onClientTick()
     {
     }
}

public class NeonClass extends BaseClass
{
    @Override
    public void onClientTick()
    {
    }
}

The NeonClass represents the Eclipse Neon program and the JunoClass represents the Eclipse Juno Program.

And this is what happens automaticly when you override a function with a custom @Interface.

My Envioment actually requires that for functions in the classes to be present at any given time even overrides. That is what my system is build on.
And i kinda want to have that feature + what Eclipse Neon provides me.
Because i cant live without both xD

I wonder if that feature was disabled and could be enabled again ^^"