Skip to content

Plugin section via file import does not work as expected#1004

Open
subyssurendran666 wants to merge 1 commit intoeclipse-equinox:masterfrom
subyssurendran666:plugin_section_via_file_import_not_as_expect_1003
Open

Plugin section via file import does not work as expected#1004
subyssurendran666 wants to merge 1 commit intoeclipse-equinox:masterfrom
subyssurendran666:plugin_section_via_file_import_not_as_expect_1003

Conversation

@subyssurendran666
Copy link

image

Changes the behavior so that no plugins are selected by default when importing from a p2f file. This allows users to explicitly select only the plugins they want to install.

Fix: #1003

@subyssurendran666
Copy link
Author

@merks could you please review this PR?

Changes the behavior so that no plugins are selected by default when
importing from a p2f file. This allows users to explicitly select only
the plugins they want to install.

Fix: eclipse-equinox#1003
@subyssurendran666 subyssurendran666 force-pushed the plugin_section_via_file_import_not_as_expect_1003 branch from ddacb61 to 93bac43 Compare March 16, 2026 15:21
@subyssurendran666
Copy link
Author

@laeubi Could you please trigger the GitHub Copilot review for this PR?

@iloveeclipse
Copy link
Member

Changes the behavior so that no plugins are selected by default when importing from a p2f file. This allows users to explicitly select only the plugins they want to install.

This is bad proposal & wrong solution. I want everything to be installed, I don't want to explicitly select anything, because the file in question has all what I need, and I do this literally every day.

Copy link
Member

@iloveeclipse iloveeclipse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As explained, it is not a solution for the problem.

@subyssurendran666
Copy link
Author

Changes the behavior so that no plugins are selected by default when importing from a p2f file. This allows users to explicitly select only the plugins they want to install.

This is bad proposal & wrong solution. I want everything to be installed, I don't want to explicitly select anything, because the file in question has all what I need, and I do this literally every day.

One situation I faced while setting up JDT.UI was that I only needed AssertJ and Mockito. However, the p2f file contains many other plugins as well. In that case, I had to manually deselect the unwanted plugins, or click “Deselect All” and then select only the required plugins. Because of this, the auto-selection process irritated me multiple times while setting up JDT.UI.

The actual problem was slightly different. In the existing implementation, all plugins are selected by default. If the user clicks “Deselect All” and then tries to select the required plugin, all the plugins get auto-selected again, and the plugin that the user manually selected becomes deselected.

To avoid this issue, I set all plugins to be deselected by default, and the problem was resolved. These are the reasons why I implemented it this way.

I am open to implementing this in a different way, but auto-selecting all plugins by default can definitely cause inconvenience for users who do not need all the plugins.

@iloveeclipse
Copy link
Member

If the user clicks “Deselect All” and then tries to select the required plugin, all the plugins get auto-selected again,

This is the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plugin selection from File → Import via p2f file does not work as expected.

2 participants