Split Maven SCR Plugin and reorganize SCR modules
-------------------------------------------------
Key: FELIX-2669
URL: https://issues.apache.org/jira/browse/FELIX-2669
Project: Felix
Issue Type: Task
Components: Maven SCR Plugin
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: maven-scr-plugin-1.4.6
FELIX-2642 exhibited issues with the current Maven SCR Plugin with respect to
extensibility and reuse of the core functionality in other environments than
Maven. While FELIX-1684 laid out the basis for reuse, there are still some open
points. See also the dev@ thread at
http://markmail.org/message/aqpdbu4wjaphmfrr.
This task issue is about refactoring the Maven SCR Plugin and probably
restructuring everything related to this plugin:
* Create a maven module with just the core descriptor generation
implementation
* Refactor current scrplugin module to just be the Maven Plugin part
* Create a maven module for just the Ant Task part
* Create a maven module with the DefaultAnnotationTagProvider
* Consider moving the SlingAnnotationTagProvider back to the Sling project
In addition everything "SCR" might be reorganized below a new trunk/scr folder
like this:
trunk/scr/scr -- The Declarative Services implementation (formerly
trunk/scr)
trunk/scr/descriptorgenerator -- The core descriptor generation (formerly
part of the plugin)
trunk/scr/maven-scr-plugin -- The Maven plugin (formerly trunk/scrplugin)
trunk/scr/ant -- The Ant Task (formerly part of the plugin (as of
FELIX-2642))
trunk/scr/annotations -- The default annotations (formerly
trunk/scr-annotations)
Discussion: maybe the location of the descriptor support stuff inside an "scr"
folder is inappropriate because the functionality may just as well be used to
create a MetaType service descriptor without even using Declarative Services at
all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
