You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@yetus.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/09/22 13:59:00 UTC

[jira] [Updated] (YETUS-549) Provide a maven enforcer plugin example that limits a downstream project to particular Audience Annotations

     [ https://issues.apache.org/jira/browse/YETUS-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated YETUS-549:
------------------------------
    Description: 
It would be very nice for those that annotate their public API via the audience annotations if they could tell their downstream users "here's how you fail your build if you start using things outside of what we consider Public."

It might be messy / not useful if folks mix and match Public / not Public in their api (for example, having an Public method that returns an Private object), but that's a horse of a different color (Apilyzer might help them clean that up)

  was:
It would be very nice for those that annotate their public API via the audience annotations if they could tell their downstream users "here's how you fail your build if you start using things outside of what we consider Public."

It might be messy / not useful if folks mix and match Public / not Public in their api (for example, having an IA.Public method that returns an IA.Private object), but that's a horse of a different color (Apilyzer might help them clean that up)


> Provide a maven enforcer plugin example that limits a downstream project to particular Audience Annotations
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: YETUS-549
>                 URL: https://issues.apache.org/jira/browse/YETUS-549
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Audience Annotations
>    Affects Versions: 0.5.0
>            Reporter: Sean Busbey
>
> It would be very nice for those that annotate their public API via the audience annotations if they could tell their downstream users "here's how you fail your build if you start using things outside of what we consider Public."
> It might be messy / not useful if folks mix and match Public / not Public in their api (for example, having an Public method that returns an Private object), but that's a horse of a different color (Apilyzer might help them clean that up)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)