settings.xml

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[TEIIDTOOLS-632] Removing subprojects not part of the release and updating poms to support prooduct build (#1696)

  1. … 10 more files in changeset.
MODE-2613: Modeshape persistence test module

  1. … 22 more files in changeset.
MODE-2168 Updated the ModeShape EAP kit to 6.3.0.GA and the integration-platorm-bom to CR10.

  1. … 4 more files in changeset.
MODE-2227 Updated the EAP kit to run against EAP 6.3.0.Beta1. Also, fixed the fact that when running via -DskipTests the integration tests module were attempting to unpack an EAP zip distribution.

  1. … 6 more files in changeset.
MODE-2227 Updated the EAP kit to run against EAP 6.3.0.Beta1. Also, fixed the fact that when running via -DskipTests the integration tests module were attempting to unpack an EAP zip distribution.

  1. … 7 more files in changeset.
MODE-2204 Updated the ModeShape BOMs and the EAP techpreview repository.

  1. … 7 more files in changeset.
MODE-2097, MODE-2169, MODE-2197 Integrated the latest version of the jboss-integration BOM. This commit includes changes for multiple different issues that snowballed: - packaging Javadocs in a zip - updating Apache POI In addition, after integrating the BOM a number of unit tests had to be updated to reflect changes in dependencies both from a functionality perspective and from a deprecation perspective. The most significant change there was the rewriting of the ConnectorTestCase (modeshape-jca) because the new versions of Arquillian + IronJacamar hold filelocks on Windows: https://issues.jboss.org/browse/JBJCA-1027

  1. … 93 more files in changeset.
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) - org.jboss.as dependencies replaced with org.wildfly dependencies

  1. … 42 more files in changeset.
MODE-2028 Updated the EAP kit to 6.1.1.GA

  1. … 9 more files in changeset.
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.

  1. … 20 more files in changeset.
MODE-1915 - Updated ModeShape's EAP kit to 6.1.0.Beta

  1. … 5 more files in changeset.
MODE-1849 - Updated kit as per review

  1. … 2 more files in changeset.
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 http://community.jboss.org/docs/DOC-16545 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.

  1. … 2 more files in changeset.
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 http://community.jboss.org/docs/DOC-16545 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.

  1. … 2 more files in changeset.