I am working on Eclipse plugin. At the beginning exporting of it worked fine but I guess that after updating Eclipse it broke down. Eclipse started to mentioned that I have uninstalled some equinox packages. It took time till I understood that version of Eclipse made a problems and I reinstalled older version of Eclipse. Now I am again able to run sample environment with plugin but I still am not able to export plugin. In export form where I need to select deployable plugin and/or fragments I don't have listed anything. From what I found I understand that it might be problem with importing project in Eclipse as it might not remove information that project is external and thus not listing as project that could be exported. But I did not find any way to prove this case.
Is there anybody having any idea how to solve this kind of issue?
Related
I'm checking whether we'd be able to migrate from Ant to Gradle, but got confused right at the very beginning of these checks - Apache Netbeans 12 LTS (+ Gradle plugin from official repo) refuses to properly open Gradle projects that were created by a another Netbeans instance, which is a major pain.
I tried to open (in Netbeans) one of the Java library project examples from Gradle docs, only to find out the IDE immediately spews out errors (missing imports for tests) that are unjustified and offers a very limited amount of IDE integration - forget running specific tests, even debugging is all grayed out. Gradle and Netbeans also see different classpaths.
If I create a Gradle project inside Netbeans, everything works fine - no errors, Projects Tree shows an additional tree node, called "Configurations", like in the image below, I'm able to debug and everything just works.
However, even if I just copy/paste this project's directory to a different location, everything breaks after the project is reopened (I also get this issue, same thing happens for example projects found in Gradle docs).
What is going on here? Netbeans seems to know more about a project it created, than about projects that were created outside it or were just relocated. How do I force it to treat all Gradle projects equally (so that they work as expected)?
I used Gradle 7.0.1 and let the New Projects wizard "Initialize the Gradle wrapper" for the project created inside Netbeans 12 LTS. The setting to prefer existing wrappers is enabled in settings if relevant.
Enabling an "experimental" option in Gradle options, called Enable 'lazy' Source Group Initialization does help with simple projects that were created by Netbeans, so they open as expected.
But this does not work for Gradle projects that contain subprojects, such as the example project from Gradle docs:
The issue tracker for this Netbeans plugin has been quite active recently, mentioning issues like this, so perhaps there is hope.
At least part of the problem is that the LTS release of Netbeans (at the time of this writing) doesn't support gradle 7. The latest release, Netbeans 12.4, is the first version that supports gradle 7.
When trying to run the iTrace plugin as an Eclipse application, I get these plugin validation problems.
I've looked at similar questions, but none of them have answered my question.
I've added both the jna jar and commons-logging to the project's build path, but the validation errors persist.
I guess the other thing it could be that the Apache ivyDE not working properly, but even then I thought the com.sun.jna issue should be solved by adding the jar to the build path.
EDIT:
Here are the plugins I have for com.sun.jna and org.apache.commons.logging as well as the run configuration.
EDIT 2: On another machine the plugins validate which is very strange since the installed plugins are very similar.
Here are the corresponding installed plugins for the second machine:
I have no idea why these plugins work, but the others don't. They are using slightly different version of Eclipse though.
I've been dealing with this problems for days now.
I need to install maven and the eclipse plug-in "maven2eclipse" on an offline environment.
So far I've installed maven on the computer but I'm not able to import or open a maven project in eclipse when I right click and select "import source" in the package/project explorer. Maven alternatives simply aren't there for me to use even though I've installed all of the plug-ins that m2e repository has to offer.
I've downloaded the m2e-repository for a local version with these commandlines:
Artifact and metadata (replacing .artifact. with .metadata. and running it again)
"C:\eclipse Java EE\eclipse.exe" -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication \ -source http://download.eclipse.org/technology/m2e/releases \ -destination C:\Maven2Eclipse\repos
I then moved this local folder to the offline system and used it as a local repository.
I've also downloaded the helios repository, but I haven't installed anything from it. Becuase I seemed to be lacking some important dependancies without it. Something with eclipse.UI.. haven't been able to reproduce it.
Anyways, I've added the downloaded repositories to the disposal of my offline environment.
I installed everything with "m2e" and/or "maven" in it's name but I still can't import an "existing maven project". The option simply isn't there.
Here's a screenshot of what m2e software I have installed using the "install new software".
http://i.imgur.com/xPKN6qn.png
Have I missed something? There's something missing and keeping me from actually being able to select the import source "import an existing maven project".
I've been searching the web like crazy and I cannot find anything that resembles my problem.
There's quite a lot on mirroring eclipse repositories and what not but I don't seem to have a problem whit that, unless something didn't get downloaded.
Thanks in advance for any help.
It is better if you can update eclipse with the automatic update by using the url online directly.downloading and then installing the plugin manually causes a lot of issues as some plugins might not get downloaded properly in the installer or some plugins may be completely missing from the installer itself.
Please check the proper url to install the plugin automatically which matches with the version of the eclipse you may be using.
Just...check this two things, if you go in eclipse configuration, inside the Maven tab?
1: Check the Offline mode...
2: Try to use the Maven you've installed (not the embedded one..)
I solved the issue by manually copying all plugins and feature files into their respective folders, making sure everything was installed as well and then restarting eclipse a couple of times with the -clean addition. After that, it started working.. weird :/
Thanks for the answers though!
I am totally new to working with Maven in Eclipse. I am using the latest verion of Eclipse (Kepler). According other posts, as well as Eclipse's help page http://help.eclipse.org/kepler/index.jsp?topic=//org.eclipse.platform.doc.user/tasks/tasks-127.htm , I am supposed to try to install new software within Eclipse IDE.
However, when I try to Add Eclipse's recommended m2e release, Eclipse gives me an error:
Unable to read repository at http://download.eclipse.org/technology/m2e/releases.
download.eclipse[...]releases is not a valid repository location.
Essentially I run into the same problem no matter which approach I take outlined on the Eclipse help page. Is there some other/better way to integrate Maven with Eclipse? Are there steps I should have taken before this? All I have done so far is install Eclipse. How can I successfully get Maven running?
EDIT: Now I am using Java EE and still run into problems when making a Maven project. I get a "Could not resolve archetype error" could this be because I'm behind a proxy?
Most convenient option:
The reason you're getting that error is because that repo is deprecated, and it has been moved. Example of how the new repo looks:
http://download.eclipse.org/technology/m2e/releases/1.0/1.0.0.20110607-2117
Copy that in the Install New Software view, and you will see that it works.
Other options:
Install the Maven Integration from Eclipse Marketplace (Help -> Eclipse Marketplace)
Download the EE version of Kepler (comes with m2e)
Choose your own release (bottom of the page) and use the Install New Software view.
I had the same issue here and the above answer didnt work for me. Although Maven is installed I cane update my dependencies on my folder the way I used to be able to do on Juno. What I did was used the pom.xml from my current project and pasted it into the pom of my new project I created specifically in Eclipse using new project->Maven.
This was eclipse knows its a Maven project and allows my all the benefits of being one.
To install maven properly for eclipse you should set the correct repos as follow:
Help=>install=>
then work with
http://download.eclipse.org/releases/
example of eclipse version : mars or kepler ..
So I tried to get the Maven Gwt archetype up and running. So some background info, I got Maven 3.0, and I have JDK 1.7 in Eclipse.
I ran the archetype, imported the project, and had a bunch of warnings and errors, I solved most of them but this one: GWT SDk servlet.jar was missing in WEB-INF/lib
So I searched stack overflow, and used someones suggestion of using quick-fix to synchronize them. Now I get a warning saying that I have not J2SE1.5 installed.
Do I need J2SE1.5 to run my web app? Why is JDk 1.7 not enough?
Next, I get the warning
Classpath entry com.google.gwt.eclipse.core.GWT_CONTAINER will not be exported or published. Runtime ClassNotFoundExceptions may result.
Which I also have no clue why it is saying that.
But I am able to run the clean install gwt:run Maven goals without any problems.
I could suppress the warnings but my ADD would kill me, I'd rather understand the issues if I am going to just ignore them.
If you have a GWT_CONTAINER entry in your build-path with a Maven project, then you're doing it wrong (gwt-maven-plugin archetype most probably does it wrong, but I don't have the patience to fix all its warts and nobody else seems to bother; maybe we should simply get rid of it).
You should first install the Google Plugin for Eclipse (GPE), which works hand-in-hand with M2Eclipse (M2E) to autoconfigure the project when it detects it's a GWT project (makes use of the gwt-maven-plugin IIRC).
Then make sure you don't have any .project, .classpath or .settings/ files/folders and import your Maven project in Eclipse. M2E and GPE should do everything for you. In the event that GPE doesn't add the GWT nature to your project, go check "Google Web Toolkit" in the project preferences, you'll see that GPE will have automatically selected the gwt-user from your POM as the GWT SDK.
See http://code.google.com/p/google-web-toolkit/wiki/WorkingWithMaven (which suggests avoiding the gwt-maven-plugin archetype).
All in all, it's easier to simply start from scratch: add a dependency on gwt-user and add the gwt-maven-plugin, then do everything else with GPE wizards in Eclipse.
You might also find https://github.com/tbroyer/gwt-maven-archetypes helpful.