You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2017/07/25 10:28:00 UTC

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

J.W. Janssen created ACE-627:
--------------------------------

             Summary: 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)