lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] Updated: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
Date Mon, 04 Oct 2010 07:27:33 GMT


Steven Rowe updated LUCENE-2657:

    Attachment: LUCENE-2657.patch

This version of the patch puts the third-party non-mavenized .jar installation stuff into
a profile in the top-level POM.

So instead of running the above-listed script, instead just run the following Maven invocation:
mvn -N -Pbootstrap install

{{-N}} disables recursive building, {{-Pbootstrap}} activates the "bootstrap" profile (defined
in the POM) and the local repo artifact installation stuff is bound to the "install" phase
in the "bootstrap" profile.

I discovered that the Tika artifact snapshots (tika-core and tika-parsers) are hosted at the
Apache snapshots repository, and that was causing these dependencies not to work properly,
so I switched their coordinates to org.apache.solr:solr-tika-*:4.0-SNAPSHOT, so that they
will remain stable.

Also, the previous patch had some weirdness with the Solr DIH Extras POM - it wasn't being
treated as a new file, but rather a diff from some other file (the POM template, I think)
- anyway, this patch fixes the problem.

Everything still compiles, and all tests except the two previously failing tests still pass.

> Replace Maven POM templates with full POMs, and change documentation accordingly
> --------------------------------------------------------------------------------
>                 Key: LUCENE-2657
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 3.1, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-2657.patch, LUCENE-2657.patch
> The current Maven POM templates only contain dependency information, the bare bones necessary
for uploading artifacts to the Maven repository.
> Full Maven POMs will include the information necessary to run a multi-module Maven build,
in addition to serving the same purpose as the current POM templates.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message