[
https://issues.apache.org/jira/browse/SLING-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353111#comment-17353111
]
Konrad Windszus commented on SLING-8738:
----------------------------------------
As I fear that bnd won't allow a better method soon, I would actually like to
include the `-fixupmessages` instruction in upcoming parent release. [~radu]
WDYT?
The code proposed at
https://github.com/bndtools/bnd/issues/3444#issuecomment-534087739 seems safe
enough:
{code}
-fixupmessages:"Export *, has \\d+, private references"; \
restrict:=warning; \
is:=error
{code}
> Trigger an error during build if an API uses a private reference in its
> public methods' signatures
> --------------------------------------------------------------------------------------------------
>
> Key: SLING-8738
> URL: https://issues.apache.org/jira/browse/SLING-8738
> Project: Sling
> Issue Type: Improvement
> Components: General
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Bundle Parent 43
>
>
> Following the discussion from https://github.com/bndtools/bnd/issues/3444, we
> should add the provided {{-fixupmessages}} instruction to our bundle parent
> pom, in order to make sure that APIs that we export cannot reference private
> references in their public method signatures.
> This is more of a precaution, rather than a fix for a Sling issue.
> Projects using the bundle parent pom can override the bnd instruction
> locally, if needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
