[LUCENE-2657] Replace Maven POM templates with full POMs, and change documentation accordingly

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1, 4.0-ALPHA
• Fix Version/s: 3.1, 4.0-ALPHA
• Component/s: general/build
• Lucene Fields: New, Patch Available
• Assignee: Steven Rowe
• Reporter: Steven Rowe
• Created: 20/Sep/10 14:39
• Updated: 28/Aug/22 12:32
• Resolved: 22/Jan/11 07:42

Description

The current Maven POM templates only contain dependency information, the bare bones necessary for uploading artifacts to the Maven repository.

The full Maven POMs in the attached patch include the information necessary to run a multi-module Maven build, in addition to serving the same purpose as the current POM templates.

Several dependencies are not available through public maven repositories. A profile in the top-level POM can be activated to install these dependencies from the various lib/ directories into your local repository. From the top-level directory:

mvn -N -Pbootstrap install

Once these non-Maven dependencies have been installed, to run all Lucene/Solr tests via Maven's surefire plugin, and populate your local repository with all artifacts, from the top level directory, run:

mvn install

When one Lucene/Solr module depends on another, the dependency is declared on the artifact(s) produced by the other module and deposited in your local repository, rather than on the other module's un-jarred compiler output in the build/ directory, so you must run mvn install on the other module before its changes are visible to the module that depends on it.

To create all the artifacts without running tests:

mvn -DskipTests install

I almost always include the clean phase when I do a build, e.g.:

mvn -DskipTests clean install

Issue Links

• incorporates: SOLR-1218 maven artifact for webapp
• relates to: SOLR-1964 Double-check and fix Maven POM dependencies
• relates to: LUCENE-935 Improve maven artifacts
• relates to: LUCENE-622 Provide More of Lucene For Maven