Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-2550 Adds OpenDocument Format sequencer

  1. … 25 more files in changeset.
MODE-2551 Adds EPUB 3.0 sequencer

  1. … 16 more files in changeset.
MODE-2549 Adds PDF sequencer

  1. … 21 more files in changeset.
MODE-2552 Adds sequencer for several audio formats

  1. … 22 more files in changeset.
MODE-2553 Adds sequencer for several video formats

  1. … 18 more files in changeset.
MODE-2569 Adds file-persistence to the Wildfly kit This also changes the way the kit integration tests are run so that the actual WF xml configuration files from the kit are used instead of local test-copies.

  1. … 42 more files in changeset.
MODE-2570 Trims the modeshape binary distribution by removing the demos, test and test-source artifacts. It also updates the JavaDoc plugin number and configuration to run with JDK 8.

  1. … 33 more files in changeset.
MODE-2570 Trims the modeshape binary distribution by removing the demos, test and test-source artifacts. It also updates the JavaDoc plugin number and configuration to run with JDK 8.

  1. … 39 more files in changeset.
MODE-2561 Removes the Teiid sequencer from the ModeShape codebase

  1. … 143 more files in changeset.
MODE-2561 Removes the Teiid sequencer from the ModeShape codebase

  1. … 142 more files in changeset.
MODE-2162: Store indexes in ElasticSearch

  1. … 41 more files in changeset.
MODE-2162: Store indexes in Elasticsearch against 4.x branch

  1. … 41 more files in changeset.
MODE-2516 Updates JDK to 1.8 and jboss-parent to the latest version (19) This is the first significant commit of the 5.x series and contains a number of significant changes: - the naming of Maven version properties changed to adopt the standard pattern: 'version.<groupId>.<artifactId>' - build system and dependency updates so that the latest Maven plugin versions function correctly - updating source code to avoid compiler and javadoc warnings

  1. … 154 more files in changeset.
MODE-2159 Adds support for the Lucene index provider to the AS kit

  1. … 12 more files in changeset.
MODE-2383 Fixed the way binary distributions are built so that there is no need to install *-with-dependency artifacts in the Maven repository.

  1. … 24 more files in changeset.
MODE-2383 Added back "examples" to the binary distribution and made sure none of the ZIP assemblies get attached & deployed to Nexus.

  1. … 21 more files in changeset.
MODE-2169 Added an assembly descriptor which zips the Javadocs.

  1. … 3 more files in changeset.
MODE-2146 Split modeshape-jca into modeshape-jca (just the sources) and modeshape-jca-rar (creates RAR assembly).

  1. … 18 more files in changeset.
MODE-2146 Split modeshape-jca into modeshape-jca (just the sources) and modeshape-jca-rar (creates RAR assembly). Fixed additional checkstyle issues.

  1. … 18 more files in changeset.
MODE-1736: Add JCA adaptor directly to binary distribution assembly

  1. … 1 more file in changeset.
MODE-1675 - Changed the build so that modeshape-client.jar is a publishable artifact during the "assembly" profile

  1. … 5 more files in changeset.
MODE-1607 Fixed the JavaDoc generation errors due to 'provided' dependencies

After a lot of trial and error (and hangwringing), the easiest solution is to forcibly include the 'provided'

dependencies with a scope of 'compile' in the "assembly" profile in the "modeshape-distribution/pom.xml" file.

Note that we are (and have been for quite some time) building our JavaDoc in one pass, rather than using

aggregate JavaDocs for each module. The reason is that we only want to build the JavaDoc during assembly

builds, and so the aggregate JavaDoc approach results in the JavaDoc assembly running the entire build as

a fork (to build all of the modules _with_ JavaDoc); this means that a full assembly build would build all

modules at least twice. This would make the builds significantly longer, and the Mead productization build

process is not able to even handle such circular builds.

However, if we build the JavaDoc in one pass, then we simply have to have the modeshape-distribution module

depend on all of the other modules for which we want to build JavaDoc and put into the assemblies (e.g., the

distribution, source, and AS7 kit ZIP files). Normally this works great. But this fails as soon as we have

'provided' dependencies that our code references (since the dependencies will be available in the runtime environment);

see http://jira.codehaus.org/browse/MJAVADOC-340.

The solution that works is simply to include the normally 'provided' dependencies in the dependencies list

for the "assembly" profile.

Note that several other changes were made to the profile's definition to clean up the JavaDoc plugin configuration.

  1. … 1 more file in changeset.
MODE-872 - Updated assembly descriptor & process for modeshape-jdbc

- cleaned up & updated the Ant task which unpacks and processes the dependencies

- added both modeshape-jdbc and modeshape-rest-client to the modules section of the binary distribution

- removed explicit overwrite of maven-ant-plugin from parent pom, as it is defined by jboss-parent

  1. … 5 more files in changeset.
MODE-1389 - Updated directory for client jar

MODE-1389 - Updated assemblies and descriptors

  1. … 38 more files in changeset.
MODE-1386 Updated Maven assemblies, corrected dependencies, and added examples

The Maven assemblies were corrected (a bit; still work to do to create usable distributions),

but several dependencies were removed and two examples were added to the codebase (but not to

the build yet).

  1. … 60 more files in changeset.
MODE-1156 Client JAR is now included in distribution

The client JAR (which is actually the 'modeshape-jdbc-<version>-jar-with-dependencies.jar' file) is now copied into the 'modeshape-distribution/target' directory and renamed to 'modeshape-<version>-client.jar', and is also placed into the 'modeshape-<version>-dist.zip' file. The release script was also changed to copy the information into the archive directory.

  1. … 4 more files in changeset.
MODE-1104 Changed build to work in a single pass

Prior to this change, someone running a ModeShape build for the first time had to run two separate commands:

'mvn -Pintegration install' and 'mvn -Passembly install'. It also used aggregator goals for JavaDoc and

assemblies, which fork a new build process for each invocation and which can result in a build that does

double work (if they're included in the main build process). Plus, because the JavaDoc and assembly usages

were in the parent POM, the JavaDoc and assemblies were produced before the modules were compiled; on a machine

in which 'mvn install' was not yet run, this caused an error.

Now, the assembly operation is defined in a child module called 'modeshape-distribution' and the assembly

descriptors are referenced as being on the classpath since they're now defined in a new

'modeshape-assembly-descriptors' module. The end result is that, on a fresh machine on which ModeShape

has not yet been built, the source for ModeShape can be downloaded and completely built using a single

command: 'mvn -Passembly install'.

This commit moves quite a few files around and restructures a number of the POM files, but does not affect

any of the Java source code.

    • -0
    • +118
    ./binary-distribution.xml
  1. … 63 more files in changeset.