Sorry, entering a bug into the product JDT has been disabled.

I think concretely it would be nice to have (conversely really horrible not to have) a redirection link to where an issue should be opened as an alternative to Bugzilla.

Looks like that entire list of options related to bugs need to be updated.

mentioned in issue eclipsefdn/it/websites/projects.eclipse.org#90 (closed)

I've updated JDTs product description in Bugzilla to point people at Github. I've also removed the Bugzilla details from the PMI which removes the report bug/helpwanted bugs etc. list from the PMI.

However I think we can agree that this is somewhat sub-optimal because now we are providing no hints at all on where bugs should go. I've filed an issue against the PMI to discuss where/how we should point people at the right issue tracker.

As a workaround I have added the following blurp to https://projects.eclipse.org/projects/eclipse.jdt/developer:

The Bugzilla JDT components have been disabled.

Please file issues here:

    APT - https://github.com/eclipse-jdt/eclipse.jdt.core/issues
    Core - https://github.com/eclipse-jdt/eclipse.jdt.core/issues
    Debug - https://github.com/eclipse-jdt/eclipse.jdt.debug/issues
    Doc - https://github.com/eclipse-jdt/eclipse.jdt/issues
    Text - https://github.com/eclipse-jdt/eclipse.jdt.ui/issues
    UI - https://github.com/eclipse-jdt/eclipse.jdt.ui/issues

List was taken from #1169 (comment 679861)

added Bugzilla Migration ~16280 labels

People trying to file a JDT bug directly from https://bugs.eclipse.org will get even less information: they will chase the selection of products just to wreck their brain in search of JDT (and platform for that matter). Since our most valuable bug reporters are used to this latter path, not showing any sign sends the message that JDT no longer exists? is no longer interested in bug reports?

As per #1169 (closed) I did adapt https://bugs.eclipse.org/bugs/describecomponents.cgi?product=JDT to show links to GitHub issues for the JDT product and components.

Due to limitations or opinionated choices, Bugzilla does not show products or components if no components are open for entering bugs. So JDT and Platform disappeared from the list here:
https://bugs.eclipse.org/bugs/enter_bug.cgi?classification=Eclipse%20Project

I've edited the "Eclipse Project" Bugzilla classification to point to GitHub issues for those two components.
=> https://bugs.eclipse.org/bugs/enter_bug.cgi?classification=Eclipse%20Project

Thank you. These all look like really nice improvements!

Looks much better to me now, just one bookmark still not looking good: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT - I'm sure there are still links pointing to it.

After the debate on the mailing list has escalated, I'd like to add that I do see a severe failure in planning (I'm not in favor of letting the community sort out all issues after things have gone wrong), but I explicitly won't blame foundation staff. Their need to focus is well understood (albeit deplorable), and it's not their job to plan migration paths of projects in detail. I could still add a ton of questions that should have been answered before disabling bugzilla, but haven't been answered yet.

thanks

I'll create some redirects. I agree that dead end links are just bad.

Part of planning a project's migration should be communication within the project -- not just committers to committers, but to forums and mailing list for contributors and the project's own community. I feel this communication is an opportunity for project leads to engage with their communities.

Other questions and comments, ideas, feedback, can be posted to the plan of the plan: #678

Here's another tricky one: I just got the following helpful exception logged from Eclipse:

SWT call to Webkit timed out after 10000ms. No return value will be provided.
Possible reasons:
1) Problem: Your javascript needs more than 10000ms to execute.
   Solution: Don't run such javascript, it blocks Eclipse's UI. SWT currently allows such code to complete, but this error is thrown 
     and the return value of execute()/evalute() will be false/null.

2) However, if you believe that your application should execute as expected (in under10000 ms),
 then it might be a deadlock in SWT/Browser/webkit2 logic.
 I.e, it might be a bug in SWT (e.g this does not occur on Windows/Cocoa, but occurs on Linux). If you believe it to be a bug in SWT, then
Please report this issue *with steps to reproduce* via:
 https://bugs.eclipse.org/bugs/enter_bug.cgi?alias=&assigned_to=platform-swt-inbox%40eclipse.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=&component=SWT&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-1=X&flag_type-11=X&flag_type-12=X&flag_type-13=X&flag_type-14=X&flag_type-15=X&flag_type-16=X&flag_type-2=X&flag_type-4=X&flag_type-6=X&flag_type-7=X&flag_type-8=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&product=Platform&qa_contact=&rep_platform=PC&requestee_type-1=&requestee_type-2=&short_desc=webkit2_BrowserProblem
For bug report, please atatch this stack trace:
...

For obvious reason, that URL -- hardcoded in existing, published software -- gives the equivalent answer:

Sorry, entering a bug into the product Platform has been disabled.

It seems all the helpful detail hints are irrecoverably wasted at this point.

mentioned in issue #4086 (closed)

assigned to @chills2023

added statewip label

Hello @sherrmann , I pushed a new patch so that the redirect for new issues is working https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT

I'll close this issue, please reopen if you feel something is still not working right.

closed

Sorry, entering a bug into the product JDT has been disabled.

Designs

Child items ...

Activity