[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2657:
--------------------------------
Attachment: LUCENE-2657.patch
In this patch:
# {{ant generate-maven-artifacts}} now works the same as it does on trunk
without this patch -- using {{maven-ant-tasks}} -- except that instead of using
the POM templates, the POMs provided in the patch are used.
# {{ant generate-maven-artifacts}} now functions properly at the top level,
from {{lucene/}}, from {{modules/}}, and from {{solr/}}.
# Removed all {{*-source.jar}} and {{*-javadoc.jar}} generation related
functionality from the POMs, as well as the {{dist}} profile - the Ant build is
responsible for putting together the maven artifacts.
# Removed the POM templates, except for the two required to deploy the
{{solr-noggit}} and {{solr-commons-csv}} artifacts from the Ant build.
# Modified the Maven artifact handling in the Ant build, including artifact
signing, to be correct.
# Based on feedback from Stevo Slavić
<http://www.mail-archive.com/[email protected]/msg45656.html>, added
explicit {{<groupId>}}'s to the POMs that didn't have them, and added explicit
{{<relativePath>}}'s to the {{<parent>}} declarations in all POMs.
I think this patch is ready to be committed to trunk.
I'll post a branch_3x version of this patch tomorrow, and then I think the
patches on this issue will be complete.
> Replace Maven POM templates with full POMs, and change documentation
> accordingly
> --------------------------------------------------------------------------------
>
> Key: LUCENE-2657
> URL: https://issues.apache.org/jira/browse/LUCENE-2657
> 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, LUCENE-2657.patch,
> LUCENE-2657.patch, LUCENE-2657.patch, LUCENE-2657.patch, LUCENE-2657.patch,
> LUCENE-2657.patch, LUCENE-2657.patch, LUCENE-2657.patch, LUCENE-2657.patch,
> LUCENE-2657.patch, 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.
> 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:
> {code}
> mvn -N -Pbootstrap install
> {code}
> 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:
> {code}
> mvn install
> {code}
> 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:
> {code}
> mvn -DskipTests install
> {code}
> I almost always include the {{clean}} phase when I do a build, e.g.:
> {code}
> mvn -DskipTests clean install
> {code}
--
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: [email protected]
For additional commands, e-mail: [email protected]
