[
https://issues.apache.org/jira/browse/LUCENE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242568#comment-13242568
]
Robert Muir commented on LUCENE-3930:
-------------------------------------
I'll work on merging this back. I've tried to setup jenkins to where there will
be no failed builds,
but its the kind of thing where i'll be surprised if I get away without a
failure. If there are problems,
I will fix. If the problems are serious, I will revert.
As far as the plan for 3.x: my idea is we bake in trunk for a while (let
jenkins have its way with the
change, etc). At the same time we can look at how to backport for hopefully
next week.
I might create a branch off of 3.x (the same way as this one worked) so that
its easier for people to help.
But first lets get it in trunk and see how that goes.
> nuke jars from source tree and use ivy
> --------------------------------------
>
> Key: LUCENE-3930
> URL: https://issues.apache.org/jira/browse/LUCENE-3930
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Reporter: Robert Muir
> Assignee: Robert Muir
> Priority: Blocker
> Fix For: 3.6
>
> Attachments: LUCENE-3930-skip-sources-javadoc.patch,
> LUCENE-3930-solr-example.patch, LUCENE-3930-solr-example.patch,
> LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.patch,
> LUCENE-3930__ivy_bootstrap_target.patch, ant_-verbose_clean_test.out.txt,
> noggit-commons-csv.patch, patch-jetty-build.patch
>
>
> As mentioned on the ML thread: "switch jars to ivy mechanism?".
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
