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 :)
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 :)
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 :)
=20that 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=
Thanks a lot :-) :-) I will see...
=20
On 3/13/26 13:35, Ronald Klop wrote:
Hi,predefined maven
=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 =
running# download, so the build does not need to download while do-build is =
=20
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...
=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 -=
tree, but not in my computer :)=20
All the best, Norbert :-)
=20
--=20
I love penguins at the south pole, windows in my house and apples on my=
as DISTVERSION (4.38).=20=20
=20
=20
=20
=20
Your GH_TUPLE line defines a specific tag to use, which is now the same =
at in the main port and leave the quarterly port unchanged.NorbertXYZ:eclipse-maven:${DISTVERSION}:n
=20
A possible solution is to create a new tag in github (4.38_2) and use th=
ree, but not in my computer :)NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n=20
See: https://github.com/NorbertXYZ/eclipse-maven/tags
=20
I hope this helps.
=20
Regards,
Ronald.
=20
=20
--=20
I love penguins at the south pole, windows in my house and apples on my t=
Rereading your mail I saw some more concerns you mention.=20
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=
keep the 4.38 tag unchanged in github.otally=20
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=
recognize going back to some project years later and wondering how=20=20
things worked.
If you get stuck, there are probably some people here or on java@ that=
want to help further.=20
NB: it can really help to keep ports@ in the cc:, if you want feedback=
from others too.d
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=
uses preinstalled quaterly packages - that means also thell
"older" maven39 port.=C2=A0 My question is: if I would insta=
the newest packages from latest - would it fix the?=C2=A0
problem?=C2=A0 But what happens with poudiere runs for the
quaterly packages.=C2=A0 They would need "older" maven39, or=
and if I use software, I install packages from quaterly.=C2==A0
I am a bit confused about how to proceed...=2D-----------
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 :)
------------------------------------------------------------=
Your GH_TUPLE line defines a specific tag to use, which is nowmy tree, but not in my computer :)
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=
On 3/14/26 08:32, Norbert Grundmann wrote:
Hello Ronald,[My notes/questions below are general/generic, not based in a detailed analysis of java/eclipse details.]
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.
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.gzI 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.
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 ;-)
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.
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,[My notes/questions below are general/generic, not based in a detailed
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.
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.gzI doubt that taking externally built binaries not built by the FreeBSD
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 ;-)
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.
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
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 06:53:27 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
921 files (14,318M bytes) |
| Messages: | 264,771 |