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
OpenPGP_0x8006FAABBF942F73.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
