Hi Piotr,
Thinking at it carefully, AFAIK it is a design decision done in early Maven 2
design time:
- POM properties don't influence dependencies
- profile activation influence dependencies
(I don't know for CLI properties)
The rationale is that:
1. POM properties are expected to be fixed once
Hello,
While looking at differences in generated CycloneDX SBOMs[1] I
stumbled upon an incoherence in the way Maven builds models of a
project's dependencies.
On one hand the properties defined in a project have no effect on the
effective models of dependencies. For example in:
3.0.0-beta1
