You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Dominik Przybysz (JIRA)" <ji...@apache.org> on 2016/06/20 20:40:58 UTC
[jira] [Commented] (ARIES-1570) Prepare extension machanism in
blueprint maven plugin
[ https://issues.apache.org/jira/browse/ARIES-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340355#comment-15340355 ]
Dominik Przybysz commented on ARIES-1570:
-----------------------------------------
I am working on my repo at github [1]. When it will be ready, I will create pull request and ask for review.
[1] https://github.com/alien11689/aries/tree/ARIES-1570
> Prepare extension machanism in blueprint maven plugin
> -----------------------------------------------------
>
> Key: ARIES-1570
> URL: https://issues.apache.org/jira/browse/ARIES-1570
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Affects Versions: blueprint-maven-plugin-1.4.0
> Reporter: Dominik Przybysz
> Assignee: Dominik Przybysz
> Fix For: blueprint-maven-plugin-1.5.0
>
>
> Goals:
> - create SPI for processing external annotations on classes, methods, constructors, fields
> - move Spring annotation handling to separate package and let it implement SPI
> - move bleurpint plugin core (handling javax.** annotations and maven specific parts) to separate package - impl
> Packages structures should look like:
> - core
> - spi
> - spring
> core package will use only spi package and will not use/know classes from spring package.
> spring package will not use core clases, it will only implement interfaces from spi package.
> All currently green tests should pass after these changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)