[
https://issues.apache.org/jira/browse/SLING-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227401#comment-17227401
]
Bertrand Delacretaz commented on SLING-2938:
--------------------------------------------
I have tried moving the integration tests in the main module, running them with
maven-invoker-plugin and I think that looks good, what do people think?
[https://github.com/apache/sling-org-apache-sling-adapter-annotations/pull/1/files]
Having the tests in the same repository provides quicker feedback when making
changes, and with the invoker plugin they remain decoupled from the main code.
If we agree we can merge that PR and deprecate the annotations-it module.
> AdapterMethods annotation and adapter proxy service
> ---------------------------------------------------
>
> Key: SLING-2938
> URL: https://issues.apache.org/jira/browse/SLING-2938
> Project: Sling
> Issue Type: Bug
> Components: Engine, Extensions
> Affects Versions: Adapter 2.1.0
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: SLING-2938-api.patch, console.jpg
>
>
> Following up on an idea that Olaf Otto presented at CQCon last week, I've
> been working on an @AdapterMethod annotation that makes it easier to create
> Sling adapters, as in
> @Component
> @Service
> public class MyAdapters implements AdapterMethodProvider {
> @AdapterMethod
> public Bar toBar(Foo f) { ... adapt Foo to Bar ... }
> }
> As this requires changes to the sling.api bundle, I'll commit to my
> whiteboard first, for review
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
