Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Jan 28, 2014

  1. Horia Chiorean

    MODE-2065 Updated the main ModeShape dependencies which overlap with …

    …those from Wildfly.
    Some notable changes include:
    - RestEASY upgraded to 3.0.6 (includes ModeShape code update)
    - Servlet API upgraded to 3.1 (includes ModeShape code update)
    - dependencies replaced with org.wildfly dependencies
    authored January 28, 2014

Sep 10, 2013

  1. Horia Chiorean

    MODE-2028 Updated the EAP kit to 6.1.1.GA

    authored September 10, 2013 rhauch committed September 10, 2013

May 28, 2013

  1. Horia Chiorean

    MODE-1944 Migrated ModeShape EAP kit to EAP 6.1.0.GA. This presented …

    …a number of challenges:
    - RestEASY 2.3.6 excludes explicity a dependency required by resteasy-multipart-provider/apache.james. For this to work, it had to be re-added with the scope "runtime"
    - Deploying exploded webapps does not work anymore (for whatever reason...). This means that our EAP kit had to be changed to provide packaged .war files for the web application. This brought forth several issues around the subsystem and the content of the wars which was fixed.
    authored May 24, 2013 rhauch committed May 28, 2013

May 07, 2013

  1. Horia Chiorean

    MODE-1915 - Updated ModeShape's EAP kit to 6.1.0.Beta

    authored May 01, 2013 rhauch committed May 07, 2013

Mar 14, 2013

  1. Horia Chiorean

    MODE-1849 - Updated kit as per review

    authored March 14, 2013 rhauch committed March 14, 2013

Jul 01, 2011

  1. Randall Hauch

    MODE-1197 Removed JBoss Maven repository settings from our POM

    Having a "repositories" and "pluginRepositories" sections in our parent POM makes it very difficult (if not impossible) to host the ModeShape artifacts in any other repository, including the Maven central repository.
    This change removes those sections from the parent POM and places them in a new "settings.xml" file. This means that developers that don't want to change their "~/.m2/settings.xml" file can simply add the "-s settings.xml" argument to all Maven commands. For details on how to configure Maven, see the wiki page.
    The following procedure was used to test these changes:
    removed the 'repositories' and 'pluginRepositories' sections from our parent POM;
    1. renamed my '~/.m2/settings.xml' file and '~/.m2/repositories' directory so they wouldn't be used;
    2. added to the root of our codebase a 'settings.xml' file that specified the JBoss Maven repository in the 'repositories' and 'pluginRepositories' sections; and
    3. ran 'mvn -Passembly clean install -s settings.xml' to successfully build all artifacts (except JavaDoc and assemblies), downloading everything Maven needed (i.e., the whole internet)
    The build worked fine.
    authored June 15, 2011
Something went wrong with that request. Please try again.