#29789 tl:generate-java fails on the first build after a TopLogic version change: it neither resolves the engine web fragments nor reads the project's own model sources

enhancement

major

#29659

TL Views: Popover-Element mit beliebigem Inhalt an einer auslösenden Schaltfläche

#29713

TL Views: a user cannot hide a tile of a <dashboard> and add it again later

#29755

React-UI: Auswahl in Objektlisten (<object-list selection>) – Karten direkt anwählbar

#29756

React view table: Excel export (parity with classic TableComponent) and generic download view action

#29757

React view table: show row count (total / filtered / selected) like the classic table

#29776

TL Views: Einheitliches Drag & Drop für Tabellen, Baum-Tabellen, Bäume und Kanban-Boards mit mehreren Drop-Operationen, Drop-Positionen und Drag-Arten

#29782

Concept: Discover right for the model based security (filtered object sources, masked form fields)

#29785

OpenAPI server: request bodies are not validated against the declared schema

#29786

MUI: Avatar (TLAvatar) mit Material UI darstellen

#29787

React UI: Atomare Bausteine (Schaltflächen, Menü-Auslöser, Checkboxen, Eingabefelder, Chips, …) sehen überall gleich aus und lassen sich durch eine Komponentenbibliothek (z.B. Material UI) ersetzen

#29797

XML import into existing data: resolve IDs against existing objects, skip known subtrees, optional references, language and variables from the input

#29799

Form dependencies: derived fields do not follow edited values; Java script functions cannot report what they read to the ScriptTracer

#29811

TL Views: a <button> ignores the display mode of its command and always shows icon and label

#29812

TL Views: a table column declares its own comparator; enumeration columns follow the enumeration's order

#29814

TL Views: no supported way for a server-side background source (a bus listener) to push a channel value into a view; only <start-job> does it through internal API

#29815

TL Views table: no per-row CSS class (a row cannot be marked as changed, stale or own)

#29816

TL Views table: a <computed-column> cannot be hidden by default (shown only through the column chooser)

#29821

Design System wave 3b: table, tree, column selection and text read the design system package

#29825

Design System: column selection of the React table – grouping as one select, checkbox first, visible and hidden columns apart

#29829

TL Views: Beschreibbarer Kanal, der aus anderen Kanälen vorbelegt wird

#29830

Transaction monitor: Select a time range or a revision range instead of a single day.

#29836

Design System wave 4a: dialog, window, drawer, snackbar and notice bar read the design system package

#29840

Persistent object wrapper hierarchy: remove dead and duplicated code, move stateless behavior into interface defaults, replace class identity checks

#29849

Configuration: an encrypted property value that is not a valid encrypted value is silently "decrypted" to garbage instead of being rejected

#29854

PowerPoint-Präsentationen aus TL-Script erzeugen: deklarative Folienbausteine, Export in eine Firmenvorlage, Analyse von Vorlagen

#29858

Privileged TL-Script functions: authorize a configured script as a whole by a command group on a computed security object

#29859

React-Einfachauswahl: Die aktuell gewählte Option fehlt in der Optionsliste

#29866

Design System wave 4b: app shell, app bar, sidebar and bottom bar read the design system package

#29870

Design System wave 4c: layout containers read the design system package

#29907

Entwicklerkommandos und Skript-Rekorder außerhalb des Produktivmodus für alle Benutzer

minor

#28605

Possibility to download a recorded script

#28995

Column filter should consider comparator of the column when sorting the options

#29801

TL Views: the split of <adaptive-detail> is configurable (size, unit, min-size on <selector> and <detail>; drawer width as drawer-size)

#29805

TL Views: a <value-input> is declared like a model attribute (mandatory, annotations) - a mandatory enumeration input offers no "no value" option

defect

critical

#29784

OpenAPI server: basic authentication of a technical user accepts an empty password when the configured password is empty (e.g. unset environment variable)

#29823

HistoryCompaction: Löschen von REVISION/REVISION_XREF und Umschreiben der Revisionsbereiche in je einer Transaktion lässt die Datenbank explodieren

major

#29580

RowSourceObserver: a disposed observer is still notified and throws NPE (_scope null) from DerivedViewChannel and GlobalModelEventForwarder

#29783

TLScriptFunctions: a script function is bound to an arbitrary overload of the same name, including a private one

#29788

Configuration: the error for an undecodable encrypted property echoes the value (e.g. a plain-text password) into the log

#29789

tl:generate-java fails on the first build after a TopLogic version change: it neither resolves the engine web fragments nor reads the project's own model sources

#29791

TL Views table: the row activation button runs the activation command without selecting its row, so commands reading the selection channel see another row (wrong breadcrumb label)

#29792

TL Views: a closed dialog (and a left tile-stack frame) stays visible for 1 s unless the application ships its own exit animation - move the demo's animations into the engine

#29800

Model patch of an existing database fails when a class gains a generalization and overrides its attributes in the same change

#29806

WrapperGenerator: every top-level class of a module with a singleton extends StructuredElement (regression of #26716)

#29807

WrapperGenerator: classifier constants of two enumerations collide, the generated factory does not compile

#29808

TL Views: the <on-submit> command of a text or number <value-input> runs on Enter only, not when the field is left with a changed value

#29810

TL Views: the selection channel of a <tree> keeps an object deleted in another view, and scripts over it fail

#29813

TL Views: a <tree> does not react to a change of an object it does not display yet, so a node that becomes a child of a shown node does not appear

#29822

CompactHistoryTask: Wartungsfenster bleibt nach dem Lauf aktiv, Task-Ende geht im Neustart der Persistenzschicht verloren

#29824

TL Views table: "Standard wiederherstellen" in the column selection drops a declared group-by (and does not restore the declared sort)

#29837

TestCompileJSPs modifies the module's source webapp and breaks concurrently running scripted tests of the same module

#29838

ClusterManager: a database connection that failed in a cluster transaction is returned to the pool and keeps failing every refetch

#29846

Changing the type of a column with content fails on Oracle (ORA-01439) and of an indexed column on MS SQL Server

#29848

ReportQueueTest.testAddJob fails sporadically: the queue thread may process the job before the test checks that it is queued

#29871

TestZipper.testEmptyFolder fails depending on the order in which the file system lists a folder

#29878

React UI does not react behind a proxy that buffers or refuses the window event stream

minor

#29766

TL-Script add() wirft UnsupportedOperationException bei Multi-Referenz auf transientem Objekt

#29804

XML import: line and column of a message location are formatted with a thousands separator ("line 4,433")

#29809

TL Views: a <value-input type="tl.core:Binary"> shows the file name as text instead of the binary field (no upload, no download)

task

minor

#29790

Upgrade guide 7.11 to 8.0: add the Maven >= 3.8.9 requirement, state that 7.10.x applications can follow it, and point to it from the release notes

#29793

Developer docs: recipe for an application-defined primitive type whose display depends on the owning object (custom datatype, value class, type-level storage, label provider, input control)

defect

major

#29789

tl:generate-java fails on the first build after a TopLogic version change: it neither resolves the engine web fragments nor reads the project's own model sources

Build Migration

Affects tl-maven-plugin 8.0.0-alpha10, goal generate-java (com.top_logic.build.maven.generate.GenerateJavaBinding).

Scenario

An application binds generate-java to generate-sources, as is common (and as recommended in the wrapper-generation documentation):

<plugin>
  <groupId>com.top-logic</groupId>
  <artifactId>tl-maven-plugin</artifactId>
  <executions>
    <execution>
      <id>generate-binding</id>
      <phase>generate-sources</phase>
      <goals><goal>generate-java</goal></goals>
    </execution>
  </executions>
  <configuration>
    <modules>my.module</modules>
  </configuration>
</plugin>

After raising the parent from 7.10.2 to 8.0.0-alpha10 (application version inherited from the parent), the very first build fails, so nothing can ever be installed:

Failed to resolve dependency 'com.top-logic:<app>:jar:8.0.0-alpha10' ... Could not find artifact
After bootstrapping the application's own artifact into the local repository, the goal fails with {{{

Generation for modules '...' failed. InvocationTargetException: Unable to createXMLProperties: Could not resolve '/WEB-INF/conf/top-logic.cluster.xml' to an existing resource. }}}

Analysis

The -X log of the goal shows for every engine module:

WARNING: No web fragment found for module '~/.m2/repository/com/top-logic/tl-core/8.0.0-alpha10/tl-core-8.0.0-alpha10.jar', searched: [~/.m2/repository/com/top-logic/tl-core/8.0.0-alpha10/tl-core-8.0.0-alpha10-web-fragment.war]
...
INFO: Using resource paths: [file:~/.m2/repository/com/top-logic/<app>/8.0.0-alpha10/<app>-8.0.0-alpha10-web-fragment.war]

The goal sets up the application configuration from web fragments in the local repository only: the application's own *installed* -web-fragment.war and the fragments PathInfo expects next to each engine jar.
It never asks Maven to resolve the web-fragment classifier artifacts. With a new engine version none of them is in the local repository yet (they are only fetched later in a normal build), so the configuration is incomplete and loading metaConf.txt fails.
It does not read the model from the project's src/main/webapp either. Therefore it needs the project's own artifact in the target version, which does not exist before the first successful build, and after a model change the generator sees the stale model until the project has been installed again.

Pre-fetching the fragments (mvn dependency:copy-dependencies -Dclassifier=web-fragment -Dtype=war -DfailOnMissingClassifierArtifact=false) and installing the project once with the generation skipped makes it work, confirming the analysis.

Related: #29705 fixed finding a fragment located in another repository of a maven.repo.local.tail chain; here the fragments are never fetched.

Expected

generate-java resolves the web-fragment wars of the project dependencies through Maven artifact resolution (type=war, classifier=web-fragment, missing ones skipped), like any other dependency.
It uses the project's own src/main/webapp (the reactor sources) instead of the project's installed artifact.
Then the goal works in generate-sources with an empty local repository, after a version change, and directly after a model change.

Workaround

Do not bind generate-java to the lifecycle; after mvn install, run mvn tl:generate-java on demand when the model changes.

Lösung

AppModuleStack (tl-maven-plugin) determines the TopLogic modules of an application: each jar dependency that is a TopLogic web component, ordered along the module dependencies, with its -web-fragment.war resolved through Maven artifact resolution. It provides the resource stack of the application (highest priority first) and closes the opened archives afterwards. The goals app and generate-java both use it.
Goal app: unchanged behaviour (the app layer is the application's resolved web fragment, an unresolvable fragment is an error); the built war is identical.
Goal generate-java:
- The application layer is the project's own src/main/webapp, so the generator always sees the current model sources.
- The class path contains the project's target/classes (if present) instead of the project's installed artifact, so the goal never needs the project's own artifact.
- A web fragment that cannot be resolved is skipped with the warning Skipping web fragment of ....
- The resource stack is logged (Resource stack (highest priority first):).
WrapperGenerator.generate(List<Path>, String[]) (tl-element) generates from an explicitly given resource stack (first entry overrides later ones) instead of deriving it from the class path; generate-java calls it.
The engine parent POM tl-parent-all no longer declares the snapshot repository tl-snapshots (https://dev.top-logic.com/nexus/repository/toplogic-snapshots/) as repository and plugin repository: a build of the engine never takes TopLogic snapshots from a remote, only from its own reactor and local repository. The snapshotRepository of the distributionManagement (deployment) is unchanged.

Tests

TestWrapperGenerator (tl-element): generation through the explicit resource stack, and the error for a module missing in the stack.
TestAppModuleStack (tl-maven-plugin): build order, resource-stack order, modules without fragment, closing the archives.
TestGenerateJavaIntegration (test module test.com.top_logic.build.maven, a regular module test, so the CI runs it): builds the test application src/test/projects/generate-java-it (never installed, generate-java bound to generate-sources) up to test-compile in a separate Maven process. The build starts with an empty local repository and gets the plugin and the other TopLogic artifacts from the local repository of the running build, which the test adds as remote repository through global settings; the user settings of the running build (mirrors such as the Central proxy, proxies, credentials) apply unchanged. The test module depends on tl-maven-plugin and tl-element, so that the reactor has installed them before the test runs (tl-maven-plugin itself cannot depend on the engine, whose build uses the plugin). The test checks that the binding is generated and compiled and that all engine fragments were resolved into the empty repository. With the previous goal implementation it fails with the ticket's first symptom.
The invoker profile run-its of tl-maven-plugin (never run by the CI) and its trivial IT are removed.

Not covered

The generator still loads the complete application configuration, so configuration referencing the application's own classes needs these classes compiled (target/classes) when the goal runs. This is left to a separate ticket.

Migration

An application whose POM inherits from the TopLogic parent POMs and builds against a TopLogic SNAPSHOT version from the TopLogic Nexus must declare the snapshot repository itself, since tl-parent-all no longer does. Applications created from tl-archetype-app already declare it; others add to their pom.xml:

{{{#!xml <repositories>

<repository>
<id>tl-snapshots</id>
<url>https://dev.top-logic.com/nexus/repository/toplogic-snapshots/</url>
<releases><enabled>false</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>

</repositories> <pluginRepositories>

<pluginRepository>
<id>tl-snapshots</id>
<url>https://dev.top-logic.com/nexus/repository/toplogic-snapshots/</url>
<releases><enabled>false</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</pluginRepository>

</pluginRepositories> }}}

Applications on a released TopLogic version need no change.