You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/10/20 15:47:27 UTC

[jira] Created: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

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.


[jira] Resolved: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved FELIX-2669.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: scr annotations 1.3.2
                   scr generator 1.0.0
                   scr ant task 1.0.0

Reafctoring is complete and seems working properly.

> 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, scr ant task 1.0.0, scr generator 1.0.0, scr annotations 1.3.2
>
>
> 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.


[jira] Closed: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed FELIX-2669.
------------------------------------


Close after release

> 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.6.0, scr ant task 1.0.0, scr generator 1.0.0, scr annotations 1.4.0
>
>
> 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.


[jira] Commented: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923421#action_12923421 ] 

Felix Meschberger commented on FELIX-2669:
------------------------------------------

Fixed and updated legal files in Rev. 1025968

> 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, scr ant task 1.0.0, scr generator 1.0.0, scr annotations 1.3.2
>
>
> 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.


[jira] Commented: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923400#action_12923400 ] 

Felix Meschberger commented on FELIX-2669:
------------------------------------------

Refactored the modules as described above:

 Rev. 1025935 moved SCR plugin code down to scrplugin/maven-scr-plugin
 Rev. 1025937 moved scr.annotations down to scrplugin/annotations
 Rev. 1025938, 1025941, 1025943, 1025944, cleanup of dependencies and code
 Rev. 1025950 removed empty directories remaining after moving the code/projects
 Rev. 1025952 removed scr-annotations module from main reactor

> 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.


[jira] Commented: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923355#action_12923355 ] 

Felix Meschberger commented on FELIX-2669:
------------------------------------------

Reconsidering the reorganization, I think we should leave the scr module implementing the DS specification where it is a move the plugin/task stuff into the scrplugin folder:

    trunk/scrplugin
             +--- generator  --  The core descriptor generator stuff
             +--- annotations  --  The core annotations along with the per-annotation JavaTag support classes
             +--- maven-scr-plugin  --  The Maven Plugin
             +--- scrtask  --  The Ant Task

As a consequence the scr.annotations module will thus be moved into the trunk/scrplugin/annotations folder and merged with the annotation supprt classes currently located in the scrplugin module and thus finally put together stuff, that belongs together.

> 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.


[jira] Issue Comment Edited: (FELIX-2669) Split Maven SCR Plugin and reorganize SCR modules

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923421#action_12923421 ] 

Felix Meschberger edited comment on FELIX-2669 at 10/21/10 8:30 AM:
--------------------------------------------------------------------

Fixed and updated legal files in Rev. 1025968 and ensured inclusion of DEPENDENCIES files in Rev. 1025971

      was (Author: fmeschbe):
    Fixed and updated legal files in Rev. 1025968
  
> 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, scr ant task 1.0.0, scr generator 1.0.0, scr annotations 1.3.2
>
>
> 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.