-
Notifications
You must be signed in to change notification settings - Fork 83
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.
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
Toggle OSGi and Eclipse plugin creation options appropriately #800
Conversation
If one creates plugins using the automatic manifest generation feature, subsequent plugin projects created with Eclipse as the target is throwing errors, due to the 'Generate OSGi metadata automatically' button not being unchecked. This commit tries to resolve this issue by unchecking the feature whwnever an Eclipse plugin project using templates is created.
Test Results 30 files - 237 30 suites - 237 0s ⏱️ - 48m 21s Results for commit fd68e09. ± Comparison against base commit 27cf508. This pull request removes 3319 tests.
|
change looks good, build is failing due to issue mentioned in #782 |
I think this is better fixed with: |
@@ -167,6 +167,7 @@ private void updateAutomatic() { | |||
private void updateRuntimeDependency() { | |||
boolean depends = fEclipseButton.getSelection(); | |||
fOSGiCombo.setEnabled(!depends); | |||
useAutomaticMetadata.setSelection(!depends); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems not very useful as we actually save this so it can be reused afterwards, it would be better to fix the place where having this option active causes trouble.
@alshamams I just merged a fix for this can you verify if it solves your problem? In the meanwhile I'll close this PR. |
If one creates plugins using the automatic manifest generation feature,
subsequent plugin projects created with Eclipse as the target is throwing errors, due to the 'Generate OSGi metadata automatically' button not being unchecked. This commit tries to resolve this issue by unchecking the feature whwnever an Eclipse plugin project using templates is created.
Fixes: #798