In an existing Eclipse project, I created a new package (using Eclipse in Linux) and checked it into source control (we use Subversion).
Another user got the new files and can see them in Eclipse on Windows, but not in Linux. The new files are there, just not visible in Eclipse.
I was thinking it might be an Eclipse setting that only lets him see some file types - there are .feature and .java files - but there are pre-existing .java files that he does see in Eclipse.
Any clue what might be causing this?
Related
I am trying to contribute to my first open source project but after forking and cloning from the repo, all files are marked as an error.
Sample error
This is after selecting a source folder.
Current project source
Under package it says: package name does not correspond to filepath
... but I have this
misnamed packages?
Android studio isn't picking up those libraries.
IME there are 2 ways of importing these (I have only had success with the first):
1) copy the source parallel to your own (ie example.com)
2a) include the jar in a libs folder and tell AS to look out for it. (right click will typically provide a good option that I can't recall)
2b) because Android can struggle (ie I couldn't do it, though inroads may have been made since) with importing jars, you may need to use AAR's (android library packages, Android Archive Library (aar) vs standard jar)
However, because this is an open source project, this should all be handled auto-magically for you via the gradle scripts included in the distro.
I'm developing an eclipse plugin and in order to test it I have to install it into my eclipse application regularly. However as I dont't want to change the version of my plugin every time I want to test a new feature I always uninstalled the plugin from within eclipse and afterwards I'd go to the eclipse folder and delete my plugin out of the plugins folder (and delete the respective entries in the eclipse XML-files).
That worked great in windows but I have recently switched to Linux (Mint) and I just found out that my plugin is no longer located in the plugins folder inside the eclipse program directory. Therefore I can't really delete the old plugin whcih then prevents the new version of the plugin from installing properly.
Does anyone have an idea about where eclipse copies the installed plugin or a differerent approch to actually completely uninstall (delete) an installed eclipse plugin?
Okay after searching through my whole filesystem I found it out myself.
Eclipse has a hidden folder in the home directory named .eclipse in which each installed eclipse version has it's sub-directory and in there there is also a plugins and a features folder that then contain the externally installed plugins and features.
It also contains the corresponding artifacts.xml.
I'm not sure whether this behaviour is specific to the Linux Mint OS or rather a new "feature" of Eclipse Neon but if anyone is having the same problem that's were I found it.
Help -> Installation Detail.
Then click the plugin you want removed then press "Uninstall...".
Note: there is a "Plug-ins" tab in the Installation Detail dialog. This is misleading; you are not to click it.
Ps. It might be easier to test the plugin, during development, on a run-time workbench.
I want to use a different installation of the Eclipse IDE, and drop into it some plugins and features that I already downloaded and install on a different instance of Eclipse. How can I do that? AFAIK, it's not as plain as copying the jar files, because Eclipse keeps some meta-data somewhere.
If it matters, the OS is Ubuntu Linux.
The convention is for the meta-data for plugins to be kept in workspace/.metadata/.plugins/ So just copy those to the workspace for the new install. Or just copy the entire workspace if you like.
You can try adding the old eclipse as a repository for install new software. The directory you want is OLD_ECLIPSE/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDKProfile.profile/
If you uncheck "group items by category" you should see the list of features you installed in your OLD_ECLIPSE.
I'm trying to use the Play framework with IntelliJ community edition, which doesn't know what to do with YAML files. It asked me how to open them, and I chose to use the "associated application". But now whenever I double-click on a YAML file in IntelliJ, nothing happens.
The file associations for YAML files are set correctly in my desktop environment, KDE, and opening a YAML file from xdg-open works, but IntelliJ is not using xdg-open.
I suppose this could be related to the fact that I initially installed plain Ubuntu and then switched it to Kubuntu by installing the KDE packages. I'm using Oracle JDK 6.
To edit them as plain text files in IDEA, I can go to Settings (Ctrl+Alt+S), search for File Types and choose "Files opened in associated applications", then remove .yml from the list. Then double-click a YAML file and choose to edit it as a text file. But this is not ideal - I'd like to be able to use associated external applications.
I'm running Eclipse (versions 3.6 and 3.5) on Ubuntu and I'm having trouble installing Eclipse plugins.
There is an easy way to install eclipse plugins in Eclipse, but this doesn't work for me on Ubuntu! This way only works properly under Windows and Mac OSX.
Just like in the tutorial, I create a folder inside my eclipse SDK folder that is named Links.
In this folder, I create a file eclipse-cpp-helios-linux-gtk.lnk or eclipse-cpp-helios-linux-gtk.link that contains this line:
path=/home/taher/opt/eclipse/Third-party-eclipse-links/eclipse-cpp-helios-linux-gtk
and save it, but when I start Eclipse doesn't recognize the plugin!
How can I resolve this problem?
With Eclipse Galileo (3.5) or Helios (3.6), I would rather recommend an external directory called 'mydropins' (for instance), which you can reference from your eclipse.ini, with the option:
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=C:/Prog/Java/eclipse_addons
This is called a shared dropins folder.
See in this SO answer an example of plugin deployment in this shared dropins folder.
(Your link refers to the previous provisioning mechanism, pre-p2.
P2 is the new provisioning system introduced late in Eclipse3.4, refined (debugged?) in eclipse 3.5 and 3.6.
See the supported dropins formats to check how you can organize your own personal dropins folder (that you can reuse between several eclipse installations)
You said you are using:
-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/home/taher/opt/eclipse/Third-party-eclipse-links
That means, under /home/taher/opt/eclipse/Third-party-eclipse-links, you:
won't have any .link file
will copy:
eclipse-cpp-helios-linux-gtk
eclipse
features
plugins
Note: the structure within eclipse-cpp-helios-linux-gtk should be the one describe above, for p2 to pick it up.