[
https://issues.apache.org/jira/browse/LABS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jan iversen closed LABS-383.
----------------------------
Resolution: Won't Fix
outdated and closed, if not correct please reopen.
> [build] Enforce implementations on api packages
> -----------------------------------------------
>
> Key: LABS-383
> URL: https://issues.apache.org/jira/browse/LABS-383
> Project: Labs
> Issue Type: Improvement
> Components: Magma
> Affects Versions: Current
> Reporter: Simone Gianni
> Fix For: Next
>
>
> Some packages are apis, like foundation-database. They does not work out of
> themself, they need to compose with their implementations (like
> database-openjpa) to be functional. There should be a maven goal that checks
> for these situations, warning the user or blocking completely in the case
> where an api package is present without any implementation.
> The problem is how to identify these api-only packages and how to propose
> possible implementations.
> The pom is not extensible to support such additional informations (at least
> not in maven 2.x), so an additional file should be added in the jar, telling
> that the package is api only. Possible implementations could be placed in
> that file in first phase. Obviously this creates a coupling where for each
> new implementation the api file must be updated, but we can survive this
> right now.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
