[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983161#action_12983161
]
Robert Muir commented on LUCENE-2657:
-------------------------------------
Chris: well thats the problem with maven, it tries to be too many things, a
dependency management tool,
a packaging system, a build system, ...
So, thats why I said we have to just be very clear about which exact scope of
maven we are discussing.
If the patch presented here is against /dev-tools, and is to assist developers
who like maven, then as
I said before I am totally ok with this, but I'm only speaking for myself.
Because maven is so many things, and due to Earwin's confusion, I think it
would be good in general to
add a README.txt to dev-tools anyway, that states what exactly it is (tools to
assist lucene/solr developers,
that aren't supported, its not bugs if they stop working, and will be deleted
if they rot).
Separately what you said about other code in trunk is totally true... for
example its my opinion that there is
a lot of code in lucene's contrib that should be moved out to something like
apache-extras... currently lucene's
contrib has to compile and pass tests or the build fails... there is definitely
some stuff in there that is more
"sandboxy", slows down lucene core development, but itself isnt getting much
maintenance other than devs
doing the minimum work to make them pass tests... and we should be keep other
options in mind for stuff like this.
> 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]
