You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/06/02 08:01:00 UTC
[jira] [Resolved] (SLING-8738) Trigger an error during build if an
API uses a private reference in its public methods' signatures
[ https://issues.apache.org/jira/browse/SLING-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved SLING-8738.
------------------------------------
Resolution: Fixed
Fixed in https://github.com/apache/sling-parent/commit/2eca657b1774c5f2b800ba16676abc138640021c.
> 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: Konrad Windszus
> Priority: Major
> Fix For: Bundle Parent 43
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)