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 211959 - Packages from JAR dependencies of NBM wrapper not offered for export in customizer
Summary: Packages from JAR dependencies of NBM wrapper not offered for export in custo...
Status: NEW
Alias: None
Product: apisupport
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.2
Hardware: All All
: P4 normal with 2 votes (vote)
Assignee: Milos Kleint
URL:
Keywords:
: 213553 (view as bug list)
Depends on:
Blocks: 201099
  Show dependency tree
 
Reported: 2012-05-02 11:48 UTC by toben
Modified: 2012-06-19 14:58 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description toben 2012-05-02 11:48:42 UTC 
Product Version = NetBeans IDE Dev (Build nbms-and-javadoc-9263-on-20120501)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_03
Runtime = Java HotSpot(TM) 64-Bit Server VM 22.1-b02

Hallo,

building an RCP application I need to specify public packages for my modules. The option to select public packages of my module displays 
only packages already specified in pom for public usage. I am unable to define new public packages using the options dialog. I have to specify
it in my pom. This works in netbeans 7.1.x.

Tobias
Comment 1 toben 2012-05-02 12:52:01 UTC 
For clarification. This seems to happen only for wrapper modules. I want to make a jars package public. With "normal" modules all packages of this actual modul are presented.
Comment 2 Jesse Glick 2012-05-03 18:15:13 UTC 
Yes, this was changed intentionally - for many cases the list of packages was overwhelming as it was taken from all transitive dependencies. So the customizer was changed to show just packages physically present in the source project; any others you can add directly in the POM.

For some cases certain dependencies would better be shown but it is not obvious what the right behavior should be. One possible change is to show packages from all dependencies if there are no packages in sources at all, though this breaks down when you add a minor helper class to the wrapper module (even just a ModuleInstall that you would not want to export but need to have present). Showing only direct dependencies would be rather arbitrary. As bug #201099 comment #2 notes, you might want to discriminate by packaging type of dependency, following the fairly complex algorithm that nbm-maven-plugin itself uses to decide what will be a Class-Path extension; unclear if there is an equivalent for OSGi bundles.
Comment 3 toben 2012-05-04 07:30:03 UTC 
What about a simple CheckBox (only project packages / all packages) with a default behaviour like you described it:

1. Module with no local sources: all packages (checkbox disabled)
2. Module with local source: only modul packages (checkbox enabled)

So you have the "right" filtered view but more if you wish.
Comment 4 Jesse Glick 2012-05-04 13:56:37 UTC 
Might work. Not for 7.2.
Comment 5 Jesse Glick 2012-06-04 22:35:32 UTC 
*** Bug 213553 has been marked as a duplicate of this bug. ***