[
https://issues.apache.org/jira/browse/FELIX-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761568#action_12761568
]
Felix Meschberger commented on FELIX-1684:
------------------------------------------
Implemented first shot in Rev. 820997:
* Isolated all dependencies inside the o.a.f.scrplugin.mojo package
* Provide glue interfaces for logging and descriptor reading
To reuse the functionality in a non-Maven environment do the following:
* Implement the Log interface for the log mechanism of your environment
* Extend the JavaClassDescriptorManager implementing the abstract methods
getSource() -- get JavaSource instances for the classes to contribute
to the descriptors
getComponentDescriptors() -- get existing descriptors from extended
classes
* Create a SCRDescriptorGenerator instance, set it up calling the setter
methods and call execute()
See the o.a.f.scrplugin.mojo package for the Maven-based implementations and
use.
> Refactor to use core functionality in non-Maven contexts
> --------------------------------------------------------
>
> Key: FELIX-1684
> URL: https://issues.apache.org/jira/browse/FELIX-1684
> Project: Felix
> Issue Type: Improvement
> Components: Maven SCR Plugin
> Affects Versions: maven-scr-plugin-1.4.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: maven-scr-plugin-1.4.1
>
>
> Currently the JavaDoc tag and annotation processing to generate SCR
> declarations is heavily dependend on Maven plugin functionality. This
> prevents the re-use of the central SCR declaration generation in non-Maven
> contexts such as Ant tasks or IDE integrations.
> To do this, we have to extract common functionality and separate the Maven
> specific stuff out
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
