#1 member access

[Jeff Knox]

This is a minor design point:
I am extending the functionality of CrontabEntry for
some custom scheduling behavior. In order to use my
new CrontabEntry subclass, I must extend Crontab and
override newCrontabEntry (...). Fine, since
newCrontabEntry is given protected access-- but it
references the member threadGroup which has only
package visibility.

The workaround is simple-- the subclass of Crontab is
given it's own member threadGroup-- but this is
duplication of code and would be cleaner if
Crontab.threadGroup simply had protected access.

This is a quality product-- thanks!
Jeff