Agree, this could be an issue with windows LFN to 8.3 SFN conversion.
Another issue I found with my observation mentioned below, is the name of
python executable name used in build.xml. On windows Python executable have
same with different versions, python might be having version
specific executable names on other OS.
Python installer for 2.7 and 3.4 version on windows installs python
executable with 'python.exe'.
Since solr expects 3.2 or higher version I installed python 3.4 version.
Not sure what's the executable name on linux.
Ant build.xml expects the name to be python32.exe and for a workaround I
created copies of python.exe with python32.exe & python3.2.exe but still
was getting java.io.IOException: Cannot run program "python3.2". It worked
once I did below changes in build.xml
+<!--
<property name="python32.exe" value="python3.2" />
+-->
+ <property name="python.exe" value="python" />
:
+<!--
<exec executable="${python32.exe}" failonerror="true"
taskname="python32">
+-->
+ <exec executable="${python.exe}" failonerror="true" taskname="python">
:
+<!--
<exec executable="${python32.exe}" failonerror="true"
taskname="smoker">
+-->
+ <exec executable="${python.exe}" failonerror="true" taskname="smoker">
On Sat, Nov 8, 2014 at 8:39 PM, Shawn Heisey <[email protected]> wrote:
> On 11/7/2014 12:19 PM, Anurag Sharma wrote:
> > I am able to proceed proceed further on changing all the instances of
> > 'python3.2' | 'python32.exe' with python and python32.exe
>
> This is a little odd. The only thing I can think of here is that
> something in the stack (Java, ant, or maybe even Windows itself) is
> trying to treat ".2" as the filename extension in a throwback to the 8.3
> days of DOS -- and failing because not only does "python3.2" not exist
> as a full filename, but ".2" is not the extension for an executable.
>
> Windows may have long filenames, but under the covers, it still thinks
> in the old 8.3 filename structure. in a command prompt, go to your home
> directory (C:\Users\username for most recent versions) and type "dir /x"
> to see both the long and short filenames.
>
> One fix would be to use "python3" as the executable name and somehow
> detect that it's at least version 3.2. If the output from "python3
> --version" cannot be parsed easily by ant, perhaps a simple python
> script can be written and included that throws a nonzero exit code if an
> incompatible version is used, which hopefully can abort the build.
>
> I think that might be the easy fix. Whether it's the right fix is
> something I have to ask those who are a lot better at wrangling ant.
>
> Thanks,
> Shawn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
