What I used to do in this case is to download the txz package file from an older package repository found here.
pkg.freebsd.org
Unfortunately access has now been blocked and you cannot see the names of the packages.
So now I know of no way to grab old packages.
In the past I would have fetched eclipse.txz from an older repository and
pkg add
the file.
pkg will spit out what additional packages are needed to fulfill dependencies and I would fetch them as well.
It could be labor-some for a dependency heavy application but way quicker than building from ports.
It looks like pkg mirrors are not allowing indexes on folders anymore. For example https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/ now returns 403/Forbidden. Anybody knows why ?
forums.freebsd.org
There is one way you might be able to try.
Trick package into using an older repository.
Modify package path as found in
/etc/pkg/FreeBSD.conf to lead to an older repository.
This is the line that would need modification.
url: "pkg+
http://pkg.FreeBSD.org/${ABI}/quarterly",
Changed to something like this:
url: "pkg+
http://pkg.FreeBSD.org/${ABI}/release_0/quarterly",
As per this post:
I am probably missing something so any clarification is welcome. All I am using are current binary packages, nothing built from source. This already happened with firefox couple of months ago but it was quickly resolved when firefox reappeared. Now I am trying to install...
forums.freebsd.org
Once again it helps to be able to look at the package repositories too see which repository actually contained the needed version of Eclipse.
Now you will need to guess and pay attention to which version of the application pkg is going to install.
Some caveats to this method are: mixing older packages with newer will be trouble.
That was where
pkg add
shined. It would allow 2 versions of programs to exist. You could have an older library and newer library co-exist. You would need to lock the old packages to allow for pkg updating.
The version of FreeBSD used would also matter. You would need to research from Freshports when exactly the eclipse version was available and align that with the date that package was available. Then check the dates on FreeBSD releases for the /release_X version needed from the package repository.
There are ways to add FreeBSD 11 repository packages to FreeBSD 12 with an env setting.
After you get eclipse running you will need
pkg lock
eclipse and it dependencies and revert
/etc/pkg/FreeBSD.conf back.