Maven NetBeans Module Plugin

OpenIDE-Module-Public-Packages must always be added to module manifest

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.6
  • Fix Version/s: 3.0
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

See

http://www.netbeans.org/nonav/issues/show_bug.cgi?id=139966

for background. Whatever code in Maven creates NetBeans modules must be sure to always insert the OIDE-M-P-P attribute. The default should be "-" (i.e. do not export any packages) unless otherwise requested. Package wildcards ("something.*") are permitted but discouraged; explicit packages ("something.") preferred.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Milos Kleint added a comment -

Well, I'd like to have a reasonable default without the need to have additional configuration in place added by user (convention over configuration)

For that we could use "no public packages". That's fine for modules that just add some new functionality, but is really bad for modules that just wrap external libraries as netbeans modules (please note that this scenario is rather cumbersome in netbeans ant based projects)
The "something.* stuff requires you to have additiona configuration somewhere (manifest or elasewhere). The netbeans ant projects bypass the problem by additional tooling support which generates the entries.
So "empty" public packages value still seems to me like the best out of the box option that works for all cases without additional setup.

Please advise.

Show
Milos Kleint added a comment - Well, I'd like to have a reasonable default without the need to have additional configuration in place added by user (convention over configuration) For that we could use "no public packages". That's fine for modules that just add some new functionality, but is really bad for modules that just wrap external libraries as netbeans modules (please note that this scenario is rather cumbersome in netbeans ant based projects) The "something.* stuff requires you to have additiona configuration somewhere (manifest or elasewhere). The netbeans ant projects bypass the problem by additional tooling support which generates the entries. So "empty" public packages value still seems to me like the best out of the box option that works for all cases without additional setup. Please advise.
Hide
Permalink
Jesse Glick added a comment -

Again: whatever the decision about the pom.xml format, the Maven plugin must never generate a module that is lacking the OIDE-M-P-P attribute.

I still recommend that an empty package list ("-") be the default unless otherwise specified. If there is a common need to create library wrappers which export all packages (which is also suspect - in many cases only certain packages should really be exported), this can be handled either by an archetype which does the setup similarly to a project wizard in the IDE; or by a one-line marker in pom.xml which requests all packages to be exported.

Show
Jesse Glick added a comment - Again: whatever the decision about the pom.xml format, the Maven plugin must never generate a module that is lacking the OIDE-M-P-P attribute. I still recommend that an empty package list ("-") be the default unless otherwise specified. If there is a common need to create library wrappers which export all packages (which is also suspect - in many cases only certain packages should really be exported), this can be handled either by an archetype which does the setup similarly to a project wizard in the IDE; or by a one-line marker in pom.xml which requests all packages to be exported.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.