Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Eclipse Classic vs Eclipse Java
Eclipse Classic vs Eclipse Java [message #858029] Fri, 27 April 2012 01:14 Go to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
Hi guys,

watching www.eclipse.org/downloads/compare.php I have to comment that Eclipse Classic 3.7.2 (174MB) is greater than Eclipse IDE for Java Developer (128 MB) whether Eclipse Classic relate to less packages than Eclipse Java.

Can someone explain the reason? I assume its because of source code packaged in Eclipse Classic but i have not been able to find that code yet. can someone help? Smile

[Updated on: Sat, 28 April 2012 02:47]

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #858212 is a reply to message #858029] Fri, 27 April 2012 03:31 Go to previous messageGo to next message
Satyam Kandula is currently offline Satyam KandulaFriend
Messages: 444
Registered: July 2009
Senior Member
Look at *source* jars in the plugins folder.

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #859354 is a reply to message #858212] Fri, 27 April 2012 15:41 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
Oh ok, thanks and how can i use the code jars?

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #865194 is a reply to message #859354] Mon, 30 April 2012 09:24 Go to previous messageGo to next message
Satyam Kandula is currently offline Satyam KandulaFriend
Messages: 444
Registered: July 2009
Senior Member
If you are doing plugin development, you should be able to look at the Eclipse platform source and step through them while debugging..

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #865317 is a reply to message #865194] Mon, 30 April 2012 10:40 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
Satyam Kandula wrote on Mon, 30 April 2012 05:24
If you are doing plugin development, you should be able to look at the Eclipse platform source and step through them while debugging..

ok great, thank you very much Smile

does the classic eclipse contain sources for all plugins. I miss import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor for example Smile

[Updated on: Mon, 30 April 2012 10:41]

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #867569 is a reply to message #865317] Tue, 01 May 2012 11:10 Go to previous messageGo to next message
Stephan Herrmann is currently offline Stephan HerrmannFriend
Messages: 1853
Registered: July 2009
Senior Member
[quote title=Rudolf Schmidt wrote on Mon, 30 April 2012 12:40]Satyam Kandula wrote on Mon, 30 April 2012 05:24

does the classic eclipse contain sources for all plugins. I miss import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor for example Smile


I can tell for sure for every single plug-in but the JDT sources are complete (incl. the class you mention). Does your project have a dependency on org.eclipse.jdt.ui?

best,
Stephan

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #867826 is a reply to message #867569] Tue, 01 May 2012 13:56 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
[quote title=Stephan Herrmann wrote on Tue, 01 May 2012 07:10]Rudolf Schmidt wrote on Mon, 30 April 2012 12:40
Satyam Kandula wrote on Mon, 30 April 2012 05:24

does the classic eclipse contain sources for all plugins. I miss import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor for example Smile


I can tell for sure for every single plug-in but the JDT sources are complete (incl. the class you mention). Does your project have a dependency on org.eclipse.jdt.ui?

best,
Stephan


yea, you could say it. my project is to fix the bug discribed in http(s)://bugs.eclipse.org/bugs/show_bug.cgi that exists since 2004. its time to fix it Smile

the class containing this bug references to org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor and i cant resolve it.

could you be so kind to help me? I have added all known plugins (from the plugin view) to the java search and checked out the master branch from git://git.eclipse.org/gitroot/jdt/eclipse.jdt.ui.git

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #868032 is a reply to message #867826] Tue, 01 May 2012 15:59 Go to previous messageGo to next message
Stephan Herrmann is currently offline Stephan HerrmannFriend
Messages: 1853
Registered: July 2009
Senior Member
Stephan Herrmann wrote on Tue, 01 May 2012 07:10


I can tell for sure for every single plug-in...


For completeness: I meant to say "I can't ..."

Rudolf Schmidt wrote on Tue, 01 May 2012 15:56

my project is to fix the bug discribed in http(s)://bugs.eclipse.org/bugs/show_bug.cgi that exists since 2004. its time to fix it Smile


Somehow the bug number got lost ...

Rudolf Schmidt wrote on Tue, 01 May 2012 15:56

the class containing this bug references to org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor and i cant resolve it.

could you be so kind to help me? I have added all known plugins (from the plugin view) to the java search and checked out the master branch from git://git.eclipse.org/gitroot/jdt/eclipse.jdt.ui.git


I don't exactly see what you mean by adding plugins to the java search, but the key question is: have you specified the dependency on org.eclipse.jdt.ui in your own Plug-in project (in MANIFEST.MF)? Or are you making changes inside the org.eclipse.jdt.ui project? Where exactly do you see the error?

BTW, when speaking of a failure to resolve RenameFieldProcessor this is not a matter of having source code in Eclipse Classic, even less so if you work from a source project from git.

Stephan

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #868300 is a reply to message #868032] Tue, 01 May 2012 18:50 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
stupid message: "You cannot use links until you have posted more than 25 messages."

so you have to spam until 25 posts to post more spam *g*

I'm really sorry. the resolving problem occurs in the file RenamePrivateFieldTests and not in the file RenameFieldProcessor. its the line number 35: "import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor;" with the error message: "The import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor cannot be resolved"

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #868387 is a reply to message #868300] Tue, 01 May 2012 21:43 Go to previous messageGo to next message
Stephan Herrmann is currently offline Stephan HerrmannFriend
Messages: 1853
Registered: July 2009
Senior Member
Rudolf Schmidt wrote on Tue, 01 May 2012 20:50
the resolving problem occurs in the file RenamePrivateFieldTests and not in the file RenameFieldProcessor. its the line number 35: "import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor;" with the error message: "The import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor cannot be resolved"


So, your org.eclipse.jdt.ui.tests.refactoring project cannot "see" your org.eclipse.jdt.ui. Maybe you need to check the versions in your MANIFEST.MF's. Aren't there any error markers on the manifest?

Stephan

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #868396 is a reply to message #868387] Tue, 01 May 2012 22:11 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
Stephan Herrmann wrote on Tue, 01 May 2012 17:43
Rudolf Schmidt wrote on Tue, 01 May 2012 20:50
the resolving problem occurs in the file RenamePrivateFieldTests and not in the file RenameFieldProcessor. its the line number 35: "import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor;" with the error message: "The import org.eclipse.jdt.internal.corext.refactoring.rename.RenameFieldProcessor cannot be resolved"


So, your org.eclipse.jdt.ui.tests.refactoring project cannot "see" your org.eclipse.jdt.ui. Maybe you need to check the versions in your MANIFEST.MF's. Aren't there any error markers on the manifest?

Stephan


Hey Stephan,

indeed, there are some errors. The MANIFEST.MF containing RenamePrivateFieldTests cants resolve the package "org.eclipse.test.performance"

thats the content of the manifest file:


Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %Plugin.name
Bundle-SymbolicName: org.eclipse.jdt.ui.tests.refactoring; singleton:=true
Bundle-Version: 3.8.0.qualifier
Bundle-ClassPath: refactoringtests.jar
Bundle-Activator: org.eclipse.jdt.ui.tests.refactoring.infra.RefactoringTestPlugin
Bundle-ActivationPolicy: lazy
Bundle-Vendor: %Plugin.providerName
Bundle-Localization: plugin
Export-Package: 
 org.eclipse.jdt.ui.tests.refactoring;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.actions;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.all;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.ccp;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.changes;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.extensions;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.infra;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.nls;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.reorg;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.type;x-internal:=true,
 org.eclipse.jdt.ui.tests.refactoring.typeconstraints;x-internal:=true
Require-Bundle: 
 org.eclipse.core.filebuffers,
 org.eclipse.core.filesystem,
 org.eclipse.core.resources,
 org.eclipse.core.runtime,
 org.eclipse.jdt.core,
 org.eclipse.jdt.core.manipulation,
 org.eclipse.jdt.ui;bundle-version="[3.8.0,4.0.0)",
 org.eclipse.jdt.ui.tests,
 org.eclipse.jface.text,
 org.eclipse.ltk.core.refactoring,
 org.eclipse.ltk.ui.refactoring,
 org.eclipse.team.core,
 org.eclipse.test.performance,
 org.eclipse.ui,
 org.eclipse.ui.ide,
 org.eclipse.ui.workbench.texteditor,
 org.junit;bundle-version="4.8.2"
Bundle-RequiredExecutionEnvironment: J2SE-1.5


and at line 36 "org.eclipse.test.performance" there is a error symbol. hovering over it displays "Bundle 'org.eclipse.test.performance' cannot be resolved"

the manifest from RenameFieldProcessor contains 3 errors.

its content is


Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.eclipse.jdt.ui; singleton:=true
Bundle-Version: 3.8.0.qualifier
Bundle-Activator: org.eclipse.jdt.internal.ui.JavaPlugin
Bundle-ActivationPolicy: lazy
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Export-Package: org.eclipse.jdt.internal.corext;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.corext.buildpath;x-internal:=true,
 org.eclipse.jdt.internal.corext.callhierarchy;x-internal:=true,
 org.eclipse.jdt.internal.corext.codemanipulation;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.corext.codemanipulation.tostringgeneration;x-internal:=true,
 org.eclipse.jdt.internal.corext.dom;x-internal:=true,
 org.eclipse.jdt.internal.corext.dom.fragments;x-internal:=true,
 org.eclipse.jdt.internal.corext.fix;x-internal:=true,
 org.eclipse.jdt.internal.corext.javadoc;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.base;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.binary;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.changes;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.code;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.code.flow;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.delegates;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.generics;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.nls;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.nls.changes;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.participants;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.rename;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.reorg;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.scripting;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.sef;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.structure;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.structure.constraints;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.surround;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.tagging;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.typeconstraints;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.typeconstraints.types;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.typeconstraints.typesets;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.typeconstraints2;x-internal:=true,
 org.eclipse.jdt.internal.corext.refactoring.util;x-internal:=true,
 org.eclipse.jdt.internal.corext.template.java;x-internal:=true,
 org.eclipse.jdt.internal.corext.util;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.ui;x-friends:="org.eclipse.jdt.junit,org.eclipse.jdt.apt.ui",
 org.eclipse.jdt.internal.ui.actions;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.ui.browsing;x-internal:=true,
 org.eclipse.jdt.internal.ui.callhierarchy;x-internal:=true,
 org.eclipse.jdt.internal.ui.commands;x-internal:=true,
 org.eclipse.jdt.internal.ui.compare;x-internal:=true,
 org.eclipse.jdt.internal.ui.dialogs;x-friends:="org.eclipse.jdt.apt.ui",
 org.eclipse.jdt.internal.ui.dnd;x-internal:=true,
 org.eclipse.jdt.internal.ui.filters;x-internal:=true,
 org.eclipse.jdt.internal.ui.fix;x-internal:=true,
 org.eclipse.jdt.internal.ui.infoviews;x-internal:=true,
 org.eclipse.jdt.internal.ui.jarimport;x-internal:=true,
 org.eclipse.jdt.internal.ui.jarpackager;x-internal:=true,
 org.eclipse.jdt.internal.ui.jarpackagerfat;x-internal:=true,
 org.eclipse.jdt.internal.ui.javadocexport;x-internal:=true,
 org.eclipse.jdt.internal.ui.javaeditor;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.ui.javaeditor.breadcrumb;x-internal:=true,
 org.eclipse.jdt.internal.ui.javaeditor.saveparticipant;x-internal:=true,
 org.eclipse.jdt.internal.ui.javaeditor.selectionactions;x-internal:=true,
 org.eclipse.jdt.internal.ui.model;x-internal:=true,
 org.eclipse.jdt.internal.ui.navigator;x-internal:=true,
 org.eclipse.jdt.internal.ui.packageview;x-internal:=true,
 org.eclipse.jdt.internal.ui.preferences;x-friends:="org.eclipse.jdt.apt.ui",
 org.eclipse.jdt.internal.ui.preferences.cleanup;x-internal:=true,
 org.eclipse.jdt.internal.ui.preferences.formatter;x-internal:=true,
 org.eclipse.jdt.internal.ui.propertiesfileeditor;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.actions;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.binary;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.code;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.contentassist;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.ui.refactoring.nls;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.nls.search;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.reorg;x-internal:=true,
 org.eclipse.jdt.internal.ui.refactoring.sef;x-internal:=true,
 org.eclipse.jdt.internal.ui.search;x-internal:=true,
 org.eclipse.jdt.internal.ui.text;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.correction;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.correction.proposals;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.folding;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.java;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.java.hover;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.javadoc;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.spelling;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.spelling.engine;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.template.contentassist;x-internal:=true,
 org.eclipse.jdt.internal.ui.text.template.preferences;x-internal:=true,
 org.eclipse.jdt.internal.ui.typehierarchy;x-internal:=true,
 org.eclipse.jdt.internal.ui.util;x-friends:="org.eclipse.jdt.junit,org.eclipse.jdt.apt.ui",
 org.eclipse.jdt.internal.ui.viewsupport;x-friends:="org.eclipse.jdt.junit",
 org.eclipse.jdt.internal.ui.wizards;x-friends:="org.eclipse.jdt.junit,org.eclipse.jdt.apt.ui",
 org.eclipse.jdt.internal.ui.wizards.buildpaths;x-internal:=true,
 org.eclipse.jdt.internal.ui.wizards.buildpaths.newsourcepage;x-internal:=true,
 org.eclipse.jdt.internal.ui.wizards.dialogfields;x-friends:="org.eclipse.jdt.apt.ui",
 org.eclipse.jdt.internal.ui.workingsets;x-internal:=true,
 org.eclipse.jdt.ui,
 org.eclipse.jdt.ui.actions,
 org.eclipse.jdt.ui.cleanup,
 org.eclipse.jdt.ui.dialogs,
 org.eclipse.jdt.ui.jarpackager,
 org.eclipse.jdt.ui.refactoring,
 org.eclipse.jdt.ui.search,
 org.eclipse.jdt.ui.text,
 org.eclipse.jdt.ui.text.folding,
 org.eclipse.jdt.ui.text.java,
 org.eclipse.jdt.ui.text.java.correction,
 org.eclipse.jdt.ui.text.java.hover,
 org.eclipse.jdt.ui.wizards
Require-Bundle: 
 org.eclipse.help;bundle-version="[3.4.0,4.0.0)",
 org.eclipse.core.expressions;bundle-version="[3.4.100,4.0.0)",
 org.eclipse.core.filesystem;bundle-version="[1.2.0,2.0.0)",
 org.eclipse.core.resources;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.core.variables;bundle-version="[3.2.200,4.0.0)",
 org.eclipse.jdt.core;bundle-version="[3.8.0,4.0.0)",
 org.eclipse.search;bundle-version="[3.7.0,4.0.0)",
 org.eclipse.debug.core;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.debug.ui;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.jdt.launching;bundle-version="[3.6.100,4.0.0)",
 org.eclipse.compare;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.team.ui;bundle-version="[3.4.100,4.0.0)",
 org.eclipse.team.core;bundle-version="[3.4.100,4.0.0)",
 org.eclipse.jface.text;bundle-version="[3.8.0,4.0.0)",
 org.eclipse.ui;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.ui.console;bundle-version="[3.4.0,4.0.0)",
 org.eclipse.ui.workbench.texteditor;bundle-version="[3.8.0,4.0.0)",
 org.eclipse.ui.ide;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.ui.views;bundle-version="[3.3.100,4.0.0)",
 org.eclipse.ui.editors;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.core.runtime;bundle-version="[3.7.0,4.0.0)",
 org.eclipse.ltk.core.refactoring;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.ltk.ui.refactoring;bundle-version="[3.5.0,4.0.0)",
 org.eclipse.ui.forms;bundle-version="[3.4.0,4.0.0)",
 org.eclipse.ui.navigator;bundle-version="[3.3.200,4.0.0)",
 org.eclipse.ui.navigator.resources;bundle-version="[3.4.0,4.0.0)",
 org.eclipse.jdt.core.manipulation;bundle-version="[1.4.0,2.0.0)",
 com.ibm.icu;bundle-version="4.4.2"
Bundle-RequiredExecutionEnvironment: J2SE-1.5
Import-Package: org.eclipse.jdt.core,
 org.eclipse.jdt.core.dom,
 org.eclipse.jdt.core.search,
 org.eclipse.text.edits


the error messages are:

Unsatisfied version constraint: 'org.eclipse.jdt.core: [3.8.0,4.0.0)'
Unsatisfied version constraint: 'org.eclipse.jdt.launching: [3.6.100,4.0.0)'
Unsatisfied version constraint: 'org.eclipse.jface.text: [3.8.0,4.0.0)'
Unsatisfied version constraint: 'org.eclipse.ui.workbench.texteditor: [3.8.0,4.0.0)'

dunno how to solve the problem.

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #868572 is a reply to message #868396] Wed, 02 May 2012 08:38 Go to previous messageGo to next message
Deepak Azad is currently offline Deepak AzadFriend
Messages: 543
Registered: July 2009
Senior Member
As mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=64698
please follow the instructions on
http://wiki.eclipse.org/JDT_UI/How_to_Contribute. Essentially as you
already realized you need more projects in your workspace to satisfy
dependencies on test projects.

--
Deepak Azad
http://wiki.eclipse.org/JDT/FAQ

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #870504 is a reply to message #868572] Tue, 08 May 2012 13:18 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
Ok,

as you can see in bugs.eclipse.org/bugs/show_bug.cgi?id=64698#c12 i checked the projects out.

but i have still the same problem.

no developer answer in the mailing list of jdt

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #870514 is a reply to message #870504] Tue, 08 May 2012 13:52 Go to previous messageGo to next message
Deepak Azad is currently offline Deepak AzadFriend
Messages: 543
Registered: July 2009
Senior Member
On 5/8/2012 6:49 PM, Rudolf Schmidt wrote:
> as you can see in bugs.eclipse.org/bugs/show_bug.cgi?id=64698#c12 i
> checked the projects out.

I assume after 'cloning' the git repositories, you also 'imported' the
projects from these repositories into your workspace?

PS: Such questions are best asked on the newsgroup, I for one do not
feel like answering them on the mailing list as that just adds clutter
to everyone's inbox.

--
Deepak Azad
http://wiki.eclipse.org/JDT/FAQ

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #870551 is a reply to message #870514] Tue, 08 May 2012 16:21 Go to previous messageGo to next message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member
yea of course i imported them in my buildpath.

could you be so kind, to say where the newsgroup relates on jdt issues is located for asking questions to jdk?

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #870613 is a reply to message #870551] Wed, 09 May 2012 02:20 Go to previous messageGo to next message
Deepak Azad is currently offline Deepak AzadFriend
Messages: 543
Registered: July 2009
Senior Member
On 5/8/2012 9:51 PM, Rudolf Schmidt wrote:
> yea of course i imported them in my buildpath.

.... and the original error did not go away? i.e. MANIFEST.MF containing
RenamePrivateFieldTests still cannot resolve the package
"org.eclipse.test.performance"

Do you also have a 1.5 JDK installed ?

> could you be so kind, to say where the newsgroup relates on jdt issues
> is located for asking questions to jdk?
newsgroup and the forum are the same thing, i.e. this place :-)

--
Deepak Azad
http://wiki.eclipse.org/JDT/FAQ

Report message to a moderator

Re: Eclipse Classiv vs Eclipse Java [message #873130 is a reply to message #870613] Thu, 17 May 2012 14:51 Go to previous message
Rudolf Schmidt is currently offline Rudolf SchmidtFriend
Messages: 15
Registered: April 2012
Junior Member

Yea, i do not have jdk 1.5 installed. and yes, RenamePrivateFieldTests can still not resolve org.eclipse.test.performance.

edit:

i found the solution with the help of paulweb515. i had to checkout from R3_maintance7 branche instead of master or something else.

[Updated on: Thu, 17 May 2012 16:52]

Report message to a moderator

Previous Topic:How to figure our an ITypeRoot comes from Java Standard Library?
Next Topic:eclipse project type
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue Apr 23 05:30:52 GMT 2024

Powered by FUDForum. Page generated in 0.04196 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly