You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2014/11/19 10:32:34 UTC
[jira] [Resolved] (SLING-4180) Sightly Engine should properly
reimport its own API export
[ https://issues.apache.org/jira/browse/SLING-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-4180.
--------------------------------------
Resolution: Fixed
Thanks for providing the patch. I have applied it in Rev. 1640508.
(I did not annotate the exceptions yet, because I am not sure, whether these should really be annotated at all).
> Sightly Engine should properly reimport its own API export
> ----------------------------------------------------------
>
> Key: SLING-4180
> URL: https://issues.apache.org/jira/browse/SLING-4180
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.0
> Reporter: Radu Cotescu
> Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.0
>
>
> The Sightly API needs to be cleaned up such that the import versions are properly set by marking all interfaces as either {{@ConsumerType}} or {{@ProviderType}}.
> The package export should be defined with a {{package-info.java}} file instead of in the {{pom.xml}} such that the export is close to the source.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)