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.

Bug 189089 - Need a check for implementation dependencies when generating UC
Summary: Need a check for implementation dependencies when generating UC
Status: RESOLVED INVALID
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: PC All
: P1 normal (vote)
Assignee: nbbuild-issues@ide
URL: http://wiki.netbeans.org/DevFaqImplem...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-30 16:01 UTC by Martin Ryzl
Modified: 2010-07-30 17:28 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ryzl 2010-07-30 16:01:33 UTC
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.
Comment 1 Jesse Glick 2010-07-30 17:28:20 UTC
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.)