[
https://issues.apache.org/jira/browse/LUCENE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914112#action_12914112
]
Steven Rowe commented on LUCENE-2657:
-------------------------------------
{quote}
bq. Full Maven POMs will include the information necessary to run a
multi-module Maven build
That sort of sounds like a parallel build process (i.e. you would be able to
build lucene/solr itself with maven). Is it?
We've avoided that type of thing in the past.
{quote}
Yes, it constitutes a parallel build process, but the Ant build process would
remain the official build. For example, the artifacts produced by the Maven
build will not be exactly the same as those produced by the Ant build process,
and so cannot be used as release artifacts.
It has been noted elsewhere that a Maven build has never been produced for
Lucene. I hope in this issue to provide that, so that the discussion about
whether or not to include it in the source tree has a concrete reference point.
> 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
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.1, 4.0
>
>
> The current Maven POM templates only contain dependency information, the bare
> bones necessary for uploading artifacts to the Maven repository.
> Full Maven POMs will include the information necessary to run a multi-module
> Maven build, in addition to serving the same purpose as the current POM
> templates.
--
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]
