Apex Code Development You need to sign in to do that
Don't have an account?
jwhartfield Package Version always includes non-referenced installed package
I just installed a managed package (EasyPage) into our ORG. After installing, anytime I make a new class or page the 'EasyPage' managed package is included in the list of dependencies found under in the 'Version Settings' tab of these new classes or pages. These classes/pages are completely blank, so there are no actual dependencies on anything. I tried to use Eclipse to tweak the XML and remove the dependency, but the VersionSettings keeps on coming back when I save.
Does anybody know why this might be happening? Is this behavior by design?