lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
Date Wed, 19 Jan 2011 16:30:44 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983782#action_12983782
] 

Steven Rowe commented on LUCENE-2657:
-------------------------------------

I'm sensitive to the two-build-systems problem. While I like being able to produce local Maven
artifacts, I agree that mixed build systems for new users will be confusing.

I'm okay with putting the POMs themselves under {{dev-tools/}}.  But I want the {{generate-maven-artifacts}}
target to stay in Ant's build, not under {{dev-tools/}}, and a new target {{get-maven-poms}}
added to the top-level {{build.xml}}; {{generate-maven-artifacts}} would depend on {{get-maven-poms}}.
 All {{pom.xml}}'s would be added to {{svn:ignore}} entries where they are placed by {{get-maven-poms}}.

Robert, would you agree to keeping {{generate-maven-artifacts}} and adding {{get-maven-poms}}?

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message