You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/10/19 12:30:05 UTC

[jira] [Resolved] (SLING-5170) Make dependency handling code more reusable

     [ https://issues.apache.org/jira/browse/SLING-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-5170.
-------------------------------------
    Resolution: Fixed

I moved most of the code into a separate Modelpreprocess class which can be subclassed to customize
Rev 1709384

> Make dependency handling code more reusable
> -------------------------------------------
>
>                 Key: SLING-5170
>                 URL: https://issues.apache.org/jira/browse/SLING-5170
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Slingstart Maven Plugin 1.3.8
>
>
> If you want to build other maven plugins dealing with the provisioning model, it's currently a little bit hard to reuse the dependency lifecycle handler and extend it's functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)