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] Issue Comment Edited: (LUCENE-2657) Replace Maven POM templates with full POMs, and change documentation accordingly
Date Fri, 14 Jan 2011 07:57:46 GMT

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

Steven Rowe edited comment on LUCENE-2657 at 1/14/11 2:56 AM:
--------------------------------------------------------------

* Set snapshot {{updatePolicy}} to {{never}} for both the {{apache.snapshots}} and the {{carrot2.org}}
Maven repositories, so that they won't constantly be checked for snapshot updates.
* Consolidated distribution-related profiles to just one named {{dist}}
* Solr-specific noggit and commons-csv jars are now properly placed in {{solr/dist/maven/}}
when deploying with the {{dist}} profile
* No longer setting the repositories' {{uniqueVersion}} to {{false}} when deploying under
the {{dist}} profile; as a result, snapshot artifacts' names will include build timestamps
instead of "{{SNAPSHOT}}" in {{*/dist/maven/}}.
* {{mvn clean}} from {{lucene/src/}} and {{solr/src/}} now removes {{lucene/dist/}} and {{solr/dist/}},
respectively, in addition to the build directories already being removed.

To populate both {{lucene/dist/maven/}} and {{solr/dist/maven/}}, run from the top level:
{code}
mvn -Pdist -DskipTests deploy
{code}

To only populate only {{lucene/dist/maven/}}, run from the top level:
{code}
mvn -N -Pdist deploy
cd lucene
mvn -Pdist -DskipTests deploy
cd ../modules
mvn -Pdist -DskipTests deploy
{code}


      was (Author: steve_rowe):
    * Set snapshot {{updatePolicy}} to {{never}} for both the {{apache.snapshots}} and the
{{carrot2.org}} Maven repositories, so that they won't constantly be checked for snapshot
updates.
* Consolidated distribution-related profiles to just one named {{dist}}
* Solr-specific noggit and commons-csv jars are now properly placed in {{solr/dist/maven/}}
when deploying with the {{dist}} profile
* No longer setting the repositories' {{uniqueVersion}} to {{false}} when deploying under
the {{dist}} profile; as a result, snapshot artifacts' names will include build timestamps
instead of "{{SNAPSHOT}}" in {{*/dist/maven/}}.
* {{mvn clean}} from {{lucene/src/}} and {{solr/src/}} now removes {{lucene/dist/}} and {{solr/dist/}},
respectively, in addition to the build directories already being removing.

To populate both {{lucene/dist/maven/}} and {{solr/dist/maven/}}, run from the top level:
{code}
mvn -Pdist -DskipTests deploy
{code}

To only populate only {{lucene/dist/maven/}}, run from the top level:
{code}
mvn -N -Pdist deploy
cd lucene
mvn -Pdist -DskipTests deploy
cd ../modules
mvn -Pdist -DskipTests deploy
{code}

  
> 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
>
>
> 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