Project

General

Profile

Bug #2207

Whitespace in java component type declaration may lead to repeated and concurrent recompiles

Added by Henning Blohm 6 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
z2-core
Target version:
Start date:
18.08.2026
Due date:
% Done:

0%

Estimated time:
origin:

Description

Currently in ComponentsBuilder._requiresMake(Collection<String>, Properties) we check if a component version noted in the dependency map of the component in consideration matches with the version noted for the component in the system.

For (non-prebuilt) Java components we use the compilation timestamp as system version, otherwise we use the repository revision.

However the type check does not trim the type setting in the component descriptor in that piece of code, so that a "com.zfabrik.java " type name is not detected as a Java component and hence the repository revision is taken.

The "incorrectly" declared component however is elsewhere detected as Java component, compiled, and a compilation timestamp is stored.

After compilation of a dependency component we find that timestamp and not it down in the dependency map (which is correct).

On the next cycle however we compare against the repository revision again so that a rebuild is performed.

Acceptance Criteria

  • The component type is trimmed in the component descriptor already to avoid any mis-interpretation

No data to display

Also available in: Atom PDF