Major
Nice to have
Detail
Detail
#25930
Falsche Resource-Path-Reihenfolge im Build einer Anwendung
A deployed tl-demo has the (broken) glossy theme by default. From the dependencies, we would expect the Decent theme to be displayed by default.
In the deployed application, the Meta-Conf seems to have been assembled in the wrong order:
... reportingConf.xml modelWysiwygConf.xml wysiwygHighlighterConf.xml tl-themes-dezent.conf.xml <----- TLPerfConf.xml demoRemoteConf.xml tl.graph.diagramjs.server.xml monitoringConf.xml EWEConf.xml loginMessagesConf.xml themesGlossyConf.xml <----- modelSearchConf.xml tl-chartjs.config.xml tl-layout-formeditor.config.xml ...
Analysis
The problem is that the IDE and the build calculate the order of the configuration files in different ways. In the IDE, this is done by directly analyzing the Eclipse .classpath files. In the build, the configuration sequence is derived from the Ant4Eclipse "build order". However, this only arranges the projects in dependency order and does not determine a clear classpath order. It merely ensures that a build is possible in this order.
Solution: Use the same code in the build and IDE that calculates the resource path order.
Test
- Deploy tl-demo and log in as root.
- Expect the user to initially see the Decent theme.