| Summary: | Change Export-Package: rules from internal* to internal.* | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Markus Keller <markus.kell.r> |
| Component: | EBR | Assignee: | Gunnar Wagenknecht <gunnar> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, gunnar |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Keller
Do the other instructions for "about" files really make sense? Export-Package: \ !about.html,!about_files, \ AFAICS, the first one tries not to export package "about.html" (not relevant, we only have a *file* called "about.html"), and the second one would better use .* I.e. make it: Export-Package: \ !about_files.*, \ (In reply to Markus Keller from comment #2) > Do the other instructions for "about" files really make sense? > > Export-Package: \ > !about.html,!about_files, \ > > AFAICS, the first one tries not to export package "about.html" (not > relevant, we only have a *file* called "about.html"), and the second one > would better use .* So bnd did not seem to be smart enough back in the day when I added them to the template. It did export "about.html" and "about_files" as a package when those files were present on the bundle classpath. However, I haven't tested again with the latest versions of the Maven bnd plug-in that we are using now. |