Download JAR files tagged by part with all dependencies

This part of the project contains the core api, xml schemas for each supported xmpp protocol and the jaxb generated code. Because this section rarely changes (i.e. when a new protocol is added or when an existing protocol is updated by the XMPP Standards Foundation its usually not required to actually build from this directory but allow maven to retrieve the pre-built artifacts instead. Doing this will save you a lot of time as there are over 100 modules within this part of the project.

This was the original artifact. It now adds dependencies for all of the other modules so that existing code will still continue to function until they change their dependencies. The modules that are not included in this are: niosax, maven, template test-framework and swing as they were not part of the original jar. To allow time for this migration, this module will remain in the project until 11.1 when it will be removed.

The XJavaDoc engine is a complete rewrite of Sun's JavaDoc engine that is faster and more suited for XDoclet (although it is completely standalone). It scans java source code and makes information about a class available via special java beans that are part of the XJavaDoc core. These beans provide the same information about a class as Sun's JavaDoc API, and some nice extra features.

The XJavaDoc engine is a complete rewrite of Sun's JavaDoc engine that is faster and more suited for XDoclet (although it is completely standalone). It scans java source code and makes information about a class available via special java beans that are part of the XJavaDoc core. These beans provide the same information about a class as Sun's JavaDoc API, and some nice extra features.

Small Java library for generating dynamic proxies on top of [ByteBuddy](https://github.com/raphw/byte-buddy) or [Javassist](https://github.com/jboss-javassist/javassist). You can generate data transfer objects, rich traits or even whole implicit DAO implementations dynamically at runtime easily. This library solves the complex stuff, so you can focus on application logic. Serializability, cloning are already solved by us. We also aim for transparent and easily debuggable proxies, because as we know proxies is usually part of "magic" for the team. Hence, the name of this library - Proxycian as a magician for the proxies ;)

This archetype is creating a full Sling Project composed of a OSGi Bundle and a Content Package which can be deployed to the Sling using specific profiles. It also contains two shadow folders that provide example code / files which are not part of the default build but can be easily copied into the active modules. If the project was created with the **optionAll** property set to **y** (yes) then an **All** package is created with acts as the single deployment unit of all bundles and packages in that project. Otherwise the **ui.apps** package is the deployment unit.