Re: Question for java/eclipse build

Hi Michael,

thanks for your reply :-)  I hope I did not make to much trouble - but I 
think it is solved now with eclipse and maven.  And yes it was the 
change between maven *.12 and *.13, what you wrote is a resolver 
change.  It broke the build on eclipse...

To avoid downloading files in the (poudiere) eclipse build step - I made 
a repository for the dependent maven files which I extracted in a 
temporary port build run on my side.

Overall this is not a real big deal.  I will continue the way I did  
till now - but now I know the reason of failure.  Maybe I can or need to 
integrate different maven versions into "my" eclipse-maven repository in 
special tag names??!  But that would make a lot of data...

I am free for good solutions or corrections :-)  Or to get insight for 
details which are needed to understand the software build / run behaviour.

All the best and many thanks to all, Norbert :-)

On 3/20/26 21:47, Michael Osipov wrote:
> Hi folks,
>
> thanks for the heads-up. I like to understand better what the issue is.
> I assume that a Maven Resolver change from .12 to .13 caused the issue.
> My understand is that you guys rely on 'mvn dependency:go-offline' and 
> we don't have something similar to Makefile.crates to have offline 
> builds, plus slight changes in the resolution code cause build issues.
>
> Norbert, feel free to reach out to me directly to further discuss this 
> and making the process better.
>
> Michael
>
> On 2026-03-20 16:45, Vladimir Druzenko wrote:
>> Hello!
>>
>> It’s probably better to simply update your Maven repository with each 
>> incompatible devel/maven39 update and make a new tag with the new 
>> version. Update the tag name in the port. And ask the devel/maven39 
>> maintainer ([email protected]) to notify you before updating so 
>> that the updates are committed synchronously. For example, he can 
>> create a PR with the topic "java/eclipse: Update devel/maven39" 
>> that devel/maven39 will be updated on such and such a day, and will 
>> attach a patch so that you can apply it and prepare a new repository. 
>> And then commit the updates at the same time.
>>
>> AFAIR [email protected] == [email protected] and have commit bit 
>> to ports.
>>
>> 15.03.2026 09:44, Norbert Grundmann пишет:
>>> ...coming back and asking for advice how to handle that the build of 
>>> java/eclipse depends on the version of maven39.  The new eclipse 
>>> 4.39 port build on quaterly installed depended packages is fine with 
>>> maven39 version 3.9.12 but breaks with version 3.9.13 - that is the 
>>> same for older eclipse version 4.38...  The architecture like 
>>> aarch64 or amd64 does not matter.
>>>
>>> To build I made a repository https://github.com/NorbertXYZ/eclipse- 
>>> maven on github getting the maven dependencies...  So the build 
>>> process does not download files.
>>>
>>> Thanks for remarks - I am not clear how to handle this a good way, 
>>> my approach of taking a prepared FreeBSD *.tar.gz file is not to a 
>>> good idea.
>>>
>>> Regards, Norbert
>>>
>>>
>>> On 3/15/26 06:54, Norbert Grundmann wrote:
>>>> thanks.  So I will keep "the old" way and integrate that there is a 
>>>> maven upgrade which affects newer builds...
>>>>
>>>> Regards, Norbert
>>
>>
>> -- 
>> Best regards,
>> Vladimir Druzenko
>>
>

-- 
I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)