Correcting declared compile-time dependencies to match what the compiler BLD200512301900
authorjglick@netbeans.org
Fri, 30 Dec 2005 07:41:09 +0000
changeset 6708aa6bee3c05d8
parent 6707 778b02c40e51
child 6709 23c7e34ce67a
Correcting declared compile-time dependencies to match what the compiler
actually needs, in preparation for #59792. In some cases this reveals API usage
flaws. Typically corrections consist of
1. Undeclared usage of packages from lib/*.jar or core/*.jar.
2. Usage of a public class which extends an inaccessible class.
3. Usage of a constant from an inaccessible class (inlined, so irrelevant at runtime).
4. Unused dependencies which would have been illegal had they been used.
Module authors are strongly encouraged to review the new ide/golden/*.txt and
try to properly fix some of the problematic cases (e.g. #2, #3).
jmiutils/nbproject/project.xml
     1.1 --- a/jmiutils/nbproject/project.xml	Fri Dec 30 05:41:32 2005 +0000
     1.2 +++ b/jmiutils/nbproject/project.xml	Fri Dec 30 07:41:09 2005 +0000
     1.3 @@ -52,6 +52,7 @@
     1.4                  <!-- BUT javac (in JDK 1.4 at least) wants to access the superclass, meaning you need to have a compile dep on this module. -->
     1.5                  <!-- Which is funny, since the client will not be able to actually access MetamodelManager directly without an impl dep. -->
     1.6                  <!-- This situation is a violation of the basic rule that an exposed API must not refer directly to an API-inaccessible class. -->
     1.7 +                <package>org.netbeans.lib.jmi.util</package>
     1.8              </public-packages>
     1.9              <class-path-extension>
    1.10                  <runtime-relative-path>ext/jmiutils.jar</runtime-relative-path>