Ok, I verified this and it does solve the problem. In other words, moving BaseAggregator to the util package works, even when BaseAggregator is package protected (i.e. not public).
So... can we move this, please? Cheers, Dave On Fri, 2007-06-15 at 12:45 +0200, Niclas Hedhman wrote: > On 6/15/07, David Leangen <[EMAIL PROTECTED]> wrote: > > > > BaseAggregator is in the "internal" package, which is not exported. > > > > In Eclipse, this means that any time I try to use a method (like > > getApplicationName() ), I am getting an AccessRestrictionException and > > my code does not compile. > > > > > > I understand that this is an Eclipse bug, but in the meantime, can we > > please move BaseAggregator to the util package? > > Before attempting a half-hearted effort, could you check if it would > work with a non-public BaseAggregator in util package?? I suspect > that that won't work either, and I definately don't want to open > BaseAggregator up for public subclassing. > if that won't work either, the only other thing I see happening is to > take away the BaseAggregator, and replace it with a class that each of > the subclasses delegates all the method calls to. Not very pretty... > > Cheers > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
