[
http://jira.amdatu.org/jira/browse/AMDATU-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10093#action_10093
]
Marcel Offermans commented on AMDATU-64:
----------------------------------------
I cannot stress enough that we should never, ever rely on start levels to solve
ordering issues. In other words, if the startup order is causing problems,
something else is seriously wrong and you should spend some time trying to fix
that.
The only thing start levels can do is "streamline" the startup process by
defining an order, but that is probably largely irrelevant since we tend to
have extremely long running instances (cloud nodes) that might get updated
multiple times during their life time (using provisioning).
So I would propose removing start levels altogether.
> Newly installed bundles are assigned start level 1
> --------------------------------------------------
>
> Key: AMDATU-64
> URL: http://jira.amdatu.org/jira/browse/AMDATU-64
> Project: Amdatu
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 0.0.4
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Priority: Minor
> Fix For: 0.0.5
>
> Attachments: AMDATU-64.patch
>
>
> When bundles are installed using the fileinstall bundle and copying them to
> the deploy directory, they are assigned start level 1 instead of the expected
> start level 40
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.amdatu.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
