Sure, Steve. Please go ahead. It seems there will be a re-spin to include
SOLR-10735 fix.

I'll also take the opportunity to dig into SOLR-10004 a bit more. Apart
from the unconventional placement of @lucene.experimental tags that I did
there, I want to understand why those descriptions still didn't make it to
the javadocs (and hence continued to print a "missing" warning).

On Sat, May 27, 2017 at 12:24 AM, Steve Rowe <[email protected]> wrote:

> Ishan,
>
> If there is a respin, I’d like to include SOLR-10758 (updates Chinese
> analysis in the Solr ref guide, and includes a Lucene test addition in the
> analysis/icu module).
>
> --
> Steve
> www.lucidworks.com
>
> > On May 26, 2017, at 12:45 PM, Ishan Chattopadhyaya <
> [email protected]> wrote:
> >
> > Not sure if half of Windows users have spaces in their home directory.
> If someone marks SOLR-10735 as a blocker and/or provides a fix, I'll be
> happy to re-spin.
> >
> > On Fri, May 26, 2017 at 9:55 PM, Tomas Fernandez Lobbe <
> [email protected]> wrote:
> > I didn’t try this myself yet (just got a Windows machine to try it), but
> looking at Uwe’s comment here[1], I think this should be a blocker, half
> Windows users won’t be able to run the example.
> >
> >
> > [1] https://issues.apache.org/jira/browse/SOLR-10735?
> focusedCommentId=16026393&page=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16026393
> >
> >> On May 26, 2017, at 8:34 AM, Ishan Chattopadhyaya <
> [email protected]> wrote:
> >>
> >> Uwe, do you think this is a blocker?
> >>
> >> On Fri, May 26, 2017 at 8:43 PM, Uwe Schindler <[email protected]> wrote:
> >> Hi,
> >>
> >>
> >>
> >> on my computer, the Solr one still does not start -see the whitespace
> in directory name (my user name):
> >>
> >>
> >>
> >> C:\Users\Uwe Schindler\Desktop\solr-6.6.0\bin>solr.cmd start -e
> techproducts
> >>
> >> Creating Solr home directory C:\Users\Uwe Schindler\Desktop\solr-6.6.0\
> example\techproducts\solr
> >>
> >>
> >>
> >> Starting up Solr on port 8983 using command:
> >>
> >> C:\Users\Uwe Schindler\Desktop\solr-6.6.0\bin\solr.cmd start -p 8983
> -s "C:\Users\Uwe Schindler\Desktop\solr-6.6.0\example\techproducts\solr"
> >>
> >>
> >>
> >>
> >>
> >> ERROR: Failed to start Solr using command: C:\Users\Uwe
> Schindler\Desktop\solr-6.6.0\bin\solr.cmd start -p 8983 -s "C:\Users\Uwe
> Schindler\Desktop\solr-6.6.0\example\techproducts\solr" Exception :
> org.apache.commons.exec.ExecuteException: Execution failed (Exit value:
> -559038737. Caused by java.io.IOException: Cannot run program
> "C:\Users\Uwe" (in directory "."): CreateProcess error=193, %1 ist keine
> zulässige Win32-Anwendung)
> >>
> >>
> >>
> >>
> >>
> >> C:\Users\Uwe Schindler\Desktop\solr-6.6.0\bin>
> >>
> >>
> >>
> >> I will post this to the issue. Starting Solr without example works, but
> you then have no core to quickly do tests.
> >>
> >>
> >>
> >> FYI, I added a Linux and Windows build of branch_6_6 to Policeman
> Jenkins a minute ago.
> >>
> >>
> >>
> >> Uwe
> >>
> >>
> >>
> >> -----
> >>
> >> Uwe Schindler
> >>
> >> Achterdiek 19, D-28357 Bremen
> >>
> >> http://www.thetaphi.de
> >>
> >> eMail: [email protected]
> >>
> >>
> >>
> >> From: Ishan Chattopadhyaya [mailto:[email protected]]
> >> Sent: Friday, May 26, 2017 9:43 AM
> >> To: [email protected]
> >> Subject: [VOTE] Release Lucene/Solr 6.6.0 RC3
> >>
> >>
> >>
> >> Please vote for release candidate 3 for Lucene/Solr 6.6.0
> >>
> >> The artifacts can be downloaded from:
> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.6.0-RC3-
> revbfb1ee42b2edbc2f2dea49b9d0e3201069d6e781
> >>
> >> You can run the smoke tester directly with this command:
> >>
> >> python3 -u dev-tools/scripts/smokeTestRelease.py \
> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-6.6.0-RC3-
> revbfb1ee42b2edbc2f2dea49b9d0e3201069d6e781
> >>
> >> Here's my +1
> >> SUCCESS! [1:16:00.055493]
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to