• Question for java/eclipse build

    From Norbert Grundmann@ngrundmann@gmx.de to muc.lists.freebsd.ports on Fri Mar 13 07:45:21 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hello,
    actually the builds for java/eclipse release 4.38_1 makes problems in
    poudiere - it ends with:
    [WARNING] The POM for org.apache.maven.plugins:maven-jar-plugin:jar:3.5.0 is missing, no dependency information available
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available
    [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.15.0 or one of its dependencies could not be resolved:
    [ERROR] Cannot access tycho-snapshots (https://repo.eclipse.org/content/repositories/tycho-snapshots/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access eclipse-snapshots (https://repo.eclipse.org/content/repositories/eclipse-snapshots/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access eclipse-cbi (https://repo.eclipse.org/content/repositories/cbi/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    If I build in /usr/ports on FreeBSD 14.3-p9 (quaterly) on aarch64 and
    amd64 I do not have any problems...
    Maybe someone could give me a tip why it happens...
    Thanks, Norbert
    --
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Fri Mar 13 08:29:30 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_7411_40053463.1773386970804
    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

    Just a quick guess.The errors started March 10 on the build cluster: https://portsfallout.com/fallout?port=java%2Feclipse%24.
    On March 8 devel/maven39 got an update.
    Could that be involved?

    Regards,
    Ronald

    Van: Norbert Grundmann <ngrundmann@gmx.de>
    Datum: 13 maart 2026 07:45
    Aan: ports@FreeBSD.org
    Onderwerp: Question for java/eclipse build



    Hello,

    actually the builds for java/eclipse release 4.38_1 makes problems in poudiere - it ends with:

    [WARNING] The POM for org.apache.maven.plugins:maven-jar-plugin:jar:3.5.0 is missing, no dependency information available
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available
    [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.15.0 or one of its dependencies could not be resolved:
    [ERROR] Cannot access tycho-snapshots (https://repo.eclipse.org/content/repositories/tycho-snapshots/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access eclipse-snapshots (https://repo.eclipse.org/content/repositories/eclipse-snapshots/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access eclipse-cbi (https://repo.eclipse.org/content/repositories/cbi/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.

    If I build in /usr/ports on FreeBSD 14.3-p9 (quaterly) on aarch64 and amd64 I do not have any problems...

    Maybe someone could give me a tip why it happens...

    Thanks, Norbert

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






    ------=_Part_7411_40053463.1773386970804
    Content-Type: text/html; charset=us-ascii
    Content-Transfer-Encoding: 7bit

    <html><head></head><body>Just a quick guess.<br class="rw_extra">The errors started March 10 on the build cluster:&nbsp;<a href="https://portsfallout.com/fallout?port=java%2Feclipse%24">https://portsfallout.com/fallout?port=java%2Feclipse%24</a>.<div>On March 8 devel/maven39 got an update.<div><div>Could that be involved?</div><div><br></div><div>Regards,</div><div>Ronald</div><div><br></div><div><p><small><strong>Van:</strong> Norbert Grundmann &lt;ngrundmann@gmx.de&gt;<br><strong>Datum:</strong> 13 maart 2026 07:45<br><strong>Aan:</strong> ports@FreeBSD.org<br><strong>Onderwerp:</strong> Question for java/eclipse build<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer" id="P"><!-- P -->
    <!-- processMimeMessage --><div class="TextPlainViewer" id="P.P"><!-- P.P -->Hello,<br>

    actually the builds for java/eclipse release 4.38_1 makes problems in poudiere - it ends with:<br>

    [WARNING] The POM for org.apache.maven.plugins:maven-jar-plugin:jar:3.5.0 is missing, no dependency information available<br>
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available<br>
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available<br>
    [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.15.0 or one of its dependencies could not be resolved:<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access tycho-snapshots (<a href="https://repo.eclipse.org/content/repositories/tycho-snapshots/">https://repo.eclipse.org/content/repositories/tycho-snapshots/</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access eclipse-snapshots (<a href="https://repo.eclipse.org/content/repositories/eclipse-snapshots/">https://repo.eclipse.org/content/repositories/eclipse-snapshots/</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access eclipse-cbi (<a href="https://repo.eclipse.org/content/repositories/cbi/">https://repo.eclipse.org/content/repositories/cbi/</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access central (<a href="https://repo.maven.apache.org/maven2">https://repo.maven.apache.org/maven2</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>

    If I build in /usr/ports on FreeBSD 14.3-p9 (quaterly) on aarch64 and amd64 I do not have any problems...<br>

    Maybe someone could give me a tip why it happens...<br>

    Thanks, Norbert<br>

    --&nbsp;<br>
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)<br>


    </div><!-- TextPlainViewer -->

    </div><!-- MessageRFC822Viewer --> </blockquote><br><br><br></div></div></div></body></html> ------=_Part_7411_40053463.1773386970804--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Fri Mar 13 08:34:08 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_8667_986511321.1773387248786
    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

    The maven update has a change that mentions the jar version that the error talks about.

    https://github.com/apache/maven/pull/11721/changes

    Regards,
    Ronald

    Van: Ronald Klop <ronald-lists@klop.ws>
    Datum: 13 maart 2026 08:30
    Aan: Norbert Grundmann <ngrundmann@gmx.de>
    CC: ports@FreeBSD.org
    Onderwerp: Re: Question for java/eclipse build




    Just a quick guess.The errors started March 10 on the build cluster: https://portsfallout.com/fallout?port=java%2Feclipse%24.
    On March 8 devel/maven39 got an update.
    Could that be involved?

    Regards,
    Ronald

    Van: Norbert Grundmann
    Datum: 13 maart 2026 07:45
    Aan: ports@FreeBSD.org
    Onderwerp: Question for java/eclipse build


    Hello,

    actually the builds for java/eclipse release 4.38_1 makes problems in poudiere - it ends with:

    [WARNING] The POM for org.apache.maven.plugins:maven-jar-plugin:jar:3.5.0 is missing, no dependency information available
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available
    [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.15.0 or one of its dependencies could not be resolved:
    [ERROR] Cannot access tycho-snapshots (https://repo.eclipse.org/content/repositories/tycho-snapshots/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access eclipse-snapshots (https://repo.eclipse.org/content/repositories/eclipse-snapshots/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access eclipse-cbi (https://repo.eclipse.org/content/repositories/cbi/) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.
    [ERROR] Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.

    If I build in /usr/ports on FreeBSD 14.3-p9 (quaterly) on aarch64 and amd64 I do not have any problems...

    Maybe someone could give me a tip why it happens...

    Thanks, Norbert

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












    ------=_Part_8667_986511321.1773387248786
    Content-Type: text/html; charset=us-ascii
    Content-Transfer-Encoding: 7bit

    <html><head></head><body>The maven update has a change that mentions the jar version that the error talks about.<div><br></div><div><a href="https://github.com/apache/maven/pull/11721/changes">https://github.com/apache/maven/pull/11721/changes</a></div><div><br></div><div>Regards,</div><div>Ronald</div><div><br><p><small><strong>Van:</strong> Ronald Klop &lt;ronald-lists@klop.ws&gt;<br><strong>Datum:</strong> 13 maart 2026 08:30<br><strong>Aan:</strong> Norbert Grundmann &lt;ngrundmann@gmx.de&gt;<br><strong>CC:</strong> ports@FreeBSD.org<br><strong>Onderwerp:</strong> Re: Question for java/eclipse build<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P -->
    <!-- processMimeMessage --><div class="MultipartAlternativeViewer do_not_remove"><!-- P.P -->
    <div class="TextHTMLViewer do_not_remove" id="P.P.P"><!-- P.P.P -->
    Just a quick guess.<br class="rw_extra">The errors started March 10 on the build cluster:&nbsp;<a href="https://portsfallout.com/fallout?port=java%2Feclipse%24">https://portsfallout.com/fallout?port=java%2Feclipse%24</a>.<div class="do_not_remove">On March 8 devel/maven39 got an update.<div class="do_not_remove"><div class="do_not_remove">Could that be involved?</div><div class="do_not_remove"><br></div><div class="do_not_remove">Regards,</div><div class="do_not_remove">Ronald</div><div class="do_not_remove"><br></div><div class="do_not_remove"><p><small><strong>Van:</strong> Norbert Grundmann <ngrundmann@gmx.de><br><strong>Datum:</strong> 13 maart 2026 07:45<br><strong>Aan:</strong> ports@FreeBSD.org<br><strong>Onderwerp:</strong> Question for java/eclipse build<br></ngrundmann@gmx.de></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P">
    <div class="TextPlainViewer do_not_remove" id="P.P">Hello,<br>

    actually the builds for java/eclipse release 4.38_1 makes problems in poudiere - it ends with:<br>

    [WARNING] The POM for org.apache.maven.plugins:maven-jar-plugin:jar:3.5.0 is missing, no dependency information available<br>
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available<br>
    [WARNING] The POM for org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 is missing, no dependency information available<br>
    [ERROR] Plugin org.apache.maven.plugins:maven-compiler-plugin:3.15.0 or one of its dependencies could not be resolved:<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access tycho-snapshots (<a href="https://repo.eclipse.org/content/repositories/tycho-snapshots/">https://repo.eclipse.org/content/repositories/tycho-snapshots/</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access eclipse-snapshots (<a href="https://repo.eclipse.org/content/repositories/eclipse-snapshots/">https://repo.eclipse.org/content/repositories/eclipse-snapshots/</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access eclipse-cbi (<a href="https://repo.eclipse.org/content/repositories/cbi/">https://repo.eclipse.org/content/repositories/cbi/</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>
    [ERROR] &nbsp;&nbsp;&nbsp;&nbsp;Cannot access central (<a href="https://repo.maven.apache.org/maven2">https://repo.maven.apache.org/maven2</a>) in offline mode and the artifact org.apache.maven.plugins:maven-compiler-plugin:jar:3.15.0 has not been downloaded from it before.<br>

    If I build in /usr/ports on FreeBSD 14.3-p9 (quaterly) on aarch64 and amd64 I do not have any problems...<br>

    Maybe someone could give me a tip why it happens...<br>

    Thanks, Norbert<br>

    --&nbsp;<br>
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)<br>


    </div>

    </div>
    </blockquote><br><br><br></div></div></div></div><!-- TextHTMLViewer --> </div><!-- MultipartAlternativeViewer -->
    </div><!-- MessageRFC822Viewer --> </blockquote><br><br><br></div></body></html> ------=_Part_8667_986511321.1773387248786--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Fri Mar 13 13:35:33 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_910_649129486.1773405333487
    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

    Hi,

    cc-ing ports@ back into the conversation

    Van: Norbert Grundmann <ngrundmann@gmx.de>
    Datum: vrijdag, 13 maart 2026 12:46
    Aan: Ronald Klop <ronald-lists@klop.ws>
    Onderwerp: Re: Question for java/eclipse build

    On 3/13/26 08:51, Ronald Klop wrote:
    The java/eclipse/Makefile has this comment:

    # The github repositories. The repository under NorbertXYZ is for a > predefined maven
    # download, so the build does not need to download while do-build is > running

    I think the port needs an updated NorbertXYZ.

    Regards,
    Ronald

    Thank you - that is the reason... I can see this in freshports on the internet...

    But how to handle this? So I have jails to test my eclipse on aarch64 and amd64. It runs 14-RELEASE-p9 and uses preinstalled quaterly packages - that means also the "older" maven39 port. My question is: if I would install the newest packages from latest - would it fix the problem? But what happens with poudiere runs for the quaterly packages. They would need "older" maven39, or? and if I use software, I install packages from quaterly. I am a bit confused about how to proceed...

    All the best, Norbert :-)

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






    Your GH_TUPLE line defines a specific tag to use, which is now the same as DISTVERSION (4.38).
    NorbertXYZ:eclipse-maven:${DISTVERSION}:n

    A possible solution is to create a new tag in github (4.38_2) and use that in the main port and leave the quarterly port unchanged.
    NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n
    See: https://github.com/NorbertXYZ/eclipse-maven/tags

    I hope this helps.

    Regards,
    Ronald.

    ------=_Part_910_649129486.1773405333487
    Content-Type: text/html; charset=us-ascii
    Content-Transfer-Encoding: 7bit

    <html><head></head><body>Hi,<br>

    cc-ing ports@ back into the conversation<br>
    &nbsp;
    <p><strong>Van:</strong> Norbert Grundmann &lt;ngrundmann@gmx.de&gt;<br> <strong>Datum:</strong> vrijdag, 13 maart 2026 12:46<br>
    <strong>Aan:</strong> Ronald Klop &lt;ronald-lists@klop.ws&gt;<br> <strong>Onderwerp:</strong> Re: Question for java/eclipse build</p>

    <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">
    <div class="MessageRFC822Viewer" id="P">
    <div class="TextPlainViewer" id="P.P">On 3/13/26 08:51, Ronald Klop wrote:<br> &gt; The java/eclipse/Makefile has this comment:<br>
    &gt;<br>
    &gt; # The github repositories. &nbsp;The repository under NorbertXYZ is for a &gt; predefined maven<br>
    &gt; # download, so the build does not need to download while do-build is &gt; running<br>
    &gt;<br>
    &gt; I think the port needs an updated NorbertXYZ.<br>
    &gt;<br>
    &gt; Regards,<br>
    &gt; Ronald<br>

    Thank you - that is the reason...&nbsp; I can see this in freshports on the internet...<br>

    But how to handle this?&nbsp; So I have jails to test my eclipse on aarch64 and amd64.&nbsp; It runs 14-RELEASE-p9 and uses preinstalled quaterly packages - that means also the "older" maven39 port.&nbsp; My question is: if I would install the newest packages from latest - would it fix the problem?&nbsp; But what happens with poudiere runs for the quaterly packages.&nbsp; They would need "older" maven39, or?&nbsp; and if I use software, I install packages from quaterly.&nbsp; I am a bit confused about how to proceed...<br>

    All the best, Norbert :-)<br>

    --&nbsp;<br>
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)<br>
    &nbsp;</div>

    <hr></div>
    </blockquote>


    Your GH_TUPLE line defines a specific tag to use, which is now the same as DISTVERSION (4.38).<br>
    NorbertXYZ:eclipse-maven:${DISTVERSION}:n<br>

    A possible solution is to create a new tag in github (4.38_2) and use that in the main port and leave the quarterly port unchanged.<br>
    NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n<br>
    See:&nbsp;<a href="https://github.com/NorbertXYZ/eclipse-maven/tags">https://github.com/NorbertXYZ/eclipse-maven/tags</a><br>

    I hope this helps.<br>

    Regards,<br>
    Ronald.<br>
    &nbsp;</body></html>
    ------=_Part_910_649129486.1773405333487--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Fri Mar 13 13:52:16 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_1269_1914973187.1773406336165
    Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable

    Rereading your mail I saw some more concerns you mention.

    1. When developing your port for main it can be easier to install dependenc= ies for main also. That gives consistency to what is upstream.
    2. As long as the maintainer of maven39 does not merge the changes to the q= uarterly branch, you don't need to do anything for quarterly. But keep the = 4.38 tag unchanged in github.
    3. Your https://github.com/NorbertXYZ/eclipse repo has a nice README.md, ma= ybe add something similar to the eclipse-maven repo with instructions to yo=
    ur future self on how you did things. =F0=9F=98=80 I totally recognize goin=
    g back to some project years later and wondering how things worked.

    If you get stuck, there are probably some people here or on java@ that want=
    to help further.

    NB: it can really help to keep ports@ in the cc:, if you want feedback from=
    others too.

    Regards,
    Ronald.

    =20
    Van: Norbert Grundmann <ngrundmann@gmx.de>
    Datum: vrijdag, 13 maart 2026 13:37
    Aan: Ronald Klop <ronald-lists@klop.ws>
    Onderwerp: Re: Question for java/eclipse build
    =20
    Thanks a lot :-) :-) I will see...
    =20
    On 3/13/26 13:35, Ronald Klop wrote:
    Hi,
    =20
    cc-ing ports@ back into the conversation
    =20
    Van: Norbert Grundmann <ngrundmann@gmx.de>
    Datum: vrijdag, 13 maart 2026 12:46
    Aan: Ronald Klop <ronald-lists@klop.ws>
    Onderwerp: Re: Question for java/eclipse build
    =20
    On 3/13/26 08:51, Ronald Klop wrote:
    The java/eclipse/Makefile has this comment:

    # The github repositories. The repository under NorbertXYZ is for a =
    predefined maven
    # download, so the build does not need to download while do-build is =
    running

    I think the port needs an updated NorbertXYZ.

    Regards,
    Ronald
    =20
    Thank you - that is the reason... I can see this in freshports on the = internet...
    =20
    But how to handle this? So I have jails to test my eclipse on aarch64 = and amd64. It runs 14-RELEASE-p9 and uses preinstalled quaterly packages -=
    that means also the "older" maven39 port. My question is: if I would inst= all the newest packages from latest - would it fix the problem? But what h= appens with poudiere runs for the quaterly packages. They would need "olde=
    r" maven39, or? and if I use software, I install packages from quaterly. =
    I am a bit confused about how to proceed...
    =20
    All the best, Norbert :-)
    =20
    --=20
    I love penguins at the south pole, windows in my house and apples on my=
    tree, but not in my computer :)
    =20
    =20
    =20
    =20
    =20
    =20
    Your GH_TUPLE line defines a specific tag to use, which is now the same =
    as DISTVERSION (4.38).
    NorbertXYZ:eclipse-maven:${DISTVERSION}:n
    =20
    A possible solution is to create a new tag in github (4.38_2) and use th=
    at in the main port and leave the quarterly port unchanged.
    NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n
    See: https://github.com/NorbertXYZ/eclipse-maven/tags
    =20
    I hope this helps.
    =20
    Regards,
    Ronald.
    =20
    =20
    =20
    --=20
    I love penguins at the south pole, windows in my house and apples on my t=
    ree, but not in my computer :)

    =20
    ------=_Part_1269_1914973187.1773406336165
    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body>Rereading your mail I saw some more concerns you m= ention.<br>

    1. When developing your port for main it can be easier to install dependenc= ies for main also. That gives consistency to what is upstream.<br>
    2. As long as the maintainer of maven39 does not merge the changes to the q= uarterly branch, you don't need to do anything for quarterly. But keep the = 4.38 tag unchanged in github.<br>
    3. Your https://github.com/NorbertXYZ/eclipse repo has a nice README.md, ma= ybe add something similar to the eclipse-maven repo with instructions to yo=
    ur future self on how you did things. =F0=9F=98=80 I totally recognize goin=
    g back to some project years later and wondering how things worked.<br>

    If you get stuck, there are probably some people here or on java@ that want=
    to help further.<br>

    NB: it can really help to keep ports@ in the cc:, if you want feedback from=
    others too.<br>

    Regards,<br>
    Ronald.<br>

    &nbsp;
    <p><strong>Van:</strong> Norbert Grundmann &lt;ngrundmann@gmx.de&gt;<br> <strong>Datum:</strong> vrijdag, 13 maart 2026 13:37<br>
    <strong>Aan:</strong> Ronald Klop &lt;ronald-lists@klop.ws&gt;<br> <strong>Onderwerp:</strong> Re: Question for java/eclipse build</p>

    <blockquote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5p=
    x; border-left: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"MultipartAlternativeViewer">
    <div class=3D"TextHTMLViewer" id=3D"P.P.P">
    <div class=3D"moz-cite-prefix">Thanks a lot :-) :-) I will see...</div>

    <div class=3D"moz-cite-prefix">&nbsp;</div>

    <div class=3D"moz-cite-prefix">On 3/13/26 13:35, Ronald Klop wrote:</div>

    <blockquote>Hi,<br>

    cc-ing ports@ back into the conversation<br>
    &nbsp;
    <p><strong>Van:</strong> Norbert Grundmann <a class=3D"moz-txt-link-rfc2396=
    E" href=3D"mailto:ngrundmann@gmx.de">&lt;ngrundmann@gmx.de&gt;</a><br> <strong>Datum:</strong> vrijdag, 13 maart 2026 12:46<br>
    <strong>Aan:</strong> Ronald Klop <a class=3D"moz-txt-link-rfc2396E" href= =3D"mailto:ronald-lists@klop.ws">&lt;ronald-lists@klop.ws&gt;</a><br> <strong>Onderwerp:</strong> Re: Question for java/eclipse build</p>

    <blockquote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5p=
    x; border-left: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"TextPlainViewer" id=3D"P.P">On 3/13/26 08:51, Ronald Klop wro= te:<br>
    &gt; The java/eclipse/Makefile has this comment:<br>
    &gt;<br>
    &gt; # The github repositories. &nbsp;The repository under NorbertXYZ is fo=
    r a &gt; predefined maven<br>
    &gt; # download, so the build does not need to download while do-build is &= gt; running<br>
    &gt;<br>
    &gt; I think the port needs an updated NorbertXYZ.<br>
    &gt;<br>
    &gt; Regards,<br>
    &gt; Ronald<br>

    Thank you - that is the reason...&nbsp; I can see this in freshports on the=
    internet...<br>

    But how to handle this?&nbsp; So I have jails to test my eclipse on aarch64=
    and amd64.&nbsp; It runs 14-RELEASE-p9 and uses preinstalled quaterly pack= ages - that means also the "older" maven39 port.&nbsp; My question is: if I=
    would install the newest packages from latest - would it fix the problem?&= nbsp; But what happens with poudiere runs for the quaterly packages.&nbsp; = They would need "older" maven39, or?&nbsp; and if I use software, I install=
    packages from quaterly.&nbsp; I am a bit confused about how to proceed...<=


    All the best, Norbert :-)<br>

    --&nbsp;<br>
    I love penguins at the south pole, windows in my house and apples on my tre=
    e, but not in my computer :)<br>
    &nbsp;</div>

    <hr></div>
    </blockquote>


    Your GH_TUPLE line defines a specific tag to use, which is now the same as = DISTVERSION (4.38).<br>
    NorbertXYZ:eclipse-maven:${DISTVERSION}:n<br>

    A possible solution is to create a new tag in github (4.38_2) and use that =
    in the main port and leave the quarterly port unchanged.<br> NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n<br>
    See:&nbsp;<a class=3D"moz-txt-link-freetext" href=3D"https://github.com/Nor= bertXYZ/eclipse-maven/tags">https://github.com/NorbertXYZ/eclipse-maven/tag= s</a><br>

    I hope this helps.<br>

    Regards,<br>
    Ronald.<br>
    &nbsp;</blockquote>

    <p>&nbsp;</p>

    <pre class=3D"moz-signature" style=3D";white-space: pre-wrap;white-space: p= re-wrap;">--=20
    I love penguins at the south pole, windows in my house and apples on my tre=
    e, but not in my computer :)</pre>
    </div>
    </div>
    </div>
    </blockquote>

    &nbsp;</body></html>
    ------=_Part_1269_1914973187.1773406336165--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Norbert Grundmann@ngrundmann@gmx.de to muc.lists.freebsd.ports on Sat Mar 14 16:32:41 2026
    From Newsgroup: muc.lists.freebsd.ports

    This is a multi-part message in MIME format. --------------snbZYX4jIu2lcy9Pju6MWUtu
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable

    Hello Ronald,

    thanks for the comments...=C2=A0 :-)

    I think I will take another approach to build eclipse in future on=20 FreeBSD.=C2=A0 About 2-3 year ago I made a lot patches to make version 4.3= 2=20
    work - the previous one was 4.24.=C2=A0 It took a lot of hours.=C2=A0 Afte=
    r months=20
    someone took over and created a github repository with FreeBSD stuff,=20
    which I took as the basis.=C2=A0 The maintainer of that repo also creates=
    =20
    *.tar.gz files which contain a full FreeBSD compilation / package, but=20
    not usable the pkg way.=C2=A0 So why recompile?=C2=A0 I want to take his *= .tar.gz=20
    file, extract and do the needed post-install steps.=C2=A0 The end should a=
    =20
    "normal" package usable for FreeBSD :-)

    The first steps of this approach seems to work...=C2=A0 I would like to ch= eck=20
    before I submit and before other people would confirm, that it works.

    What do you think?=C2=A0 This way is more easy and does not use a long=20 compilation time - just seconds for download and prepare.=C2=A0 And it is=
    =20
    less error lasting ;-)

    Of course I will depend on this github repository and data.=C2=A0 But that=
    I=20
    did the last versions, too...

    Regards, Norbert

    On 3/13/26 13:52, Ronald Klop wrote:
    Rereading your mail I saw some more concerns you mention.

    1. When developing your port for main it can be easier to install=20 dependencies for main also. That gives consistency to what is upstream.
    2. As long as the maintainer of maven39 does not merge the changes to=20
    the quarterly branch, you don't need to do anything for quarterly. But=
    =20
    keep the 4.38 tag unchanged in github.
    3. Your https://github.com/NorbertXYZ/eclipse repo has a nice=20
    README.md, maybe add something similar to the eclipse-maven repo with=20 instructions to your future self on how you did things. =F0=9F=98=80 I t=
    otally=20
    recognize going back to some project years later and wondering how=20
    things worked.

    If you get stuck, there are probably some people here or on java@ that=
    =20
    want to help further.

    NB: it can really help to keep ports@ in the cc:, if you want feedback=
    =20
    from others too.

    Regards,
    Ronald.

    *Van:* Norbert Grundmann <ngrundmann@gmx.de>
    *Datum:* vrijdag, 13 maart 2026 13:37
    *Aan:* Ronald Klop <ronald-lists@klop.ws>
    *Onderwerp:* Re: Question for java/eclipse build

    Thanks a lot :-) :-) I will see...
    On 3/13/26 13:35, Ronald Klop wrote:

    Hi,

    cc-ing ports@ back into the conversation

    *Van:* Norbert Grundmann <ngrundmann@gmx.de>
    *Datum:* vrijdag, 13 maart 2026 12:46
    *Aan:* Ronald Klop <ronald-lists@klop.ws>
    *Onderwerp:* Re: Question for java/eclipse build

    On 3/13/26 08:51, Ronald Klop wrote:
    > The java/eclipse/Makefile has this comment:
    >
    > # The github repositories. =C2=A0The repository under
    NorbertXYZ is for a > predefined maven
    > # download, so the build does not need to download while
    do-build is > running
    >
    > I think the port needs an updated NorbertXYZ.
    >
    > Regards,
    > Ronald

    Thank you - that is the reason...=C2=A0 I can see this in
    freshports on the internet...

    But how to handle this?=C2=A0 So I have jails to test my
    eclipse on aarch64 and amd64.=C2=A0 It runs 14-RELEASE-p9 an=
    d
    uses preinstalled quaterly packages - that means also the
    "older" maven39 port.=C2=A0 My question is: if I would insta=
    ll
    the newest packages from latest - would it fix the
    problem?=C2=A0 But what happens with poudiere runs for the
    quaterly packages.=C2=A0 They would need "older" maven39, or=
    ?=C2=A0
    and if I use software, I install packages from quaterly.=C2=
    =A0
    I am a bit confused about how to proceed...

    All the best, Norbert :-)

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



    Your GH_TUPLE line defines a specific tag to use, which is now
    the same as DISTVERSION (4.38).
    NorbertXYZ:eclipse-maven:${DISTVERSION}:n

    A possible solution is to create a new tag in github (4.38_2)
    and use that in the main port and leave the quarterly port
    unchanged.
    NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n
    See: https://github.com/NorbertXYZ/eclipse-maven/tags

    I hope this helps.

    Regards,
    Ronald.

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



    =2D-=20
    I love penguins at the south pole, windows in my house and apples on my tr=
    ee, but not in my computer :)

    --------------snbZYX4jIu2lcy9Pju6MWUtu
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-=

    </head>
    <body>
    <div class=3D"moz-cite-prefix">Hello Ronald,</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">thanks for the comments...=C2=A0 :-)</d=

    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">I think I will take another approach to
    build eclipse in future on FreeBSD.=C2=A0 About 2-3 year ago I made =
    a
    lot patches to make version 4.32 work - the previous one was
    4.24.=C2=A0 It took a lot of hours.=C2=A0 After months someone took = over and
    created a github repository with FreeBSD stuff, which I took as
    the basis.=C2=A0 The maintainer of that repo also creates *.tar.gz
    files which contain a full FreeBSD compilation / package, but not
    usable the pkg way.=C2=A0 So why recompile?=C2=A0 I want to take his
    *.tar.gz file, extract and do the needed post-install steps.=C2=A0 T=
    he
    end should a "normal" package usable for FreeBSD :-)</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">The first steps of this approach seems
    to work...=C2=A0 I would like to check before I submit and before ot=
    her
    people would confirm, that it works.</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">What do you think?=C2=A0 This way is mo=
    re
    easy and does not use a long compilation time - just seconds for
    download and prepare.=C2=A0 And it is less error lasting ;-)</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">Of course I will depend on this github
    repository and data.=C2=A0 But that I did the last versions, too...<= /div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">Regards, Norbert</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">On 3/13/26 13:52, Ronald Klop wrote:<br=

    </div>
    <blockquote type=3D"cite"
    cite=3D"mid:183908715.1270.1773406336228@localhost">
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUT= F-8">
    Rereading your mail I saw some more concerns you mention.<br>
    <br>
    1. When developing your port for main it can be easier to install
    dependencies for main also. That gives consistency to what is
    upstream.<br>
    2. As long as the maintainer of maven39 does not merge the changes
    to the quarterly branch, you don't need to do anything for
    quarterly. But keep the 4.38 tag unchanged in github.<br>
    3. Your <a class=3D"moz-txt-link-freetext" href=3D"https://github.co= m/NorbertXYZ/eclipse">https://github.com/NorbertXYZ/eclipse</a> repo has a=
    nice
    README.md, maybe add something similar to the eclipse-maven repo
    with instructions to your future self on how you did things. =F0=9F= =98=80 I
    totally recognize going back to some project years later and
    wondering how things worked.<br>
    <br>
    If you get stuck, there are probably some people here or on java@
    that want to help further.<br>
    <br>
    NB: it can really help to keep ports@ in the cc:, if you want
    feedback from others too.<br>
    <br>
    Regards,<br>
    Ronald.<br>
    <br>
    =C2=A0
    <p><strong>Van:</strong> Norbert Grundmann
    <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:ngrundmann@gmx.d= e">&lt;ngrundmann@gmx.de&gt;</a><br>
    <strong>Datum:</strong> vrijdag, 13 maart 2026 13:37<br>
    <strong>Aan:</strong> Ronald Klop <a class=3D"moz-txt-link-rfc2396=
    E" href=3D"mailto:ronald-lists@klop.ws">&lt;ronald-lists@klop.ws&gt;</a><b=

    <strong>Onderwerp:</strong> Re: Question for java/eclipse build</p=

    <blockquote
    style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5px; border-l= eft: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"MultipartAlternativeViewer">
    <div class=3D"TextHTMLViewer" id=3D"P.P.P">
    <div class=3D"moz-cite-prefix">Thanks a lot :-) :-) I will
    see...</div>
    <div class=3D"moz-cite-prefix">=C2=A0</div>
    <div class=3D"moz-cite-prefix">On 3/13/26 13:35, Ronald Klop
    wrote:</div>
    <blockquote>Hi,<br>
    <br>
    cc-ing ports@ back into the conversation<br>
    =C2=A0
    <p><strong>Van:</strong> Norbert Grundmann <a
    class=3D"moz-txt-link-rfc2396E"
    href=3D"mailto:ngrundmann@gmx.de"
    moz-do-not-send=3D"true">&lt;ngrundmann@gmx.de&gt;</a>=

    <strong>Datum:</strong> vrijdag, 13 maart 2026 12:46<br>
    <strong>Aan:</strong> Ronald Klop <a
    class=3D"moz-txt-link-rfc2396E"
    href=3D"mailto:ronald-lists@klop.ws"
    moz-do-not-send=3D"true">&lt;ronald-lists@klop.ws&gt;<= /a><br>
    <strong>Onderwerp:</strong> Re: Question for
    java/eclipse build</p>
    <blockquote
    style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5px; border-l= eft: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"TextPlainViewer" id=3D"P.P">On 3/13/26
    08:51, Ronald Klop wrote:<br>
    &gt; The java/eclipse/Makefile has this comment:<br>
    &gt;<br>
    &gt; # The github repositories. =C2=A0The repository
    under NorbertXYZ is for a &gt; predefined maven<br>
    &gt; # download, so the build does not need to
    download while do-build is &gt; running<br>
    &gt;<br>
    &gt; I think the port needs an updated NorbertXYZ.<b=

    &gt;<br>
    &gt; Regards,<br>
    &gt; Ronald<br>
    <br>
    Thank you - that is the reason...=C2=A0 I can see th=
    is
    in freshports on the internet...<br>
    <br>
    But how to handle this?=C2=A0 So I have jails to tes=
    t
    my eclipse on aarch64 and amd64.=C2=A0 It runs
    14-RELEASE-p9 and uses preinstalled quaterly
    packages - that means also the "older" maven39
    port.=C2=A0 My question is: if I would install the
    newest packages from latest - would it fix the
    problem?=C2=A0 But what happens with poudiere runs f=
    or
    the quaterly packages.=C2=A0 They would need "older"
    maven39, or?=C2=A0 and if I use software, I install
    packages from quaterly.=C2=A0 I am a bit confused ab=
    out
    how to proceed...<br>
    <br>
    All the best, Norbert :-)<br>
    <br>
    --=C2=A0<br>
    I love penguins at the south pole, windows in my
    house and apples on my tree, but not in my
    computer :)<br>
    =C2=A0</div>
    <hr></div>
    </blockquote>
    <br>
    <br>
    Your GH_TUPLE line defines a specific tag to use, which
    is now the same as DISTVERSION (4.38).<br>
    NorbertXYZ:eclipse-maven:${DISTVERSION}:n<br>
    <br>
    A possible solution is to create a new tag in github
    (4.38_2) and use that in the main port and leave the
    quarterly port unchanged.<br>
    NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n<br>
    See:=C2=A0<a class=3D"moz-txt-link-freetext" href=3D"https://github.com/NorbertXYZ/eclipse-maven/tags"
    moz-do-not-send=3D"true">https://github.com/NorbertXYZ/e= clipse-maven/tags</a><br>
    <br>
    I hope this helps.<br>
    <br>
    Regards,<br>
    Ronald.<br>
    =C2=A0</blockquote>
    <p>=C2=A0</p>
    <pre class=3D"moz-signature"
    style=3D";white-space: pre-wrap;white-space: pre-wrap;">--=
    =20
    I love penguins at the south pole, windows in my house and apples on my tr=
    ee, but not in my computer :)</pre>
    </div>
    </div>
    </div>
    </blockquote>
    <br>
    =C2=A0
    </blockquote>
    <p><br>
    </p>
    <pre class=3D"moz-signature" cols=3D"72">--=20
    I love penguins at the south pole, windows in my house and apples on my tr=
    ee, but not in my computer :)</pre>
    </body>
    </html>

    --------------snbZYX4jIu2lcy9Pju6MWUtu--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Norbert Grundmann@ngrundmann@gmx.de to muc.lists.freebsd.ports on Sun Mar 15 06:54:09 2026
    From Newsgroup: muc.lists.freebsd.ports

    thanks.-a So I will keep "the old" way and integrate that there is a
    maven upgrade which affects newer builds...
    Regards, Norbert
    On 3/14/26 22:09, Mark Millard wrote:
    On 3/14/26 08:32, Norbert Grundmann wrote:
    Hello Ronald,

    thanks for the comments...-a :-)

    I think I will take another approach to build eclipse in future on
    FreeBSD.-a About 2-3 year ago I made a lot patches to make version 4.32
    work - the previous one was 4.24.-a It took a lot of hours.-a After months >> someone took over and created a github repository with FreeBSD stuff,
    which I took as the basis.-a The maintainer of that repo also creates
    *.tar.gz files which contain a full FreeBSD compilation / package, but
    not usable the pkg way.
    [My notes/questions below are general/generic, not based in a detailed analysis of java/eclipse details.]

    Such a file exists that includes the compilation/package for each and
    every combination of the following? [as things stand now]:

    ) supported arch for the port-package
    (amd64 vs. aarch64 vs. i386 . . .)

    ) quarterly [2026Q1] (all but main below)
    vs. latest (all 4 of the below, including main)

    ) 13.5, 14.3 (14.4 next), 15.0 (15.1 next), and main [so: 16.0 for now]

    Even limited to tier 1 platforms (amd64 and aarch64) that is 2*(3+4)==14 combinations that each have a separate port-package built and
    distributed by-athe official FreeBSD build servers. Are all of those covered?

    (i386 is still having port-packages built for 13.5 and 14.3 as well.
    armv7 and the rest are not building such at all, according to <https://people.freebsd.org/~dbaio/pkg-master-report.html> and what it
    shows for " latest " and " quarterly ", no _ in those Set names.)

    And, different FreeBSD build servers can use different versions of the port-tree's in overlapping time frames for build activity. So each combination can get into dealing with that type of distinction as well.

    Are the *.tar.gz based on using the same OPTIONS settings as for
    official builds? What about other configuration details that might
    change the build results?

    So why recompile?
    See above and more later below.

    I want to take his *.tar.gz
    file, extract and do the needed post-install steps.-a The end should a
    "normal" package usable for FreeBSD :-)

    The first steps of this approach seems to work...-a I would like to check
    before I submit and before other people would confirm, that it works.

    What do you think?-a This way is more easy and does not use a long
    compilation time - just seconds for download and prepare.-a And it is
    less error lasting ;-)
    I doubt that taking externally built binaries not built by the FreeBSD port-package build servers from a port that uses source code would be an acceptable security risk for the official FreeBSD ports folks to allow such.

    Also, it is not obvious that an externally built port-package is always
    built in a fully compatible way with the officially built dependencies
    that would be involved in each and every official bulk build. A similar
    point goes for various combinations listed above possibly using
    different tool chains to do builds. Also, how would the update timing
    manage to match with the FreeBSD build server bulk build runs for each
    of those combinations listed earlier? (They various combinations are not synchronized and, overall, span widely distinct build time frames.)

    Some port-packages that have java/eclipse as a dependency may also
    otherwise depend on some of the same dependencies that java/eclipse
    does. Mismatched versions of those need not be coherent for overall
    operation to actually run and work.

    At various times, quarterly and latest need not match for what versions
    of dependencies and/or tool-chains are needed.

    There is a lot involved in keeping the official port-package build combinations operational. Things to not arbitrarily mix and match in a working way.

    Of course I will depend on this github repository and data.-a But that I
    did the last versions, too...

    Regards, Norbert

    On 3/13/26 13:52, Ronald Klop wrote:
    Rereading your mail I saw some more concerns you mention.

    1. When developing your port for main it can be easier to install
    dependencies for main also. That gives consistency to what is upstream.
    2. As long as the maintainer of maven39 does not merge the changes to
    the quarterly branch, you don't need to do anything for quarterly. But
    keep the 4.38 tag unchanged in github.
    3. Your https://github.com/NorbertXYZ/eclipse repo has a nice
    README.md, maybe add something similar to the eclipse-maven repo with
    instructions to your future self on how you did things. EfyC I totally
    recognize going back to some project years later and wondering how
    things worked.

    If you get stuck, there are probably some people here or on java@ that
    want to help further.

    NB: it can really help to keep ports@ in the cc:, if you want feedback
    from others too.

    Regards,
    Ronald.




    --
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Norbert Grundmann@ngrundmann@gmx.de to muc.lists.freebsd.ports on Sun Mar 15 07:44:00 2026
    From Newsgroup: muc.lists.freebsd.ports

    ...coming back and asking for advice how to handle that the build of java/eclipse depends on the version of maven39.-a 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...-a The architecture like aarch64 or amd64
    does not matter.
    To build I made a repository-ahttps://github.com/NorbertXYZ/eclipse-maven
    on github getting the maven dependencies...-a 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.-a So I will keep "the old" way and integrate that there is a
    maven upgrade which affects newer builds...

    Regards, Norbert

    On 3/14/26 22:09, Mark Millard wrote:
    On 3/14/26 08:32, Norbert Grundmann wrote:
    Hello Ronald,

    thanks for the comments...-a :-)

    I think I will take another approach to build eclipse in future on
    FreeBSD.-a About 2-3 year ago I made a lot patches to make version 4.32
    work - the previous one was 4.24.-a It took a lot of hours. After months >>> someone took over and created a github repository with FreeBSD stuff,
    which I took as the basis.-a The maintainer of that repo also creates
    *.tar.gz files which contain a full FreeBSD compilation / package, but
    not usable the pkg way.
    [My notes/questions below are general/generic, not based in a detailed
    analysis of java/eclipse details.]

    Such a file exists that includes the compilation/package for each and
    every combination of the following? [as things stand now]:

    ) supported arch for the port-package
    -a-a (amd64 vs. aarch64 vs. i386 . . .)

    ) quarterly [2026Q1] (all but main below)
    -a-a vs. latest (all 4 of the below, including main)

    ) 13.5, 14.3 (14.4 next), 15.0 (15.1 next), and main [so: 16.0 for now]

    Even limited to tier 1 platforms (amd64 and aarch64) that is 2*(3+4)==14
    combinations that each have a separate port-package built and
    distributed by-athe official FreeBSD build servers. Are all of those
    covered?

    (i386 is still having port-packages built for 13.5 and 14.3 as well.
    armv7 and the rest are not building such at all, according to
    <https://people.freebsd.org/~dbaio/pkg-master-report.html> and what it
    shows for " latest " and " quarterly ", no _ in those Set names.)

    And, different FreeBSD build servers can use different versions of the
    port-tree's in overlapping time frames for build activity. So each
    combination can get into dealing with that type of distinction as well.

    Are the *.tar.gz based on using the same OPTIONS settings as for
    official builds? What about other configuration details that might
    change the build results?

    So why recompile?
    See above and more later below.

    I want to take his *.tar.gz
    file, extract and do the needed post-install steps.-a The end should a
    "normal" package usable for FreeBSD :-)

    The first steps of this approach seems to work...-a I would like to
    check
    before I submit and before other people would confirm, that it works.

    What do you think?-a This way is more easy and does not use a long
    compilation time - just seconds for download and prepare.-a And it is
    less error lasting ;-)
    I doubt that taking externally built binaries not built by the FreeBSD
    port-package build servers from a port that uses source code would be an
    acceptable security risk for the official FreeBSD ports folks to
    allow such.

    Also, it is not obvious that an externally built port-package is always
    built in a fully compatible way with the officially built dependencies
    that would be involved in each and every official bulk build. A similar
    point goes for various combinations listed above possibly using
    different tool chains to do builds. Also, how would the update timing
    manage to match with the FreeBSD build server bulk build runs for each
    of those combinations listed earlier? (They various combinations are not
    synchronized and, overall, span widely distinct build time frames.)

    Some port-packages that have java/eclipse as a dependency may also
    otherwise depend on some of the same dependencies that java/eclipse
    does. Mismatched versions of those need not be coherent for overall
    operation to actually run and work.

    At various times, quarterly and latest need not match for what versions
    of dependencies and/or tool-chains are needed.

    There is a lot involved in keeping the official port-package build
    combinations operational. Things to not arbitrarily mix and match in a
    working way.

    Of course I will depend on this github repository and data.-a But that I >>> did the last versions, too...

    Regards, Norbert

    On 3/13/26 13:52, Ronald Klop wrote:
    Rereading your mail I saw some more concerns you mention.

    1. When developing your port for main it can be easier to install
    dependencies for main also. That gives consistency to what is
    upstream.
    2. As long as the maintainer of maven39 does not merge the changes to
    the quarterly branch, you don't need to do anything for quarterly. But >>>> keep the 4.38 tag unchanged in github.
    3. Your https://github.com/NorbertXYZ/eclipse repo has a nice
    README.md, maybe add something similar to the eclipse-maven repo with
    instructions to your future self on how you did things. EfyC I totally >>>> recognize going back to some project years later and wondering how
    things worked.

    If you get stuck, there are probably some people here or on java@ that >>>> want to help further.

    NB: it can really help to keep ports@ in the cc:, if you want feedback >>>> from others too.

    Regards,
    Ronald.




    --
    I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Vladimir Druzenko@vvd@freebsd.org to muc.lists.freebsd.ports on Fri Mar 20 18:45:44 2026
    From Newsgroup: muc.lists.freebsd.ports

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------DwZ4c0qDl3DQSa5mdxx80Df5
    Content-Type: multipart/mixed; boundary="------------0oo0bHkbxRntr03laeW9Z3fb";
    protected-headers="v1"
    Message-ID: <cd13607f-de34-419c-aa22-a7eb68d18159@freebsd.org>
    Date: Fri, 20 Mar 2026 18:45:44 +0300
    MIME-Version: 1.0
    User-Agent: Mozilla Thunderbird
    Subject: Re: Question for java/eclipse build
    To: Norbert Grundmann <ngrundmann@gmx.de>
    Cc: Mark Millard <marklmi@yahoo.com>, ports@freebsd.org,
    Ronald Klop <ronald-lists@klop.ws>, michaelo@apache.org,
    Michael Osipov <michaelo@FreeBSD.org>
    References: <777347484.15884.1773388311480@localhost>
    <b889c5d2-f780-4327-b1e1-cf15b5d14f2b@gmx.de>
    <50497640.911.1773405333508@localhost>
    <269fca85-395d-4cfe-8d42-a509b5b1ee44@gmx.de>
    <183908715.1270.1773406336228@localhost>
    <a31865c2-a807-48b0-8db6-3e509d351014@gmx.de>
    <ef941fe8-09ea-41eb-8a3d-9ba2590b47af@yahoo.com>
    <acd03710-5b59-4ce0-a285-18bfc51b6097@gmx.de>
    <1dc16c7e-37ef-4057-878e-f5c7c8dc5355@gmx.de>
    Content-Language: ru, en-US
    From: Vladimir Druzenko <vvd@freebsd.org>
    Autocrypt: addr=vvd@freebsd.org; keydata=
    xjMEZEmcEhYJKwYBBAHaRw8BAQdAzzVRU/u5Oe4kUEFSvaiRoAPwsXMi4uBnfKqFTOIxjaDN
    I1ZsYWRpbWlyIERydXplbmtvIDx2dmRAZnJlZWJzZC5vcmc+wo8EExYIADcWIQQJVt5Qnq2d
    fk5hjMKABvqrv5QvcwUCZEmcEgUJBaOagAIbAwQLCQgHBRUICQoLBRYCAwEAAAoJEIAG+qu/
    lC9z/qcBALviJppCfpN8fLj5HfnQ75ARS/RvOL+bPHB422uv9PFOAP982mg4uqoYr1BvSVqm
    rtB7/oxkqReIeieBIkyBTM97As44BGRJnBMSCisGAQQBl1UBBQEBB0D41GJgPsXUyWQckRf7
    25z8CsGADMjlIpJbVhWUQLi4fwMBCAfCfgQYFggAJhYhBAlW3lCerZ1+TmGMwoAG+qu/lC9z
    BQJkSZwTBQkFo5qAAhsMAAoJEIAG+qu/lC9z4bgA/jGNXk0cGGKii1lXk55Gwh2EQhC4pLxQ
    e/36TZiR29IBAP40fSUJOJ41IS0d8k6d5DQ0E9BJuRf+1S5AzsAUz0rmBQ==
    In-Reply-To: <1dc16c7e-37ef-4057-878e-f5c7c8dc5355@gmx.de>

    --------------0oo0bHkbxRntr03laeW9Z3fb
    Content-Type: multipart/mixed; boundary="------------3HsI28n06KZIGoPG28e62Tio"

    --------------3HsI28n06KZIGoPG28e62Tio
    Content-Type: multipart/alternative;
    boundary="------------oxd8WJMYQCTpcYc5P0eeccyD"

    --------------oxd8WJMYQCTpcYc5P0eeccyD
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGVsbG8hDQoNCkl04oCZcyBwcm9iYWJseSBiZXR0ZXIgdG8gc2ltcGx5IHVwZGF0ZSB5b3Vy IE1hdmVuIHJlcG9zaXRvcnkgd2l0aCBlYWNoIA0KaW5jb21wYXRpYmxlIGRldmVsL21hdmVu MzkgdXBkYXRlIGFuZCBtYWtlIGEgbmV3IHRhZyB3aXRoIHRoZSBuZXcgDQp2ZXJzaW9uLiBV cGRhdGUgdGhlIHRhZyBuYW1lIGluIHRoZSBwb3J0LiBBbmQgYXNrIHRoZcKgZGV2ZWwvbWF2 ZW4zOSANCm1haW50YWluZXIgKG1pY2hhZWxvQGFwYWNoZS5vcmcpIHRvIG5vdGlmeSB5b3Ug YmVmb3JlIHVwZGF0aW5nIHNvIHRoYXQgDQp0aGUgdXBkYXRlcyBhcmUgY29tbWl0dGVkIHN5 bmNocm9ub3VzbHkuIEZvciBleGFtcGxlLCBoZSBjYW4gY3JlYXRlIGEgUFIgDQp3aXRoIHRo ZSB0b3BpYyAiamF2YS9lY2xpcHNlOiBVcGRhdGXCoGRldmVsL21hdmVuMzkiIHRoYXTCoGRl dmVsL21hdmVuMzkgDQp3aWxsIGJlIHVwZGF0ZWQgb24gc3VjaCBhbmQgc3VjaCBhIGRheSwg YW5kIHdpbGwgYXR0YWNoIGEgcGF0Y2ggc28gdGhhdCANCnlvdSBjYW4gYXBwbHkgaXQgYW5k IHByZXBhcmUgYSBuZXcgcmVwb3NpdG9yeS4gQW5kIHRoZW4gY29tbWl0IHRoZSANCnVwZGF0 ZXMgYXQgdGhlIHNhbWUgdGltZS4NCg0KQUZBSVIgbWljaGFlbG9AYXBhY2hlLm9yZ8KgPT0g bWljaGFlbG9ARnJlZUJTRC5vcmcgYW5kIGhhdmUgY29tbWl0IGJpdCB0byANCnBvcnRzLg0K DQoxNS4wMy4yMDI2IDA5OjQ0LCBOb3JiZXJ0IEdydW5kbWFubiDQv9C40YjQtdGCOg0KPiAu Li5jb21pbmcgYmFjayBhbmQgYXNraW5nIGZvciBhZHZpY2UgaG93IHRvIGhhbmRsZSB0aGF0 IHRoZSBidWlsZCBvZiANCj4gamF2YS9lY2xpcHNlIGRlcGVuZHMgb24gdGhlIHZlcnNpb24g b2YgbWF2ZW4zOS7CoCBUaGUgbmV3IGVjbGlwc2UgNC4zOSANCj4gcG9ydCBidWlsZCBvbiBx dWF0ZXJseSBpbnN0YWxsZWQgZGVwZW5kZWQgcGFja2FnZXMgaXMgZmluZSB3aXRoIA0KPiBt YXZlbjM5IHZlcnNpb24gMy45LjEyIGJ1dCBicmVha3Mgd2l0aCB2ZXJzaW9uIDMuOS4xMyAt IHRoYXQgaXMgdGhlIA0KPiBzYW1lIGZvciBvbGRlciBlY2xpcHNlIHZlcnNpb24gNC4zOC4u LsKgIFRoZSBhcmNoaXRlY3R1cmUgbGlrZSBhYXJjaDY0IA0KPiBvciBhbWQ2NCBkb2VzIG5v dCBtYXR0ZXIuDQo+DQo+IFRvIGJ1aWxkIEkgbWFkZSBhIHJlcG9zaXRvcnkgDQo+IGh0dHBz Oi8vZ2l0aHViLmNvbS9Ob3JiZXJ0WFlaL2VjbGlwc2UtbWF2ZW4gb24gZ2l0aHViIGdldHRp bmcgdGhlIA0KPiBtYXZlbiBkZXBlbmRlbmNpZXMuLi7CoCBTbyB0aGUgYnVpbGQgcHJvY2Vz cyBkb2VzIG5vdCBkb3dubG9hZCBmaWxlcy4NCj4NCj4gVGhhbmtzIGZvciByZW1hcmtzIC0g SSBhbSBub3QgY2xlYXIgaG93IHRvIGhhbmRsZSB0aGlzIGEgZ29vZCB3YXksIG15IA0KPiBh cHByb2FjaCBvZiB0YWtpbmcgYSBwcmVwYXJlZCBGcmVlQlNEICoudGFyLmd6IGZpbGUgaXMg bm90IHRvIGEgZ29vZCANCj4gaWRlYS4NCj4NCj4gUmVnYXJkcywgTm9yYmVydA0KPg0KPg0K PiBPbiAzLzE1LzI2IDA2OjU0LCBOb3JiZXJ0IEdydW5kbWFubiB3cm90ZToNCj4+IHRoYW5r cy7CoCBTbyBJIHdpbGwga2VlcCAidGhlIG9sZCIgd2F5IGFuZCBpbnRlZ3JhdGUgdGhhdCB0 aGVyZSBpcyBhIA0KPj4gbWF2ZW4gdXBncmFkZSB3aGljaCBhZmZlY3RzIG5ld2VyIGJ1aWxk cy4uLg0KPj4NCj4+IFJlZ2FyZHMsIE5vcmJlcnQNCg0KDQotLSANCkJlc3QgcmVnYXJkcywN ClZsYWRpbWlyIERydXplbmtvDQoNCg==
    --------------oxd8WJMYQCTpcYc5P0eeccyD
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html>
    <html>
    <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=

    </head>
    <body>
    <div class=3D"moz-cite-prefix">Hello!</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">It=E2=80=99s 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=C2=A0devel/maven39 maintainer (<span
    style=3D"font-family:monospace"><span
    style=3D"color:#000000;background-color:#ffffff;"><a class=3D"m= oz-txt-link-abbreviated" href=3D"mailto:michaelo@apache.org">michaelo@apa= che.org</a></span></span>)
    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=C2=A0devel/maven39" that=C2=A0devel/maven39 w=
    ill 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.</div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix"><span style=3D"font-family:monospace">= <span
    style=3D"color:#000000;background-color:#ffffff;">AFAIR
    <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:michaelo@a= pache.org">michaelo@apache.org</a></span>=C2=A0=3D=3D=C2=A0</span><span
    style=3D"font-family:monospace"><span
    style=3D"color:#000000;background-color:#ffffff;"><a class=3D"m= oz-txt-link-abbreviated" href=3D"mailto:michaelo@FreeBSD.org">michaelo@Fr= eeBSD.org</a>
    and have commit bit to ports.</span></span></div>
    <div class=3D"moz-cite-prefix"><br>
    </div>
    <div class=3D"moz-cite-prefix">15.03.2026 09:44, Norbert Grundmann
    =D0=BF=D0=B8=D1=88=D0=B5=D1=82:<br>
    </div>
    <blockquote type=3D"cite"
    cite=3D"mid:1dc16c7e-37ef-4057-878e-f5c7c8dc5355@gmx.de">...coming
    back and asking for advice how to handle that the build of
    java/eclipse depends on the version of maven39.=C2=A0 The new eclip=
    se
    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...=C2=A0 The architectur=
    e
    like aarch64 or amd64 does not matter.
    <br>
    <br>
    To build I made a
    repository=C2=A0<a class=3D"moz-txt-link-freetext" href=3D"https://= github.com/NorbertXYZ/eclipse-maven">https://github.com/NorbertXYZ/eclips= e-maven</a> on github
    getting the maven dependencies...=C2=A0 So the build process does n=
    ot
    download files.
    <br>
    <br>
    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.
    <br>
    <br>
    Regards, Norbert
    <br>
    <br>
    <br>
    On 3/15/26 06:54, Norbert Grundmann wrote:
    <br>
    <blockquote type=3D"cite">thanks.=C2=A0 So I will keep "the old" wa=
    y and
    integrate that there is a maven upgrade which affects newer
    builds...
    <br>
    <br>
    Regards, Norbert</blockquote>
    </blockquote>
    <p><br>
    </p>
    <pre class=3D"moz-signature" cols=3D"72">--=20
    Best regards,
    Vladimir Druzenko</pre>
    </body>
    </html>

    --------------oxd8WJMYQCTpcYc5P0eeccyD--

    --------------3HsI28n06KZIGoPG28e62Tio
    Content-Type: application/pgp-keys; name="OpenPGP_0x8006FAABBF942F73.asc" Content-Disposition: attachment; filename="OpenPGP_0x8006FAABBF942F73.asc" Content-Description: OpenPGP public key
    Content-Transfer-Encoding: quoted-printable

    -----BEGIN PGP PUBLIC KEY BLOCK-----

    xjMEZEmcEhYJKwYBBAHaRw8BAQdAzzVRU/u5Oe4kUEFSvaiRoAPwsXMi4uBnfKqF TOIxjaDNI1ZsYWRpbWlyIERydXplbmtvIDx2dmRAZnJlZWJzZC5vcmc+wo8EExYI ADcWIQQJVt5Qnq2dfk5hjMKABvqrv5QvcwUCZEmcEgUJBaOagAIbAwQLCQgHBRUI CQoLBRYCAwEAAAoJEIAG+qu/lC9z/qcBALviJppCfpN8fLj5HfnQ75ARS/RvOL+b PHB422uv9PFOAP982mg4uqoYr1BvSVqmrtB7/oxkqReIeieBIkyBTM97As44BGRJ nBMSCisGAQQBl1UBBQEBB0D41GJgPsXUyWQckRf725z8CsGADMjlIpJbVhWUQLi4 fwMBCAfCfgQYFggAJhYhBAlW3lCerZ1+TmGMwoAG+qu/lC9zBQJkSZwTBQkFo5qA AhsMAAoJEIAG+qu/lC9z4bgA/jGNXk0cGGKii1lXk55Gwh2EQhC4pLxQe/36TZiR 29IBAP40fSUJOJ41IS0d8k6d5DQ0E9BJuRf+1S5AzsAUz0rmBQ=3D=3D
    =3Dx+2b
    -----END PGP PUBLIC KEY BLOCK-----

    --------------3HsI28n06KZIGoPG28e62Tio--

    --------------0oo0bHkbxRntr03laeW9Z3fb--

    --------------DwZ4c0qDl3DQSa5mdxx80Df5
    Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature
    Content-Disposition: attachment; filename="OpenPGP_signature.asc"

    -----BEGIN PGP SIGNATURE-----

    wnsEABYIACMWIQQJVt5Qnq2dfk5hjMKABvqrv5QvcwUCab1rqQUDAAAAAAAKCRCABvqrv5QvczW9 AQD1xxrWO9cwU25lkoCW5T3irol69BMMEsJpgx8yUlTsSAEAvVRiLzD6L9f/6I6P5wLU7aGos1Zi v7x8bDiq9KanXgo=
    =KEgG
    -----END PGP SIGNATURE-----

    --------------DwZ4c0qDl3DQSa5mdxx80Df5--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Norbert Grundmann@ngrundmann@gmx.de to muc.lists.freebsd.ports on Sat Mar 21 07:50:55 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi Michael,
    thanks for your reply :-)-a I hope I did not make to much trouble - but I think it is solved now with eclipse and maven.-a And yes it was the
    change between maven *.12 and *.13, what you wrote is a resolver
    change.-a 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.-a I will continue the way I did-a
    till now - but now I know the reason of failure.-a Maybe I can or need to integrate different maven versions into "my" eclipse-maven repository in special tag names??!-a But that would make a lot of data...
    I am free for good solutions or corrections :-)-a 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!

    ItrCOs 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-adevel/maven39
    maintainer (michaelo@apache.org) 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-adevel/maven39"
    that-adevel/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 michaelo@apache.org-a== michaelo@FreeBSD.org and have commit bit
    to ports.

    15.03.2026 09:44, Norbert Grundmann -+-+-e-|-e:
    ...coming back and asking for advice how to handle that the build of
    java/eclipse depends on the version of maven39.-a 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...-a 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...-a 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.-a 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 :)
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21f-Linux NewsLink 1.2