"The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on this page are the version of the Maven Archiver component - not for any specific plugin. To see which version of Maven Archiver a plugin uses, go to the site for that plugin. "
"The WAR Plugin is responsible for collecting all artifact dependencies, classes and resources of the web application and packaging them into a web application archive."
* Enhancements
o New plugins provide enhanced capabilities:
+ Hibernate Plugin:
# allows to generate SQL statements from Hibernate HQL statements
# shows object tree of mapped objec
Atmosphere is a POJO based framework using Inversion of Control (IoC) to bring push/Comet and Websocket to the masses! Finally a framework which can run on any Java based Web Server, including Tomcat, Jetty, GlassFish, Weblogic, Grizzly, JBossWeb and JBoss, Resin, etc. without having to learn how Comet or WebSocket support has been differently implemented by all those Containers. The Atmosphere Framework has both client (JQuery PlugIn) and server components.
Servlet 3.0 is supported along with framework like Jersey (natively), GWT (natively), Wicket, Guice, Spring etc. and programming language like JRuby, Gr oovy and Scala. We also support massive scalability with our Cluster plugin architecture (JGroups, JMS/ActiveMQ, Redis, XMPP,i etc.)
"This page describes how you can get an extended WADL from your REST app. It aligns mostly with the extended-wadl-webapp sample and uses these features:
Add additional doc tags to the WADL
Create JAXB beans from xsd - you might also create the schema from your beans
Add the grammars element that includes the xsd file from which JAXB beans were generated to the WADL
Add javadoc from your resource classes to the WADL, using most of the supported javadoc tags
For getting the extended WADL as described above these things have to be done:
Configure the maven-jaxb-plugin to create JAXB beans from xsd - this is described here just to describe what's done in the sample.
Add the application-doc.xml and application-grammars.xml to the build classpath
Configure the maven-javadoc-plugin with the ResourceDoclet provided by the wadl-resourcedoc-doclet artifact to create the resource-doc.xml.
Create a subclass of WadlGeneratorConfig that defines/configures the WadlGenerators to use
Specify your custom WadlGeneratorConfig in the web.xml as the WadlGeneratorConfig"
Eclipse Integration for Karaf is the integration of the Apache Karaf application platform and the Eclipse IDE.
Notable features include:
An Eclipse Run/Debug launcher configuration that configures Karaf to run inside the workbench transparently to the developer
Automatic deployment of workspace plugin projects to running Karaf instances without copying files
A Target Platform Definition that allows developers to target only the bundles found in Karaf distributions
A Target Platform Provisioner that automatically constructs a target platform from any Karaf distribution on the user's local disk
JMX instrumentation of the Running/Debugging Karaf instance.
Eclipse views that display the Bundle and Service status of Karaf instances
Experimental features:
Web Tools Platform integration including:
Karaf server runtime with associated classpath maintenance
Karaf runtime locator that scans local disks for compatible Karaf distributions
Install from the EIK Update Site
"Seam 3 is collection of modules and developer tools based on the Java EE platform. The modules are portable extensions to CDI that integrate with other technologies to extend the core Java EE functionality. These modules bring you many of the beloved features and integrations from Seam 2 (security, internationalization, JSF, rules, business process management) and also branch out into new areas. IDE support is provided by the JBoss Tools Eclipse plugins.
Before diving in, get up to speed with the status and direction of Seam 3. Also be sure to check out the latest news at the bottom of the page. "
Lucene is an Open Source, mature and high-performance Java search engine. It is highly flexible, and scalable from hundreds to millions of documents.
Luke is a handy development and diagnostic tool, which accesses already existing Lucene indexes and allows you to display and modify their content in several ways:
* browse by document number, or by term
* view documents / copy to clipboard
* retrieve a ranked list of most frequent terms
* execute a search, and browse the results
* analyze search results
* selectively delete documents from the index
* reconstruct the original document fields, edit them and re-insert to the index
* optimize indexes
* and much more...
Recent versions of Luke are also extensible through plugins and scripting.
I started this project because I needed a tool like this. I decided to distribute it under Open Source license to express my gratitude to the Lucene team for creating such a high-quality product. Lucene is one of the landmark proofs that Open Source paradigm can result in high-quality and free products.
"Out of the box Jersey generates basic WADL at runtime that you can obtain from your REST app via GET http://path.to.your/restapp/application.wadl. Additionally you can configure Jersey to create an extended WADL including e.g. additional doc elements or javadoc read from your resource classes: There's a custom doclet that writes your javadoc to a file so that it can be used to extend the WADL. Additionally there's the maven-wadl-plugin that allows you to create the WADL without your running REST app."
The JDT project provides the tool plug-ins that implement a Java IDE supporting the development of any Java application, including Eclipse plug-ins. It adds a Java project nature and Java perspective to the Eclipse Workbench as well as a number of views, editors, wizards, builders, and code merging and refactoring tools. The JDT project allows Eclipse to be a development environment for itself.
* Buckminster is a set of frameworks and tools for automating build, assemble & deploy (BA&D) development processes in complex or distributed component-based development. Buckminster allows development organizations to define fine-grained "production
As Eclipse plug-in and Rich Client Platform developers, we face unique challenges in how we structure and execute our unit tests. In this article, I suggest an approach to unit testing based on Eclipse fragments that can help us overcome these challenges. If you find yourself frustrated with your current plug-in testing options, read on!
But before going into detail on a fragment based solution, let's examine the current approaches and the pros and cons associated with each. The first approach is the one most of us start with as we learn the ropes of plug-in development: placing all code in a single plug-in.