[jira] [Resolved] (ACE-627) Allow ordering of artifacts to be defined.

["J.W. Janssen (JIRA)" <ji...@apache.org>]

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

J.W. Janssen resolved ACE-627.
------------------------------
    Resolution: Fixed

I've provided a simple solution in rev #1802921. Basically, you can register a custom {{ArtifactDataHelper}} that is called by a {{DeploymentProvider}} right before it returns the list of collected artifacts to the service that creates a deployment package. As such, you can use it to define a particular order in which artifacts should appear.

> Allow ordering of artifacts to be defined.
> ------------------------------------------
>
>                 Key: ACE-627
>                 URL: https://issues.apache.org/jira/browse/ACE-627
>             Project: ACE
>          Issue Type: New Feature
>          Components: Deployment
>            Reporter: J.W. Janssen
>
> If ACE is used to provision a non-OSGi target, it might be that the deployment package contains resources that need a particular ordering before they can be correctly processed. For example, consider a WAR file that needs to access certain configuration files prior to starting. This implies that the configuration needs to be processed *before* the WAR file is to be processed.
> The solution could be as simple as allowing the order in which artifacts appear in the deployment package to be defined/tuned somewhere. Alternatively, we could provide a kind of API that allows you to define the order in which artifacts are to be included in the deployment package.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)