EOSGi Eclipse plugin displays OSGi environments specified with eosgi-maven-plugin in the Project Explorer view of Eclipse and lets the user managing the environment by using a context menu.
An Eclipse plugin for running/debugging Java web applications with Jetty (successor of JettyLauncher) Features: - Support for Jetty 7, 8 and 9 (incl. 9.1.x and 9.2.x, 9.3.x, 9.4.x) - Included Jetty...
JBizMo supports building of Angular, Eclipse RCP/RAP, JavaFX, JSF (Primefaces), Swing and Vaadin applications. The generated applications can run in a stand-alone mode or they can be deployed on a ...
m2e-apt aims at providing automatic Annotation Processing configuration in Eclipse, based on your project's pom.xml and its classpath dependencies (Requires Java >= 1.6).
Due to some rogu...
Launch build, execute Java class, run Jetty or Tomcat6 by right-clicking pom.xml (or pom2.xml). Project does not need to be Maven project. Just pom.xml would be enough. (The project may be General,...
M2E Connector for the maven-dependency-plugin The connector is designed to execute the copy,copy-dependencies,unpack and unpack-dependencies goals of the maven-dependency-plugin with m2e.
This m2e connector for WRO4J (https://code.google.com/p/wro4j/) will execute wro4j-maven-plugin:run on Eclipse incremental builds, if a change is detected on css, js, less, json, sass resources und...
COLA Tests m2e connector - No longer required (see details)
JUnit + BDD = COLA Tests
COLA Tests is a BDD framework built on top of JUnit.
It is easy to use, setup and above all, DOES NOT r...
The Android for Maven Eclipse (m2e-android) is an M2E connector that adds Maven support for the Android Developer Tools (ADT) and Andmore Eclipse features. It brings the power of Maven dependency m...
Java Email Library
Product Page | Docs | Demos | API Reference | Examples | Blog | Free Support | Temporary License
Aspose.Email for Java allows developers to focus on implementing their ...
Product Page | Docs | Demos | API Reference | Examples | Blog | Free Support | Temporary License
This Plugin for Eclipse IDE is intended for Java developers who wish to use Aspose.Words for ...
An Eclipse plugin for running/debugging Java web applications with Jetty (successor of JettyLauncher) Features: - Support for Jetty 7, 8 and 9 (incl. 9.1.x and 9.2.x, 9.3.x, 9.4.x) - Included Jetty...
Nodeclipse "Enide Studio 2015" is Tool Suite for Node.js, JavaScript, Java Development. This is the most feature-rich pack. Unless there is the latest version download for your OS, recomm...
Nodeclipse "Enide Studio 2014" is Tool Suite for Node.js, JavaScript, Java Development.
This is the most feature-rich pack. Unless there is the latest version download for your OS,
recommended ...
EOSGi Eclipse plugin displays OSGi environments specified with eosgi-maven-plugin in the Project Explorer view of Eclipse and lets the user managing the environment by using a context menu.
The Groovy Development Tools (GDT) provides Eclipse and Maven (m2e) support for the Apache Groovy programming language. GDT adds full-featured IDE support including editors, wizards, content assist...
Import a .jar or .war as a project into you Eclipse IDE, even if you don't have the source by decompiling the jar
Supported project types
Maven
PDE Eclipse plugin
WAR file
Generi...
JBizMo supports building of Angular, Eclipse RCP/RAP, JavaFX, JSF (Primefaces), Swing and Vaadin applications. The generated applications can run in a stand-alone mode or they can be deployed on a ...
JBoss Tools is an umbrella project for a set of Eclipse plugins that includes support for JBoss and related technologies, such as Hibernate, JBoss AS / WildFly, CDI, OpenShift, Apache Camel, Red Ha...
The JFrog Eclipse Plugin adds JFrog Xray scanning of Maven, Gradle and NPM project dependencies to your Eclipse IDE. It allows developers to view panels displaying vulnerability information ab...
In a nutshell:
This plugin is not a replacement for JDT JUnit view, but more an addition for junit server results. It shows server console output and error stream in own console, can also correl...
Specify eclipse formatting rules and plugin settings only once in your Maven project definition and have everybody on your team use the same settings. No more code formatting conflicts or half back...
