Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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. … 62 more files in changeset.
MODE-1778 - Updated Tika to 1.3 and the AS7 modules schema to 1.2

  1. … 10 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. … 14 more files in changeset.
MODE-1764 - Updated the AS7 kit that will be provided as part of 3.2 - the former 7.1.1.kit has been removed (together will assemblies) because ISPN 5.2 is not compatible with AS7.1.1 - removed the modeshape-integration-tests folder as that was ported from 2.x and either the corresponding tests have been ported in various other places in 3.x or they no do apply anymore (connectors) - changed our AS7 distribution kit to as72 - since integration with AS7.2.0 is still WIP, the integration modules have been commented out

    • -30
    • +0
    ./modules/org/apache/lucene/3.5/module.xml
    • -62
    • +0
    ./modules/org/apache/tika/1.2/module.xml
    • -36
    • +0
    ./modules/org/modeshape/common/main/module.xml
    • -34
    • +0
    ./modules/org/modeshape/jcr/api/main/module.xml
    • -34
    • +0
    ./modules/org/modeshape/jdbc/main/module.xml
  1. … 379 more files in changeset.
MODE-1765 - Updated the AS7 distributions so that there's a dedicated one for integration-testing (which overrides the default one). The default AS7 distribution has been "cleaned up" and is now testing only during the "assembly" phase via a separate Maven module.

    • -49
    • +0
    ./modules/org/modeshape/main/res/custom.cnd
  1. … 17 more files in changeset.
MODE-1765 - Updated the AS7 distributions so that there's a dedicated one for integration-testing (which overrides the default one). The default AS7 distribution has been "cleaned up" and is now testing only during the "assembly" phase via a separate Maven module.

    • -49
    • +0
    ./modules/org/modeshape/main/res/custom.cnd
  1. … 17 more files in changeset.
MODE-295 More fixes to the build and made artifact names more consistent/appropriate

    • -0
    • +0
    ./standalone/deployments/modeshape-cmis.war.dodeploy
  1. … 64 more files in changeset.
MODE-1741 - Updated the Git connector so that indexable branches are configurable

  1. … 7 more files in changeset.
MODE-1729 - Updated the configuration files to use Arquillian defined system properties

  1. … 2 more files in changeset.
MODE-1729 - Added integration test for the Git Connector

  1. … 4 more files in changeset.
MODE-1286 Added Git connector module for AS7

Added the files that produce the AS7 module for the Git connector

and include this module in the ModeShape AS7 assemblies.

Note that this connector module (and other connectors) will need to be

referenced in the configuration of the connector, in the same way that

the sequencer configurations have to specify the sequencer module.

This also adds the "git" and "gitconnector" aliases to the

RepositoryConfiguration class.

    • -0
    • +34
    ./modules/org/modeshape/connector/git/main/module.xml
  1. … 6 more files in changeset.
MODE-1729 - Added AS7 integration test and updated configuration to use an external filesystem source.

  1. … 3 more files in changeset.
MODE-1720 Refactored ExecutionContext and its contained objects

ExecutionContext contains quite a few objects that represent the

context-specific factories, namespace registries, binary stores, etc.

The nature of these components made it difficult to created altered

contexts with customized value factories, security contexts, binary

stores, etc.

ExecutionContext was refactored to own all of the value factory

implementations, and all of the factories were changed to take

"holder"-type objects that the factories use to get the components

they want. These two steps make it far easier for ExecutionContext

to create alterations.

These changes are simple refactorings of existing behavior, and as

such made it easier to verify that the functionality remainined

unchanged. This commit will then serve as a baseline for other

changes specific to MODE-1720.

  1. … 44 more files in changeset.
MODE-1684 - Removed the file-store persistence from the workspace cache

  1. … 1 more file in changeset.
MODE-1684 - Updated the configuration file for the AS7.2 kit as well

MODE-1609 - Updated cache-index-storage to use cache-container name, not the JNDI name.

  1. … 14 more files in changeset.
MODE-1609 - Fixed AS7 subsystem binary storage integration plus some issues which surfaced: * a bug inside ChunkInputStream * wrongful logging by the sequencers

  1. … 15 more files in changeset.
MODE-1609 - Fixed remaining custom indexes and configuration issues

    • -1
    • +1
    ./modules/org/modeshape/main/module.xml
  1. … 3 more files in changeset.
MODE-1598 - Updated AS7 subsystem to support custom node-types registration

    • -0
    • +49
    ./modules/org/modeshape/main/res/custom.cnd
  1. … 15 more files in changeset.
MODE-1665 Corrected AS7.2 kit to deal with missing methods

Correcting this class led to several other problems, primarily with the logging system. In particular,

we were no longer able to see the correct logging implementations and load the SLF4J logger, probably

(big assumption here) because AS7.2 was changed to no longer leak the logging interfaces and

implementations and thereby exposing some incorrect dependencies in ModeShape modules.

Plus, our LoggerFactory class was attempting to discover the logger classes (for the various frameworks)

using the thread context classloader (TCCL) and then the system classloader – but not the current

classloader. This seems obviously incorrect, so this was changed to simply try to load the class

with the current classloader. The same thing was done for JaasProvider, which was the only other

class using the ClassUtil.loadClassStrict(...) method.

After all these changes, full builds running the following commands pass:

* mvn clean install -Pintegration

* mvn clean install -Pintegration,as72

    • -1
    • +0
    ./modules/org/modeshape/main/module.xml
  1. … 9 more files in changeset.
MODE-1563 - Integrated the initial content feature with the AS7 subsystem, including an integration test

    • -0
    • +1
    ./modules/org/modeshape/main/module.xml
    • -0
    • +11
    ./modules/org/modeshape/main/res/initial-content-custom.xml
    • -0
    • +4
    ./modules/org/modeshape/main/res/initial-content-default.xml
  1. … 16 more files in changeset.
MODE-1639, MODE-1640, MODE-1634 Replaced the Aperture-based MIME type detector with a Tika-based one

This required quite a bit of dependency gymnastics, since Tika has quite a few more transitive

dependencies than the Aperture library (which we had successfully pared down several years ago).

Tika references about 25 dependencies (including transitive dependencies), but this was reduced

in 'modeshape-jcr' to about 8 for basic MIME type detection. Note that Tika usually includes

two BouncyCastle libraries in its dependencies (used for encrypted PDFs, among other things),

but ModeShape intentionally excludes these (as we don't want to ship or depend on any

security-related JARs).

Not only do we get Tika's substantial MIME type database, we've made it possible for users

to edit the 'org/modeshape/custom-mimetypes.xml' file and provide the updated one on the application

classpath. What goes in that file will overwrite all of the other sources (namely Tika's built-in

file and its customization file, both of which are to be found on the classpath), which means

it's easiest to simply provide an updated version of this file at 'org/modeshape/custom-mimetypes.xml'.

Be sure to not remove any of the (few) customizations that ModeShape includes - those are important.

As we upgrade Tika, we'll get updated versions of the media type data. This is far more preferable

than having a ModeShape-specific version.

The MIME type related interfaces in ModeShape's public API (e.g., 'modeshape-jcr-api') have been removed.

These were added sometime in one of the 3.0 releases, so removing them will not introduce compatibility

issues for users.

Instead, we've decided to get out of the MIME type detection framework business, and have decided

to switch to Tika for all MIME type detection. In fact, you can still write your own MIME type detector,

but you do that by implementing Tika's interface and reference the implementation class(es) in the

corresponding service loader file in your JAR. (See the TIKA documentation for details.)

However, internally we still have an abstraction. This is because it is possible to remove the Tika

(and transitive dependencies) from a ModeShape installation, as long as your applications will not

expect any kind of automatic MIME type detection. This is a perfectly valid use case: for example,

using a repository to store data and do not store files (and don't use sequencers).

The AS7 kits required a bit more modification. There is now a new AS7 module for 'org.apache.tika'

that contains all of the JARs, and this is used by the ModeShape module and by the Tika text extractor

module.

All unit and integration tests pass with these changes. Several new tests were added.

    • -0
    • +62
    ./modules/org/apache/tika/1.2/module.xml
    • -1
    • +2
    ./modules/org/modeshape/main/module.xml
  1. … 68 more files in changeset.
MODE-1338 Added Teiid Sequencer to JBoss AS kit and distributions

  1. … 103 more files in changeset.
MODE-1605 Added a kit for AS7.2

The existing resources used in the kit for AS7.1 were changed slightly so that we can have another set of

resources for an AS7.2 kit. The "modeshape-distribution" module now always builds both 7.1 and 7.2 kits,

although by default it only tests the kit for 7.1. To test with 7.2 (which is currently only in Alpha1-SNAPSHOT),

use the "-Pas72" profile.

Verified that all normal builds (no profile, or with the "integration" or "assembly" profiles) pass successfully,

and that they also pass when adding the "as72" profile to these builds.

    • -0
    • +0
    ./modules/org/apache/lucene/3.5/module.xml
    • -0
    • +0
    ./modules/org/modeshape/jdbc/main/module.xml
    • -0
    • +1
    ./modules/org/modeshape/main/module.xml
  1. … 68 more files in changeset.