[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983827#action_12983827
]
Steven Rowe edited comment on LUCENE-2657 at 1/19/11 1:32 PM:
--------------------------------------------------------------
A chat on IRC confirms that Robert is okay with my proposal:
# All POMs will be stored under {{dev-tools/maven/}}.
# {{generate-maven-artifacts}} will stay in the Ant build.
# A new {{get-maven-poms}} target will be added to the Ant build to copy the
POMs from {{dev-tools/}} to their target locations: in the top-level directory,
and in each module's subdirectory under {{lucene/}}, {{solr/}}, and
{{modules/}} (trunk only).
# {{svn:ignore}} properties will be changed to include {{pom.xml}} in their
target locations.
# {{generate-maven-artifacts}} will depend on {{get-maven-poms}}.
I'll work up modified patches for trunk and branch_3x along these lines.
was (Author: steve_rowe):
A chat on IRC confirms that Robert is okay with my proposal: adding a new
{{get-maven-poms}} target in the Ant build to copy the POMs from {{dev-tools/}}
to their target locations under {{lucene/}}, {{modules/}} [trunk only] and
{{solr/}}; adding {{svn:ignore}} properties for {{pom.xml}} in their target
locations; keeping {{generate-maven-artifacts}} in the Ant build; and making
{{generate-maven-artifacts}} depend on {{get-maven-poms}}).
I'll work up modified patches for trunk and branch_3x along these lines.
> 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-branch_3x.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,
> 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]
