I have just updated from Eclipse Luna to Eclipse Oxygen and installed Andmore. I have a bunch of project workspaces which were created with Eclipse Luna and ADT.
Eclipse automatically upgrades workspaces to the newer version on import, but it doesn’t convert from ADT to Andmore (which, although sharing much of the same code, is a different plugin).
Is there a way I can migrate an existing Eclipse workspace from ADT to Andmore without having to delete and re-import every single Android project?
There is an official way, see here. This needs to be done for each project in the workspace (also for library projects, if any):
Right-click the project, then select Configure > Convert to Andmore Project (wording of the last menu item may differ slightly).
In my case I had to restart Eclipse before it would pick up everything.
You may also need to clean your project.
If you had any tabs with ADT-specific views open (which includes all ADT files and potentially anything which is not a Java source file), you will need to close and reopen them, as they still refer to ADT components which are no longer available. Closing and reopening them will bring up the corresponding Andmore view.
I still get an error message when I try to build the app, but that may be unrelated. The first build failed with an error but that was due to a separate, unrelated issue.
Related
For Eclipse Neon 4.6.1 and PyDev 5.3.1.201610311318 (i.e. everything fully updated as of today).
Is there a way to help PyDev Package Explorer remember the state of expanded directories between sessions?
This problem began only after I upgraded to Neon. Eclipse Mars and PyDev retained folder states between sessions.
My PyDev project contains a nested directories structure. No level is deeper than four levels below the project's root.
I expand one or another portions of that dirs structure as I work. After I close and restart Eclipse, all the project directories and files are present and accessible but the Package Explorer hasn't retained the dirs' expanded state from the previous session.
Sometimes some dirs may be expanded to two of four levels, but sometimes not at all.
Eclipse Neon remembers all other view settings. The size of the Eclipse window, the workspace's tools, and the files that were open in the editor are all where they were at the end of the preceding session.
Not sure it's pertinent, but because Eclipse Neon implements a different projects structure than preceding versions, when I upgraded from Mars to Neon I made a full copy of my Mars project (in case I needed to revert), then pointed Neon to that copy. I then archived my Mars project so that I'm certain I'm not accidentally accessing two different Python projects.
When I created the copy of the project might I have left something behind that affects the PyDev Package Explorer's ability to remember project directory settings between sessions?
I believe I've fixed my own problem.
As mentioned, the problem arose after I upgraded from Eclipse Mars to Eclipse Neon. As part of doing that I tried to re-use my Mars-level projects. When I did, Neon told me it needed to "upgrade" those projects to the newer Neon format. But that process evidently brings a lot of problems along with it.
So I did the following:
I of course had all my Mars projects' source files backed up.
I completely deleted my new Neon installation and reinstalled from scratch: No Mars projects, no inherited settings, no anything else.
In Eclipse Neon, I created new, empty projects (Python, Java, and Java EE).
I copied ONLY my Mars projects' source files -- and nothing else -- into the clean Neon installation's new project directories.
Because the Neon-level projects now contained only source files and nothing else, Neon no longer perceived a need to "upgrade" those projects. Now when I re-open a "Neon-pure" project, that project's folders have retained the expansion levels they had when I closed that project.
Another pleasant by-product of performing the preceding steps was that I also fixed a problem wherein Window -> Show View -> Other displayed a long list of red icons under org.eclipse.e4.secondaryDataStack:
Those red icons no longer appear.
Hope this helps...
The jar was created in eclipse but does not contain source code, only class files. Essentially I am wondering if Eclipse has a built in decompile feature that I can use to restore source code to an earlier version.
If I need to use a 3rd party decompile tool what is recommended?
Going forward, I will be sure to include source files in the .jar
Thanks in advance for any advice.
I am using eclipse
Eclipse Java EE IDE for Web Developers.
Version: Luna Service Release 1 (4.4.1)
Build id: 20140925-1800
There are Java de-compiler plugins available, but keep in mind that you are not going to get your original source code back. The de-compiled source will be equivalent to what was originally compiled, but may not be easy to read, especially if the classes were compiled with symbols removed.
Here is one plugin you can try:
http://jd.benow.ca/
If the versions you want to go back to are very recent (in the last few days) you may be able to use the Eclipse local history. Right click on a file and select 'Compare With > Local History' to see what Eclipse has.
You can configure how much local history Eclipse keeps in the Preferences in General > Workspace > Local History.
Members of my team will be working on a number of plain-text files. Rather than using a normal text editor, I would like them to utilize eclipse, so we can take advantage of the plug-ins that will make life easier... such as the svn plugin.
Therefore, I would like to provide them with an installation of Eclipse where they will set up generic projects, rather than Java projects.
However, the basic Eclipse download from the website includes all the java functionality. This means that their GUI is littered with java-related functions that are not required, and I don't really want them using.
I have attempted to remove the JDT plugins / features from the installation, but at this point the generic project functions disappear too!
How can one go about removing java functionality whilst retaining generic project functionality?
The 'Eclipse Platform' contains the minimal Eclipse without the JDT or PDE Tools.
Go to http://download.eclipse.org/eclipse/downloads/ and choose either Eclipse Kepler 4.3.2 or the release candidate of Eclipse Luna 4.4.RC3 (RC4 later today). Choose the appropriate download from the 'Platform Runtime Binary' section.
Update:
You need to open the Resource perspective to create projects and edit files - use Window > Open Perspective > Other... > Resource. The resource perspective should already be open if you start with a new workspace.
I have used Eclipse Indigo (C/C++) for sometime along with PyDev Plugin (for Python). As I messed up with the IDE (tried to tweak some core files, for fun!), I thought to install a fresh one and this time I downloaded Eclipse Indigo (for Java).
Eclipse (C/C++) was placed in C:/
Eclipse (Java) was even placed in C:/
Now when I opened Eclipse (Java), I observed two things:
The Eclipse's title bar still showing <C/C++ Eclipse>
There was a python's project file still opened up which I worked on Eclipse C/C++ IDE. Also, there was an PyDev's error popped up (mentioning it wasn't installed).
I have verified "Installed Plugins" list and didn't find any plugin related to C/C++ or python.
Now, I have got one question:
As I searched over google and found that Eclipse doesn't store anything beyond its directory, How does this above things are showing up??
There might be some Temp/ Cache files stored. However, I searched my drive with "Eclipse" and "PyDev" as keywords and found nothing.
I even searched for registry keys but couldn't find anything.
What exactly is happening and how do remove Eclipse completely?
TL;DR: using the new Eclipse (Java), select "File > Switch Workspace... > Other...", and create a new directory (e.g. java-wks) for all projects you will do using the new Eclipse.
The long explanantion is that Eclipse stores data in two locations:
The eclipse installation directory itself: contains the plug-ins you install (including the ones already installed in the package you downloaded) and some runtime configuration parameters (see eclipse/config.ini) related to how Eclipse itself should run (e.g. where to find the JRE to execute Eclipse itself, how much memory to allocate etc.)
The workspace(s), where your data (projects and source code) and all personal configuration parameters are stored. This is where Eclipse remembers where your source code is, which file(s) where opened when you last exited, which perspective was active (in your case C/C++ Eclipse), your preferences, launch configurations, breakpoints, etc.
For each Eclipse installation on your system (eclipse folder), you can have as many workspaces as you want (it helps to isolate work). There are various ways to select the workspace location: using the -data <path-to-workspace> option on the command-line, using the popup Eclipse normally shows when starting up (but you may have disabled it), or using "File > Switch Workspace...".
You can also use the same workspace from different Eclipse installations (though not at the same time), but things will not work well if you have different plug-ins installed in each: if one installation stores in the workspace "this is a Python project, and the current perspective is C/++", and the other installation does not have the Python and/or C++ plug-ins installed, it will not known what to do with these info. This is why you see the errors you reported.
For your case, my guess is that under Windows the default workspace location is somewhere in your home directory, and the new (Java) Eclipse is using that, but failing to make sense of the Python and C++ related preferences and projects the previous Eclipse stored there. You need to use a fresh workspace not "polluted" with Python and C++ stuff if you want the Java Eclipse to work without errors (or install the Python and C++ plug-ins in the new Eclipse). You may want to enable the Prompt for workspace on startup preference (in "General > Startup and Shutdown > Workspaces") if it is not to control this easily each time Eclipse starts.
My Eclipse recently broke completely and I have upgraded to Galileo. I have created a fresh workspace (say foo/workspace) and created a trivial project. I have then copied an old project from (bar/workspace/myproject) to foo/workspace/myproject. It is mavenised and has a pom.xml. How do I tell Eclipse to build it (it does not seem to recognise it is mavenised). Do I have to install the maven plugin?
In general what is the smoothest way to reinstall Eclipse (i.e. what else do I need to think about?)
I never create or checkout a project directly under the Workspace but rather use something like ~/Projects for all my projects. This allows me to remain IDE independent. Actually, I never use any IDE to create a project.
I share my workspace location across several Eclipse install (specified at startup or using -data). If anything goes wrong, I don't mind deleting and loosing my workspace, it doesn't contain anything really important anyway.
Use the m2eclipse Eclipse plugin to Import > Maven Projects into Eclipse. Another option is to use the maven eclipse plugin to generate the .project and .classpath from the command line and then to Import > Existing Projects into Workspace from Eclipse.
It is better to reference directly your old workspace when starting your new eclipse installation: see this eclipse.ini
-data
c:/a/path/to/your/old/workspace
That way, you get back all your projects.
You can install the m2eclipse maven plugin by adding its update site to the list of sites examined by the eclipse p2 provisioning mechanism
http://m2eclipse.sonatype.org/update/
If the metadata associated with your workspace is messed up, and it sounds like it is, the easiest thing to do is simply delete the .metadata folder from the workspace (or rename it to something else). Start up Eclipse, it will show an empty workspace, and then use File -> Import to import existing projects back into your workspace. Just point it to the folder of the existing project and it will do the right thing, leaving the project in place.
For the maven stuff, the Import Maven projects mentioned above seems right and probably does some other stuff to have maven work out.