Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
Hi, On 01.08.2013 15:15, Oliver-Rainer Wittmann wrote: Hi, Our current documentation about building AOO on Windows [1] (legacy one [2]) references JDK 1.6 and Visual Studio 2008 Express as needed software tools in order to build AOO on Windows. You might know that these are no longer officially available for Windows. Thus, I decided to work on a Windows build environment _without_ Visual Studio 2008 and _with_ JDK 1.7. I managed to build current trunk on a Windows 7 64bit HomePremium system using Java 7 (JDK 1.7) and without an installed Visual Studio instance. The problems which I need to solve on my way to the installation set were: (1) New version 2.7.1-1 of cygwin tool 'patch'. Version 2.7.1-1 now takes line endings in the patch file and in the file to be patch serious. Thus, the application of a patch fails when the line endings are different. Solution is to tweak the calling of the cygwin tool 'patch'. (2) Building module accessibility. In accessibility/bridge/source/java/ 'javah' is used to create a C header file from a Java class. This does not work with JDK 1.7 as the classpath does not contain the needed references to our UNO-API Java classes. Solution is to adjust the classpath for this 'javah' call. There are issues 121690 [3] and 121754 [4] regarding building with Java 7 (JDK 1.7) and HSQLDB. I think these issues are the duplicates of each other [please, can one of the people involved in these issues - e.g. Fred, Ariel or Andrea confirm this? Thx in advance]. As far as I understood these issues are solved. Please correct me, if I am wrong. My build was not hit by any build problem regarding modules hsqldb and connectivity. The installation of my build successfully passes the so-called smoketest - open document /main/smoketestdoc/[platform]/bin/smoketestdoc.sxw and hit start button. On a Windows system with JRE 6 the installation of my build does not recognize installed JRE 6 as an Java runtime environment (Menu - Tools - Option - Java). This is no problem from my point of view as our Windows users should not have JRE 6 installed anymore on their systems due to its security risks. Does somebody contradicts? I will soon update our documentation [1] in order to enable newcomers to build AOO under Windows. I will also update the reference to the Windows SDK, because for building without stlport on Windows the SP1 of the corresponding Windows SDK is needed - see issue 122500 [5]. I have already updated our documentation regarding building AOO under Windows - just forgot to mentioned it here. Feedback regarding the documentation and its application in practice is much appreciated - Thx in advance. Best regards, Oliver. [1] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows [2] http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows [3] https://issues.apache.org/ooo/show_bug.cgi?id=121690 [4] https://issues.apache.org/ooo/show_bug.cgi?id=121754 [5] https://issues.apache.org/ooo/show_bug.cgi?id=122500 Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
Hi, On 07.08.2013 08:59, Regina Henschel wrote: Hi Oliver, You have edited the old OOo3 version. There is the new version on http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step I have edited the AOO Windows build requirement wiki page [1] and the AOO Windows step-by-step guide [2] which are both referenced by our new AOO Building Guide [3]. I did not touch the legacy one [4] which is the one from OOo 3.x with the one or the other edit for AOO. I will mark it as 'historical' and give a link to the new building guide. I would like to clean up these wiki pages - more or less removing the legacy ones -, but I am currently not sure, if we would lose the one or the other important information, esp. for the Linux and the MacOS platform. [1] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows [2] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step [3] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO [4] http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows Best regards, Oliver. Kind regards Regina Oliver-Rainer Wittmann schrieb: Hi, On 01.08.2013 15:15, Oliver-Rainer Wittmann wrote: Hi, Our current documentation about building AOO on Windows [1] (legacy one [2]) references JDK 1.6 and Visual Studio 2008 Express as needed software tools in order to build AOO on Windows. You might know that these are no longer officially available for Windows. Thus, I decided to work on a Windows build environment _without_ Visual Studio 2008 and _with_ JDK 1.7. I managed to build current trunk on a Windows 7 64bit HomePremium system using Java 7 (JDK 1.7) and without an installed Visual Studio instance. The problems which I need to solve on my way to the installation set were: (1) New version 2.7.1-1 of cygwin tool 'patch'. Version 2.7.1-1 now takes line endings in the patch file and in the file to be patch serious. Thus, the application of a patch fails when the line endings are different. Solution is to tweak the calling of the cygwin tool 'patch'. (2) Building module accessibility. In accessibility/bridge/source/java/ 'javah' is used to create a C header file from a Java class. This does not work with JDK 1.7 as the classpath does not contain the needed references to our UNO-API Java classes. Solution is to adjust the classpath for this 'javah' call. There are issues 121690 [3] and 121754 [4] regarding building with Java 7 (JDK 1.7) and HSQLDB. I think these issues are the duplicates of each other [please, can one of the people involved in these issues - e.g. Fred, Ariel or Andrea confirm this? Thx in advance]. As far as I understood these issues are solved. Please correct me, if I am wrong. My build was not hit by any build problem regarding modules hsqldb and connectivity. The installation of my build successfully passes the so-called smoketest - open document /main/smoketestdoc/[platform]/bin/smoketestdoc.sxw and hit start button. On a Windows system with JRE 6 the installation of my build does not recognize installed JRE 6 as an Java runtime environment (Menu - Tools - Option - Java). This is no problem from my point of view as our Windows users should not have JRE 6 installed anymore on their systems due to its security risks. Does somebody contradicts? I will soon update our documentation [1] in order to enable newcomers to build AOO under Windows. I will also update the reference to the Windows SDK, because for building without stlport on Windows the SP1 of the corresponding Windows SDK is needed - see issue 122500 [5]. I have already updated our documentation regarding building AOO under Windows - just forgot to mentioned it here. Feedback regarding the documentation and its application in practice is much appreciated - Thx in advance. Best regards, Oliver. [1] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows [2] http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows [3] https://issues.apache.org/ooo/show_bug.cgi?id=121690 [4] https://issues.apache.org/ooo/show_bug.cgi?id=121754 [5] https://issues.apache.org/ooo/show_bug.cgi?id=122500 Best regards, Oliver. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
Hi Oliver, Oliver-Rainer Wittmann schrieb: Hi, On 07.08.2013 08:59, Regina Henschel wrote: Hi Oliver, You have edited the old OOo3 version. There is the new version on http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step I have edited the AOO Windows build requirement wiki page [1] and the AOO Windows step-by-step guide [2] which are both referenced by our new AOO Building Guide [3]. OK, I have overseen, that you edit [2] too. It is very confusing to have both. I would like to see only one page per OS, containing OS specific informations and details. I did not touch the legacy one [4] which is the one from OOo 3.x with the one or the other edit for AOO. I will mark it as 'historical' and give a link to the new building guide. +1 or 'legacy' or 'archive'. And very large ;) I would like to clean up these wiki pages - more or less removing the legacy ones -, but I am currently not sure, if we would lose the one or the other important information, esp. for the Linux and the MacOS platform. Keep the old ones but add an header to which versions they belong. I remember, that someone on the list insists on building OOo3.4.1. [1] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows [2] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step [3] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO [4] http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows Best regards, Oliver. I'm pleased, that you care about the instructions. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 8/7/13 10:01 AM, Regina Henschel wrote: Hi Oliver, Oliver-Rainer Wittmann schrieb: Hi, On 07.08.2013 08:59, Regina Henschel wrote: Hi Oliver, You have edited the old OOo3 version. There is the new version on http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step I have edited the AOO Windows build requirement wiki page [1] and the AOO Windows step-by-step guide [2] which are both referenced by our new AOO Building Guide [3]. OK, I have overseen, that you edit [2] too. It is very confusing to have both. I would like to see only one page per OS, containing OS specific informations and details. I did not touch the legacy one [4] which is the one from OOo 3.x with the one or the other edit for AOO. I will mark it as 'historical' and give a link to the new building guide. +1 or 'legacy' or 'archive'. And very large ;) I would like to clean up these wiki pages - more or less removing the legacy ones -, but I am currently not sure, if we would lose the one or the other important information, esp. for the Linux and the MacOS platform. Keep the old ones but add an header to which versions they belong. I remember, that someone on the list insists on building OOo3.4.1. I would prefer to drop[ everything that is old and that is more confusing than it helps Juergen [1] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows [2] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step [3] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO [4] http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows Best regards, Oliver. I'm pleased, that you care about the instructions. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 7 August 2013 11:31, Jürgen Schmidt jogischm...@gmail.com wrote: On 8/7/13 10:01 AM, Regina Henschel wrote: Hi Oliver, Oliver-Rainer Wittmann schrieb: Hi, On 07.08.2013 08:59, Regina Henschel wrote: Hi Oliver, You have edited the old OOo3 version. There is the new version on http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step I have edited the AOO Windows build requirement wiki page [1] and the AOO Windows step-by-step guide [2] which are both referenced by our new AOO Building Guide [3]. OK, I have overseen, that you edit [2] too. It is very confusing to have both. I would like to see only one page per OS, containing OS specific informations and details. I did not touch the legacy one [4] which is the one from OOo 3.x with the one or the other edit for AOO. I will mark it as 'historical' and give a link to the new building guide. +1 or 'legacy' or 'archive'. And very large ;) I would like to clean up these wiki pages - more or less removing the legacy ones -, but I am currently not sure, if we would lose the one or the other important information, esp. for the Linux and the MacOS platform. Keep the old ones but add an header to which versions they belong. I remember, that someone on the list insists on building OOo3.4.1. I would prefer to drop[ everything that is old and that is more confusing than it helps +1 rgds jan I Juergen [1] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows [2] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step [3] http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO [4] http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows Best regards, Oliver. I'm pleased, that you care about the instructions. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 7 August 2013 09:33, Rory O'Farrell ofarr...@iol.ie wrote: I'm deleting the quotes of the earlier discussion as it is not relevant to my point here. I have no experience of building with Java and care little about the security holes, so I bow to the expertise of those who know better. If changes are being made to the OpenOffice/Java interaction, would it be possible that these be done in such a way that no matter whether installed on a 32 or 64 bit windows, OpenOffice interfaced correctly with the installed Java, so doing away with the requirement that a 32 bit Java be installed. +1 AOO should work with what is installed, [though there is probably no need to support Java 4 or earlier any more.] Just because Java 5 or 6 is no longer current does not mean it is not being used. In particular, businesses tend to stay on older versions of Java (and OS) until the cost of updating is less than the cost of not updating. This would prevent many queries on the Forum of why OO doesn't work with an installed Java. -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 7 August 2013 12:51, sebb seb...@gmail.com wrote: On 7 August 2013 09:33, Rory O'Farrell ofarr...@iol.ie wrote: I'm deleting the quotes of the earlier discussion as it is not relevant to my point here. I have no experience of building with Java and care little about the security holes, so I bow to the expertise of those who know better. If changes are being made to the OpenOffice/Java interaction, would it be possible that these be done in such a way that no matter whether installed on a 32 or 64 bit windows, OpenOffice interfaced correctly with the installed Java, so doing away with the requirement that a 32 bit Java be installed. +1 +1 AOO should work with what is installed, [though there is probably no need to support Java 4 or earlier any more.] Just because Java 5 or 6 is no longer current does not mean it is not being used. In particular, businesses tend to stay on older versions of Java (and OS) until the cost of updating is less than the cost of not updating. correct, but at the same time companies are typically security aware, and java 6 (and below) have some serious know issues. I would have thought that its possible to develop/built with java 7 and still have java 5,6 as runtime environment, but looking at the code it does not seem easy (we would have to get the java version, and use different API calls). rgds jan I. This would prevent many queries on the Forum of why OO doesn't work with an installed Java. -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 7 August 2013 11:55, janI j...@apache.org wrote: On 7 August 2013 12:51, sebb seb...@gmail.com wrote: On 7 August 2013 09:33, Rory O'Farrell ofarr...@iol.ie wrote: I'm deleting the quotes of the earlier discussion as it is not relevant to my point here. I have no experience of building with Java and care little about the security holes, so I bow to the expertise of those who know better. If changes are being made to the OpenOffice/Java interaction, would it be possible that these be done in such a way that no matter whether installed on a 32 or 64 bit windows, OpenOffice interfaced correctly with the installed Java, so doing away with the requirement that a 32 bit Java be installed. +1 +1 AOO should work with what is installed, [though there is probably no need to support Java 4 or earlier any more.] Just because Java 5 or 6 is no longer current does not mean it is not being used. In particular, businesses tend to stay on older versions of Java (and OS) until the cost of updating is less than the cost of not updating. correct, but at the same time companies are typically security aware, and java 6 (and below) have some serious know issues. I would have thought that its possible to develop/built with java 7 and still have java 5,6 as runtime environment, but looking at the code it does not seem easy (we would have to get the java version, and use different API calls). Java is upwards compatible (except parts of JDBC). So it should be possible to restrict the code to the Java 5 API and it would then work on Java 6 and 7 and 8 etc. rgds jan I. This would prevent many queries on the Forum of why OO doesn't work with an installed Java. -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
Hi, sorry for top-posting: But please use the new thread for the discussion of dropping Java 5 and Java 6 support for Windows. Otherwise, it may happen that your arguement were lost for this discussion. Thanks in advance, Oliver. On 07.08.2013 12:59, sebb wrote: On 7 August 2013 11:55, janI j...@apache.org wrote: On 7 August 2013 12:51, sebb seb...@gmail.com wrote: On 7 August 2013 09:33, Rory O'Farrell ofarr...@iol.ie wrote: I'm deleting the quotes of the earlier discussion as it is not relevant to my point here. I have no experience of building with Java and care little about the security holes, so I bow to the expertise of those who know better. If changes are being made to the OpenOffice/Java interaction, would it be possible that these be done in such a way that no matter whether installed on a 32 or 64 bit windows, OpenOffice interfaced correctly with the installed Java, so doing away with the requirement that a 32 bit Java be installed. +1 +1 AOO should work with what is installed, [though there is probably no need to support Java 4 or earlier any more.] Just because Java 5 or 6 is no longer current does not mean it is not being used. In particular, businesses tend to stay on older versions of Java (and OS) until the cost of updating is less than the cost of not updating. correct, but at the same time companies are typically security aware, and java 6 (and below) have some serious know issues. I would have thought that its possible to develop/built with java 7 and still have java 5,6 as runtime environment, but looking at the code it does not seem easy (we would have to get the java version, and use different API calls). Java is upwards compatible (except parts of JDBC). So it should be possible to restrict the code to the Java 5 API and it would then work on Java 6 and 7 and 8 etc. rgds jan I. This would prevent many queries on the Forum of why OO doesn't work with an installed Java. -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
Hi, On 03.08.2013 10:18, Andrea Pescetti wrote: On 01/08/2013 Oliver-Rainer Wittmann wrote: Version 2.7.1-1 now takes line endings in the patch file and in the file to be patch serious. Thus, the application of a patch fails when the line endings are different. I haven't investigated this deeply at the time, but the hsqldb module has a mix of line endings (that led to a broken patch too) and uses CONVERTFILES in makefile.mk to harmonize them. Thx for the feedback. In the meanwhile my changes regarding 'patch' version 2.7.1-1 broke the Linux build - see our Linux 64bit and 32bit build bots. I am working on a corresponding patch. There are issues 121690 [3] and 121754 [4] regarding building with Java 7 (JDK 1.7) and HSQLDB. I think these issues are the duplicates of each other [please, can one of the people involved in these issues - e.g. Fred, Ariel or Andrea confirm this? Thx in advance]. As far as I understood these issues are solved. Please correct me, if I am wrong. 121754 is fixed. 121690 is more generic; I confirm that after fixing 121754 I had no problems in building with Java 7, so it might be that HSQLDB was the only problem. But I only tried with some standard build options. Namely, I didn't try with --with-junit or similar, and Kay reported issues with that. On a Windows system with JRE 6 the installation of my build does not recognize installed JRE 6 as an Java runtime environment (Menu - Tools - Option - Java). This is no problem from my point of view as our Windows users should not have JRE 6 installed anymore on their systems due to its security risks. Does somebody contradicts? As far as I know, this would be a significant limitation. We can now build with Java 5, 6 or 7 and the build can work with Java 5, 6 or 7 (regardless of the version used for building). Restricting this would require discussion, especially on less common platforms. I agree that it would be a restriction, but due to the security risks of Oracle's JRE 6 I do not think that such a restriction hurts. In contrast it would 'help' our Windows users to update their Java environment. Thus, let us start a new thread to discuss this topic. Best regards, Oliver. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 8/5/13 10:11 AM, Oliver-Rainer Wittmann wrote: Hi, On 03.08.2013 10:18, Andrea Pescetti wrote: On 01/08/2013 Oliver-Rainer Wittmann wrote: Version 2.7.1-1 now takes line endings in the patch file and in the file to be patch serious. Thus, the application of a patch fails when the line endings are different. I haven't investigated this deeply at the time, but the hsqldb module has a mix of line endings (that led to a broken patch too) and uses CONVERTFILES in makefile.mk to harmonize them. Thx for the feedback. In the meanwhile my changes regarding 'patch' version 2.7.1-1 broke the Linux build - see our Linux 64bit and 32bit build bots. I am working on a corresponding patch. There are issues 121690 [3] and 121754 [4] regarding building with Java 7 (JDK 1.7) and HSQLDB. I think these issues are the duplicates of each other [please, can one of the people involved in these issues - e.g. Fred, Ariel or Andrea confirm this? Thx in advance]. As far as I understood these issues are solved. Please correct me, if I am wrong. 121754 is fixed. 121690 is more generic; I confirm that after fixing 121754 I had no problems in building with Java 7, so it might be that HSQLDB was the only problem. But I only tried with some standard build options. Namely, I didn't try with --with-junit or similar, and Kay reported issues with that. On a Windows system with JRE 6 the installation of my build does not recognize installed JRE 6 as an Java runtime environment (Menu - Tools - Option - Java). This is no problem from my point of view as our Windows users should not have JRE 6 installed anymore on their systems due to its security risks. Does somebody contradicts? As far as I know, this would be a significant limitation. We can now build with Java 5, 6 or 7 and the build can work with Java 5, 6 or 7 (regardless of the version used for building). Restricting this would require discussion, especially on less common platforms. I agree that it would be a restriction, but due to the security risks of Oracle's JRE 6 I do not think that such a restriction hurts. In contrast it would 'help' our Windows users to update their Java environment. Thus, let us start a new thread to discuss this topic. we should think how relevant it is and if we have more work to support it. As Oliver pointed out, the latest security problems of Java result in probably many updated systems. I don't see that Java 5 or 6 is important in the future and we should focus on the future. Juergen Best regards, Oliver. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Build Environment] Windows - build using Java 7 (JDK 1.7) without having Visual Studio
On 01/08/2013 Oliver-Rainer Wittmann wrote: Version 2.7.1-1 now takes line endings in the patch file and in the file to be patch serious. Thus, the application of a patch fails when the line endings are different. I haven't investigated this deeply at the time, but the hsqldb module has a mix of line endings (that led to a broken patch too) and uses CONVERTFILES in makefile.mk to harmonize them. There are issues 121690 [3] and 121754 [4] regarding building with Java 7 (JDK 1.7) and HSQLDB. I think these issues are the duplicates of each other [please, can one of the people involved in these issues - e.g. Fred, Ariel or Andrea confirm this? Thx in advance]. As far as I understood these issues are solved. Please correct me, if I am wrong. 121754 is fixed. 121690 is more generic; I confirm that after fixing 121754 I had no problems in building with Java 7, so it might be that HSQLDB was the only problem. But I only tried with some standard build options. Namely, I didn't try with --with-junit or similar, and Kay reported issues with that. On a Windows system with JRE 6 the installation of my build does not recognize installed JRE 6 as an Java runtime environment (Menu - Tools - Option - Java). This is no problem from my point of view as our Windows users should not have JRE 6 installed anymore on their systems due to its security risks. Does somebody contradicts? As far as I know, this would be a significant limitation. We can now build with Java 5, 6 or 7 and the build can work with Java 5, 6 or 7 (regardless of the version used for building). Restricting this would require discussion, especially on less common platforms. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
