Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BundleActivator.start called twice from the extension bundle #450

Closed
yaohaizh opened this issue Nov 20, 2017 · 1 comment
Closed

BundleActivator.start called twice from the extension bundle #450

yaohaizh opened this issue Nov 20, 2017 · 1 comment
Assignees
@gorkem
Labels
bug
Milestone
End November 2017

Comments

@yaohaizh
Copy link
Contributor

With the change in the BundleUtils' start method without Bundle.START_ACTIVATION_POLICY in

         bundle.start()

The debugger plugin start called twice

  1. First one on the BundleUtil
  2. Second one on the DelegateCommandHandlerDescriptor

Is this the design behavior for BundleActivator.start? Should we avoid this multiple issue on the start or with Bundle.START_ACTIVATION_POLICY?

@gorkem @fbricon
@fbricon fbricon added the bug label Nov 20, 2017
@yaohaizh yaohaizh mentioned this issue Nov 21, 2017
Closed
@gorkem gorkem mentioned this issue Nov 24, 2017
Closed
@gorkem
Copy link
Contributor

gorkem commented Nov 25, 2017

fixed with #463

@gorkem gorkem closed this as completed Nov 25, 2017
@fbricon fbricon added this to the End November 2017 milestone Nov 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gorkem gorkem

Labels
bug
Projects
None yet
Milestone
End November 2017
Development

Successfully merging a pull request may close this issue.

Start bundles with START_ACTIVATION_POLICY gorkem/eclipse.jdt.ls
3 participants
@gorkem @fbricon @yaohaizh