I'm using RTC and Eclipse Helios. I have a project loaded in my workspace, I can browse it manually just fine, but I can't use the [Ctrl]+[Shift]+T (open type) feature.
I recently deleted a clone project, loaded into another RTC workspace. It might have something to do with that.
So basically, how do I get Eclipse to browse through my project properly?
[EDIT 1]: I am in the java perspective. If i reload my ex-project, I can browse the classes in that one, but not in my new project.
Try right-clicking on your project and clicking Refresh. I occasionally have this problem (nothing is returned in the Type view) and this resolves it for me. I don't use RTC though, so your issue may be different. I don't know what the underlying cause is.
You must be in the Java perspective to access the Ctrl+Shift+T shortcut.
With RTC (IBM Rational Team Concert), your default perspective is "Work Items".
In that perspective, the shortcut for "Open Type" isn't active.
Solution:
switch back to the Java perspective.
display the view (from RTC) "Team Artifacts" and "Pending Changes"
That way, you still benefit from the RTC features while accessing all the usual Java features.
Related
I used Eclipse Java last year for a class, and this year I have another class that's requiring us to use Eclipse C. I tried installing the Eclipse C/C++ packages, but when I write in Eclipse it stays in Java. Please help!!!
Also, I don't really want to uninstall Eclipse if I don't have to, because I'm still actively working on projects.
You've basically downloaded 2 "modes" in Eclipse: Java mode, and C/C++ mode. If you type and it assumes it's Java, that's because the project you created is in "Java mode".
First, just quit out of the app and open it again. Maybe the update only enacts when the app is refreshed.
Now go File > New. If it's installed correctly, when you hover over "New", there should be the option "C/C++ Project". If there isn't, double check that you downloaded the correct extension. (Note that I'm on a Mac so the layout might be slightly different for you, but it's the same idea).
I have many missing libraries in a Java Eclipse (3.7.2) project. Is there any way of copying the list of libraries, to paste into a document for editing?
You can select the errors in the "Problems View" and copy them. Eclipse will put a pure-text version into your clipboard which you can then paste into an Editor.
If you have a working project and want to copy libraries from there, open the (hidden) .classpath file. It's XML which you can copy&paste. I haven't tried copy&paste from the "Build Path" dialog but maybe that works as well.
While Eclipse may recognizes compile-time required dependencies that are missing i hardly doubt it knows runtime-required librarys (so no, eclipse and as faar as i know any other IDE does not support that unless dependency management is set up with for example Maven).
The librarys missed at compile time should show in the 'Problems' view of Eclipse.
Window -> Show View -> "Problems" (select view 'Problems')
Once you have a tab with that view you can order the problems by its description and all of the 'missing library..." issues will be listed in a group. You will then be able to select according entrys and CTRL+C / CTRL+V them out of there.
Also note that in my case using maven eclipse oftenly thinks there are classes or dependencys missing by the fact eclipse is not that skilled when it comes to local synchronization of your workspace.
Id rather invest that time to start adding missing dependencys or think about Maven for more proffessional dependency management.
The "other java proposals" that allows you to use the Ctrl+Space shortcut is missing from my Kempler install. I have redownloaded and reinstalled fresh from Eclipse and still do not have access to the shortcut from "other java proposals".
When searching here it's been suggested it should be checked in the advanced section of the editor preferences for Java. I can't find anything about how to enable to disable it here or in the Eclipse help files so I thought I would ask.
Thanks,
Omega
Kepler doesn't have "Other java proposals" but just Java Proposals.
This option (or Java Proposals (Task-Focused)) is sometimes left unchecked when importing the project to Kepler from a workspace on an older version of eclipse. Hence, your problem might be with workspace than the eclipse dist you are using.
I just thought I would "answer" this question incase someone else had the same problem.
It turns out that Synergy+ uses the same keystroke to lock screens. Even when it's closed, and the service is still running it holds on to key binds.
So, how I fixed it was to go through task manager and kill processes one at a time until I was able to use the shortcut, then went in to Synergy and changed the keybind.
I am used to Eclipse, in that when I save a file, it automatically generates the class file, so that when I run my application the change is already there.
Netbeans seems to be different unfortunately. Everytime I do a little change (and want to see that change), I have to go up to Run-->Clean And Build Project, then find my Java file and select 'Run File'.
Is there any way in Netbeans to speed up this process?
First: you don't need "Clean and build project" each time.
Just use "Run project" (or "Run Main Project") and NetBeans will take care of compiling whatever needs compiling.
But if you do want the "Compile on Save" feature you can enable that in the project's properties under the "Build -> Compiling" options:
For more details on Compile-On-Save see the official FAQ page http://wiki.netbeans.org/FaqCompileOnSave
I would just like to mention in case it helps anyone, that for my "Maven Web Application" project, every time I checked "Compile On Save" and clicked OK, it would not save it. I would reopen the Project Properties to find it unselected. As it turns out the reason was that the nb-configuration.xml for the project was made read-only from source control.
I want to create an Eclipse RCP from our collection of already existing Eclipse plugins.
We have the pecularity that in our RCP we want the user to be able to open ("import") Eclipse projects (we distribute some of our features in bundles which come in the form of Eclipse projects. These should be registered in the workspace because a model server scans for the opened projects and loads them). Also, when I open files via File->open an exception is thrown from our internal editors: File opening intentionally only is possible if you load an imported resource.
For the moment, I have gotten the RCP to work by depending on org.eclipse.core.resources and org.eclipse.ui.navigator.resources. Thereby, I can import complete Eclipse projects. However, I am unsure[1] this is the correct/"intented" way of doing it (e.g. the navigator view is lacking icons per default) should I rather use the CNF?
The main thing is, we have to support loading/importing Eclipse projects in our RCP. Your answer is even helpful if you know other RCPs which allow to import Eclipse projects.
Regards
SuperUser
[1] http://wiki.eclipse.org/RCP_FAQ#Is_the_resources_plug-in_.28org.eclipse.core.resources.29_considered_part_of_the_Rich_Client_Platform.3F
If you are using org.eclipse.ui.navigator.resources then you are using the CNF (it's org.eclipse.ui.navigator).
The link you have is pretty outdated information, using the Eclipse Resources support in an RCP application will work fine (our product does it). And then if you want to package the application to work either as RCP or in an IDE environment you are one step closer. Also, despite what the link you provided says, don't be afraid to use stuff in org.eclipse.ui.ide if you need them. All you really need to be concerned about is to make sure you are only using classes that are actual Eclipse API, if you do that, then everything will work on future Eclipse versions. Anything that's public is Eclipse API unless it's marked in the Javadoc that it's not intended to be used by clients.
You should not be using the Resource Navigator as that has been deprecated and is not as general as the CNF.
As far as importing and exporting Eclipse projects with RCP, our product does that as well and it works fine.
I would say you are on the right track.