This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Consider following use case (see JavaFX Profiler depending on Java Common API): - a module A has an implementation dependency on module B - we want to make A available through UC - either A has to be built with the original implementation version or - A and B have to be built together and published on UC at the same time. The problem when releasing and update and may happen if A has changed and B not, with only A having updated it's spec number. In such a case B won't be updated which results in unsatisfied implementation dependency. This has happened several times with the JavaFX Profiler example above. So whenever A and B are published on UC, it is necessary to check whether B has updated specification version even if it has not changed!!! I suggest to implement such a check as soon as possible to prevent possible regressions.
java.api.common specifies no numeric implementation version, so declaring an impl dep on it violates NB policy. Numeric implementation versions enable Auto Update to work sanely; see FAQ for complete explanation. Anyway java.api.common already lists javafx.profiler as a friend so no impl dep should be necessary. (If you are using nonexported packages from java.api.common, please cease immediately and get proper exported APIs for your needs when possible. I would check myself but building your sources seems to require at least one on-SWAN 87Mb download, which takes too long to consider. A quick search shows only a usage of UpdateHelper from org.netbeans.modules.java.api.common.ant, which is exported.)