Works for me, installing from koji buildroot with "mock -r fedora-rawhide-x86_64 --enablerepo=local --install eclipse-pde"

Actually, `--enablerepo=local` only adds the Koji buildroot repo, while outdated rawhide repos are still available. Use `--disablerepo='*' --enablerepo=local` to replicate the Koji buildroot situation:

$ mock -r fedora-rawhide-x86_64 --disablerepo='*' --enablerepo=local --install eclipse-pde
Error: 
 Problem: conflicting requests
  - nothing provides osgi(org.objectweb.asm) needed by eclipse-pde-1:4.19-5.fc35.x86_64
  - nothing provides osgi(org.objectweb.asm.tree) needed by eclipse-pde-1:4.19-5.fc35.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

$ mock -r fedora-rawhide-x86_64 --disablerepo='*' --enablerepo=local --install eclipse-jdt
...
Error: 
 Problem: conflicting requests
  - nothing provides osgi(org.hamcrest.core) needed by eclipse-jdt-1:4.19-5.fc35.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

(In reply to Miro Hrončok from comment #3)
> $ mock -r fedora-rawhide-x86_64 --disablerepo='*' --enablerepo=local
> --install eclipse-jdt
> ...
> Error: 
>  Problem: conflicting requests
>   - nothing provides osgi(org.hamcrest.core) needed by
> eclipse-jdt-1:4.19-5.fc35.noarch
> (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to
> use not only best candidate packages)



I see, it would have been useful to include reproduction instructions in the bug you filed.

Yes indeed. I thought the same and adapting the bug template is on my TODO.

Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

Hello,

This is the second reminder (step 4 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

"osgi(org.hamcrest.core)" is hamcrest-core , this maybe happens because hamcrest2 was retired [1] and hamcrest [2] is now  hamcrest-2.2-4.fc35 


[1] 
https://src.fedoraproject.org/rpms/hamcrest2

[2]
https://src.fedoraproject.org/rpms/hamcrest

It is likely that hamcrest upgrade to version 2 changed OSGi metadata or broke OSGi provides. 
If there are any hamcrest changes needed to fix eclipse, please open a bug against hamcrest package.

Trying help here with some information , yes new hamcrest broke OSGi provides [1] 
but is just need in requires [2] enabling bootstrap and try to build the build stops on [3] https://kojipkgs.fedoraproject.org//work/tasks/9222/71609222/build.log
and I guess that fix OSGi provides of hamcrest will not fix the build isn't it ? 


[1] 
dnf repoquery --disablerepo='*' --enablerepo=rawhide -q hamcrest --provides
hamcrest = 2.2-4.fc35
hamcrest-core = 2.2-4.fc35
mvn(org.hamcrest:hamcrest) = 2.2
mvn(org.hamcrest:hamcrest-all) = 2.2
mvn(org.hamcrest:hamcrest-all:pom:) = 2.2
mvn(org.hamcrest:hamcrest-core) = 2.2
mvn(org.hamcrest:hamcrest-core:pom:) = 2.2
mvn(org.hamcrest:hamcrest-library) = 2.2
mvn(org.hamcrest:hamcrest-library:pom:) = 2.2
mvn(org.hamcrest:hamcrest:pom:) = 2.2

[2]
-Requires:       osgi(org.hamcrest.core)
+Requires:       mvn(org.hamcrest:hamcrest-core)

[3] 
[WARNING] Error initializing: org.eclipse.tycho.p2.resolver.P2DependencyResolver@7a358613
java.lang.RuntimeException: java.lang.IllegalStateException: Service is not registered class='interface org.eclipse.tycho.core.shared.ProxyServiceFacade' 

https://kojipkgs.fedoraproject.org//work/tasks/9222/71609222/build.log

(In reply to Sergio Basto from comment #10)
> Trying help here with some information , yes new hamcrest broke OSGi
> provides [1] 
> but is just need in requires [2] enabling bootstrap and try to build the
> build stops on [3]
> https://kojipkgs.fedoraproject.org//work/tasks/9222/71609222/build.log
> and I guess that fix OSGi provides of hamcrest will not fix the build isn't
> it ? 
> 
> 
> [2]
> -Requires:       osgi(org.hamcrest.core)
> +Requires:       mvn(org.hamcrest:hamcrest-core)
> 

Change like ^^ will ensure that jar is there but without OSGi metadata it's useless from Eclipse POV. My team no longer has the manpower to maintain Eclipse in Fedora so it's up to community to pick it up. Mat is the official maintainer but he is no longer in the team so I don't know about his plans.

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

Hi,

I'm sorry if I'm wrong but isn't hamcrest version 2.* should be in "hamcrest2"?

"decathorpe" created it about a year ago, but orphaned it later due to lack of time.
Probably he's thinking that it's best to differentiate between the two?

link: https://src.fedoraproject.org/rpms/hamcrest2

Some information from this thread [1]

According Mikolaj Izdebski 
- eclipse can easily remove dependency on jmc.
- Only jmc directly depends on HdrHistogram, nothing else.
- Only jmc directly depends on jmc-core
- Only jmc and jmc-core directly depend on owasp-java-encoder, nothing else.

[1] https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject.org/message/ZZNAIUM2EB6WK5J65TPD7DRHP2LH327C/

Sergio, are you working on this?

This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

(In reply to Miro Hrončok from comment #17)
> Sergio, are you working on this?

not really, I'm kjust trying understand the problem , now trying build eclipse on rawhide we got [1] even with bootstrap enabled 

jakarta.annotation-api on F35 stopped to provide osgi(jakarta.annotation-api) , without any great modification of the spec ... 

and eclipse-platform is part of eclipse.src.rpm so this is in loop .
eclipse-ecf-core requires eclipse-platform ( "osgi(org.eclipse.core.net)" )  

cbi-plugins requires tycho which requires eclipse-platform, any tip ? 

[1]
Error:
Problem 1: package tycho-2.2.0-4.fc34.noarch requires eclipse-platform >= 1:4.17, but none of the providers can be installed
- conflicting requests
- nothing provides osgi(jakarta.annotation-api) needed by eclipse-platform-1:4.19-5.fc35.x86_64
Problem 2: package eclipse-ecf-core-3.14.19-2.fc34.noarch requires osgi(org.eclipse.core.jobs), but none of the providers can be installed
- package eclipse-ecf-core-3.14.19-2.fc34.noarch requires osgi(org.eclipse.core.net), but none of the providers can be installed
- conflicting requests
- nothing provides osgi(jakarta.annotation-api) needed by eclipse-platform-1:4.19-5.fc35.x86_64
Problem 3: package cbi-plugins-1.1.7-10.fc35.noarch requires mvn(org.eclipse.tycho:tycho-core), but none of the providers can be installed
- package tycho-2.2.0-4.fc34.noarch requires eclipse-platform >= 1:4.17, but none of the providers can be installed
- conflicting requests
- nothing provides osgi(jakarta.annotation-api) needed by eclipse-platform-1:4.19-5.fc35.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

If somebody plans to actually fix this until Fedora 35 beta freeze, please assign this buzgilla to you and set ti to ASSIGNED or higher before 2021-08-17, otherwise this package will be retired. Unretiring it once fixed is possible as well.

I can't build tycho on F35/rawhide bug #1988028 , even if with local build of maven-install-plugin in buildroot, maven-install-plugin is retired and even if I enable bootstrap in tycho , also readd bnd-maven-plugin-5.2.0 in buildroot doesn't solve . 
error in tycho is similar when we try to eclipse [1] 

ah about the tip, seems we need build tycho with bootstrap , after eclipse with bootstrap, after tycho without bootstrap and finally eclipse without bootstrap.

But I don't see  way to solve this , I give up .


[1] 
[WARNING] Error initializing: org.eclipse.tycho.p2.resolver.P2DependencyResolver@443a06ad
java.lang.RuntimeException: java.lang.IllegalStateException: Service is not registered class='interface org.eclipse.tycho.core.shared.ProxyServiceFacade'

This package has been orphaned.

You can pick it up at https://src.fedoraproject.org/rpms/eclipse by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.

note, this breaks the Scientific_KDE spin, because it tries to pull in various of these eclipse subpackages which fail to install.

Automation has figured out the package is retired in Fedora 35.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement

what are the packages that are F35FailsToInstall now with this retirement , isn't all java stack ?

Packages that needed eclipse to install already failed to install because eclipse did not install, so there should be no much changed. Anyway, after the package is blocked in koji, new bugzillas will be reported.

Sergio, I will still keep ecj and jgit alive because other non-eclipse packages use them, and they are quite small and easy to maintain.

Only packages named eclipse-* should be failing. No other packages should have eclipse as part of their build process.

Created attachment 1815214 [details]
reults of retire of eclipse

eclips-swt is installed on my vm with F35 and the deps on mvn(org.eclipse.swt:swt) will remove java-1.8.0-openjdk which will remove maven ...

(In reply to Sergio Basto from comment #28)
> Created attachment 1815214 [details]
> reults of retire of eclipse
> 
> eclips-swt is installed on my vm with F35 and the deps on
> mvn(org.eclipse.swt:swt) will remove java-1.8.0-openjdk which will remove
> maven ...

Did you inspect the dep chain? It's probably only openjfx that needs fixing. File a bug against openjfx package to drop support for SWT.