[
https://issues.apache.org/jira/browse/LUCENE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246359#comment-13246359
]
Steven Rowe commented on LUCENE-3951:
-------------------------------------
Hmm, JIRA lost a comment I made on this issue before resolving (or I screwed up
by editing the issue before submitting a comment I was making) - it was
something like:
I confused releasing and enabling 'the maven build', which involves putting the
POMs in place via {{ant get-maven-poms}} and installing non-mavenized
dependencies into the user's local maven repository via {{mvn -P bootstrap
install}}. The source of the non-mavenized dependencies was the {{lib/}}
directories, which are empty until ivy resolve is done, so ivy resolve is a
prerequisite.
However, since there are no longer any non-mavenized dependencies (see
SOLR-3308, LUCENE-3930, and SOLR-3310 - thanks Robert Muir and Chris Male), ivy
resolve is no longer a prerequisite for running 'the maven build'. I'll
resolve this issue as Invalid.
> get-maven-poms should depend on ivy resolve, so that non-mavenized jars are
> available for use by mvn -P bootstrap install
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3951
> URL: https://issues.apache.org/jira/browse/LUCENE-3951
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.6, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
>
> see title
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
