Any idea when that was and what module failed?
I switched to it in 2018 for my main project and at that time it was a bit of a
hard start, but thats long ago now.
----- Ursprüngliche Mail -----
> Von: "Ernesto Reinaldo Barreiro"
> An: "dev" <dev@wicket.apache.org>
> Gesendet: Mittwoch, 19. Juni 2024 11:48:52
> Betreff: Re: wicket version definition in maven poms
> Hum... I have the vague idea that I asked the same questions long long time
> ago and someone pointed me to some maven plugin bug
>
> On Wed, Jun 19, 2024 at 2:33 AM Korbinian Bachl
> wrote:
>
>> Hi,
>>
>> is there any reason wicket has static
>> <version>9.19.0-SNAPSHOTversion>
>> everywhere, even in modules
>>
>> <parent>
>> org.apache.wicket
>> wicket-parent
>> <version>9.19.0-SNAPSHOTversion>
>> ../pom.xml
>> parent>
>>
>>
>>
>> instead of a single defined properties in Wicket Parent:
>>
>> <version>${revision}${changelist}version>
>> ...
>> <properties>
>> 9.19.0
>> -SNAPSHOT
>> ...
>> properties>
>>
>>
>> and in submodules:
>>
>> <parent>
>> org.apache.wicket
>> wicket-parent
>> <version>${revision}${changelist}version>
>> parent>
>>
>>
>> That feature was introduced in maven 3.5 in 2017.
>>
>> KB
>>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
