Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-2543 Updates to jboss-parent 20 (JDK 8). It also makes some build changes removing/renaming some properties.

  1. … 14 more files in changeset.
MODE-2065 Ported the EAP kit to Wildfly 8.0.0.CR1. This exposed a number of issues that had to be addressed: - using Servlet 3.1 compliant containers meant upgrading Cargo & Jetty to 9.x - WebDAV mock tests together with dependencies were removed because they added no value - upgraded to the latest EE BOM which meant changing the Arquillian tests

  1. … 124 more files in changeset.
MODE-1849 - Changed AS7 kit to EAP kit and updated the build system so that new kit and integration tests work against EAP 6.1.Alpha1

  1. … 76 more files in changeset.
MODE-1587 - Updated the modeshape distribution so that it runs on a AS7.2 server and re-enabled the integration tests modules. However, for a local build to work, one needs for the time being a locally installed (via Maven) version of AS7.2.

In the process of updating the kit, a couple of other things were updated:

- exception processing around WritableSessionCache#persistChanges

- logging of exceptions / errors in the ModeShape Webdav Servlet

  1. … 16 more files in changeset.
Updated Arquillian JVM memory setting, increasing the max memory and permGen size. Without those changes, I cannot run locally the integration tests.

MODE-1729 Removed newlines in element values in arquillian.xml

Not sure why the newlines matter, but they're okay on Windows but

break the build on OS X.

MODE-1729 - Updated the configuration files to use Arquillian defined system properties

  1. … 2 more files in changeset.
MODE-872 - Added back into build cycle & fixed tests for web-jcr-rest-client module.

The following were updated

- cargo plugin version and general cargo usage has been refactored: the parent pom defines & configures the default cargo plugin while the child modules only use that configuration

- the cargo plugin & configuration have been updated to work with the latest version of the plugin & Jetty has been upgraded to 7x

- the JcrResources web service, on the @Delete method, does not need the @Consumed annotation

  1. … 21 more files in changeset.
MODE-1500 MODE-1501 Corrected AS7 integration (JNDI names and assemblies)

Several issues were identified and corrected. The first was that although the ModeShape engine

(e.g, the 'org.modeshape.jcr.api.Repositories' implementation) was registered in JNDI,

the Repository instances were not correctly being registered and were thus not able to be found

by deployed components. This was rectified, and now the engine and each repository is properly

registered in JNDI.

Secondly, the JNDI names where the engine and repositories are registered were changed to

more closely align with the naming patterns used by other implementations. The engine

is always registered at "jcr" in the "java:" namespace (i.e, "java:/jcr"), while each

repository is registered at "jcr/{repositoryName}" in the "java:" namespace. For example,

the repository named "sample" could be found in JNDI at "java:/jcr/sample" or "jcr/sample".

This conforms to the many examples that configure a JCR repository at "jcr/local"

(where only one repository is used).

Note that the new default JNDI names are different than ModeShape 2.x, which used "jcr/local" as the

location of the engine and "jcr/local/{repositoryName}" as the default location for each

repository. However, should the old style still be needed for a repository, the repository can

be configured with a custom JNDI name.

Thirdly, when a repository is configured to have a custom JNDI name, the repository is registered

under the specified name (as before), but now the repository is still registered under the

'jcr/{repositoryName}' name. This means that code can find the repository under either name.

Fourthly, the assembly for the ModeShape kit was moved from the 'deploy/jbossas' Maven module

(which installed the resulting ZIP into the Maven repository at 'org/modeshape/jbossas/jbossas-{version}-jbossas-7-dist.zip')

and into the "modeshape-distribution" module, which is where the binary and source distributions

are assembled. And the assembly descriptor was moved to the "modeshape-assembly-descriptors"

module (again, where the other assembly descriptors are managed and installed into the Maven repository).

Fifthly, new integration tests were written to verify that EJBs (of various flavors) can

find the ModeShape repositories correctly using the 4 different ways of looking up a repository:

1) looking up a repository in JNDI

2) looking up the Repositories interface and using it to get a named repository

3) using RepositoryFactory with a single URL (e.g., "jndi:jcr/sample" or "jndi:jcr?repositoryName=sample")

4) using RepositoryFactory with a URL to the engine (e.g, "jndi:jcr") and the name of the repository

These new integration tests are in a new Maven module that downloads AS7 and the ModeShape kit

from the Maven repository and unpacks them into the 'target' directory. When Surefire runs,

this managed server is started, the Arquillian tests are run, and then the server is shutdown.

Each Arquillian test involves creating a WAR file that will be deployed by Arquillian to the

running server, running the unit tests, and then undeploying the WAR file. The tests

can also be run with a different profile so that the tests are deployed and executed in

a separate server installation (as specified by the $JBOSS_HOME variable).

Finally, the older "modeshape-integration-tests" module and the new "modeshape-jbossas-integration-tests"

were relocated to a new top-level folder called 'integration' in the source code. Like the other

top-level directories in our codebase, this is also a Maven module that can be used to run

all of the integration tests. And the '-Pintegration' profile was brought back so that

the distributions are not created and the integration tests not run during the normal builds.

Thus, to run a normal developer build (with all the unit tests but none of the integration tests) simply use

mvn clean install

while the following command will build everything, run all the unit tests, build the AS7 assembly, and run the integration tests:

mvn clean install -Pintegration

As before, running an 'assembly' build (used for releases) will build everything, run all the unit tests,

build the AS7, binary, and source assemblies (including JavaDoc), run the integration tests, and run

the demos:

mvn clean install -Passembly

  1. … 624 more files in changeset.