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 generates a schema artifact which contains all of the schemas
from xmpp.org's subversion repository.
Generating this artifact enables a schema to be referenced by jaxb
using the ClassPathCatalogResolver and a catalog file.
To refresh the content of this artifact, either remove the src/main/resources
directory manually or run a clean build from hudson. This is because
maven-scm-plugin is set to checkout only if that directory does not exist
so that the remote subversion repository is not hit every time a build
is performed.
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 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.
The common classes for XMPP and JAXB.
The published schemas from xmpp.org are retrieved and compiled into
an artifact for each protocol.
External projects should depend on the base module + the protocol's
they are interested in. All other dependencies are then retrieved
automatically by maven.
This is the primary module external users should depend on.
It completes the uk.org.retep.xmpp.message package with the various
classes that depend on the JAXB objects, primarily the primary XMPP protocols:
streams, stanzaerror, streamerror, jabber-client, jabber-server,
component-accept and component-connect.
The JAXB handling is also defined in this module.
The common classes for XMPP and JAXB.
The published schemas from xmpp.org are retrieved and compiled into
an artifact for each protocol.
External projects should depend on the base module + the protocol's
they are interested in. All other dependencies are then retrieved
automatically by maven.
JarCasting