Eclipse Neon for Eclipse Committers can't resolve org.eclipse
I recently upgraded to Eclipse Neon. I had a plugin project that built fine in Eclipse Luna, but now in neon, everywhere that I imported "org.eclipse."something I get an error:
The import org.eclipse cannot be resolved.
The plugin.xml has errors etc.
The Project build path has "Plugin Dependencies" on the build path.
My version of Eclipse is
Eclipse IDE for Eclipse Committers
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I'm running on MacOSX High Sierra.
It's probably something very simple.
java eclipse eclipse-plugin
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
add a comment |
I recently upgraded to Eclipse Neon. I had a plugin project that built fine in Eclipse Luna, but now in neon, everywhere that I imported "org.eclipse."something I get an error:
The import org.eclipse cannot be resolved.
The plugin.xml has errors etc.
The Project build path has "Plugin Dependencies" on the build path.
My version of Eclipse is
Eclipse IDE for Eclipse Committers
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I'm running on MacOSX High Sierra.
It's probably something very simple.
java eclipse eclipse-plugin
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
1
Maybe the dependencies inMETA-INF/MANIFEST.MFare bound to a very specific version and your target platform is the running platform (so no dependency can be resolved). By the way, also Neon is pretty old. The current version is Eclipse 2018-09.
– howlger
Nov 21 '18 at 22:03
add a comment |
I recently upgraded to Eclipse Neon. I had a plugin project that built fine in Eclipse Luna, but now in neon, everywhere that I imported "org.eclipse."something I get an error:
The import org.eclipse cannot be resolved.
The plugin.xml has errors etc.
The Project build path has "Plugin Dependencies" on the build path.
My version of Eclipse is
Eclipse IDE for Eclipse Committers
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I'm running on MacOSX High Sierra.
It's probably something very simple.
java eclipse eclipse-plugin
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
I recently upgraded to Eclipse Neon. I had a plugin project that built fine in Eclipse Luna, but now in neon, everywhere that I imported "org.eclipse."something I get an error:
The import org.eclipse cannot be resolved.
The plugin.xml has errors etc.
The Project build path has "Plugin Dependencies" on the build path.
My version of Eclipse is
Eclipse IDE for Eclipse Committers
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
I'm running on MacOSX High Sierra.
It's probably something very simple.
java eclipse eclipse-plugin
java eclipse eclipse-plugin
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
edited Nov 28 '18 at 16:19
John Tang Boyland
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
asked Nov 21 '18 at 20:02
John Tang BoylandJohn Tang Boyland
45647
45647
1
Maybe the dependencies inMETA-INF/MANIFEST.MFare bound to a very specific version and your target platform is the running platform (so no dependency can be resolved). By the way, also Neon is pretty old. The current version is Eclipse 2018-09.
– howlger
Nov 21 '18 at 22:03
add a comment |
1
Maybe the dependencies inMETA-INF/MANIFEST.MFare bound to a very specific version and your target platform is the running platform (so no dependency can be resolved). By the way, also Neon is pretty old. The current version is Eclipse 2018-09.
– howlger
Nov 21 '18 at 22:03
1
1
Maybe the dependencies in
META-INF/MANIFEST.MF are bound to a very specific version and your target platform is the running platform (so no dependency can be resolved). By the way, also Neon is pretty old. The current version is Eclipse 2018-09.– howlger
Nov 21 '18 at 22:03
Maybe the dependencies in
META-INF/MANIFEST.MF are bound to a very specific version and your target platform is the running platform (so no dependency can be resolved). By the way, also Neon is pretty old. The current version is Eclipse 2018-09.– howlger
Nov 21 '18 at 22:03
add a comment |
1 Answer
1
active
oldest
votes
I have a similar problem every time I upgrade my eclipse installation.
For me the problem can be solved by adjusting the Target platform (can be found in the settings - just search for it) to match the currently running one. For that in most cases I simply add a target platform with default configuration and set that one active.
After a rebuild (normally performed automatically) all those errors are gone.
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419692%2feclipse-neon-for-eclipse-committers-cant-resolve-org-eclipse%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have a similar problem every time I upgrade my eclipse installation.
For me the problem can be solved by adjusting the Target platform (can be found in the settings - just search for it) to match the currently running one. For that in most cases I simply add a target platform with default configuration and set that one active.
After a rebuild (normally performed automatically) all those errors are gone.
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
add a comment |
I have a similar problem every time I upgrade my eclipse installation.
For me the problem can be solved by adjusting the Target platform (can be found in the settings - just search for it) to match the currently running one. For that in most cases I simply add a target platform with default configuration and set that one active.
After a rebuild (normally performed automatically) all those errors are gone.
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
add a comment |
I have a similar problem every time I upgrade my eclipse installation.
For me the problem can be solved by adjusting the Target platform (can be found in the settings - just search for it) to match the currently running one. For that in most cases I simply add a target platform with default configuration and set that one active.
After a rebuild (normally performed automatically) all those errors are gone.
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
I have a similar problem every time I upgrade my eclipse installation.
For me the problem can be solved by adjusting the Target platform (can be found in the settings - just search for it) to match the currently running one. For that in most cases I simply add a target platform with default configuration and set that one active.
After a rebuild (normally performed automatically) all those errors are gone.
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
answered Nov 27 '18 at 15:15
RavenRaven
1,24111023
1,24111023
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
add a comment |
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
Thanks that worked. It's bizarre. I changed it from (old) "Running Platform" to (new) "Running Platform". The only difference is that the original "Running Platform" has a plugin icon whereas the new (working) one has an Eclipse icon.
– John Tang Boyland
Nov 28 '18 at 16:17
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
@John Tang Boyland Yeah that's the same on my system all the time. However the old "Running Platform" usually is broken. Don't know why but recreating it that way fixes it...
– Raven
Nov 28 '18 at 18:04
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419692%2feclipse-neon-for-eclipse-committers-cant-resolve-org-eclipse%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Maybe the dependencies in
META-INF/MANIFEST.MFare bound to a very specific version and your target platform is the running platform (so no dependency can be resolved). By the way, also Neon is pretty old. The current version is Eclipse 2018-09.– howlger
Nov 21 '18 at 22:03