BorlandTalk.com Borland discussion newsgroups   Archives   FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in  How to use a common JDK 1.4.2?          BorlandTalk.com Forum Index -> JBuilder IDE View previous topic :: View next topic   Author Message Heinz Wehner Guest Posted: Fri Dec 19, 2003 11:05 pm    Post subject: How to use a common JDK 1.4.2? I've just installed JBuilderX Foundation and noticed that the IDE is based on a JDK 1.4.2 located in subdirectory jdk1.4. The same is true for C++BuilderX Personal and for using other software, I also need to install another copy of Sun's JDK 1.4.2. This means 2 redundant copies of the same JDK. I think everybody would agree that this is a waste of disk space. One JDK 1.4.2 should suffice. Is it possible to advise JBuilderX (and C++BuilderX) to use a JDK 1.4.2 that is installed in another location, like C:jdk1.4.2 for example? Heinz Wehner (Karlsruhe, Germany) Back to top Rock Guest Posted: Sat Dec 20, 2003 5:49 am    Post subject: Re: How to use a common JDK 1.4.2? Select menu "Tools->Configure JDKs..." then click "Change..." button, browser to new JDK location and click "OK". JBuiler'll set CLASSPATH to your new JDK location automatically, that's all. Rock "Heinz Wehner" <Heinz.Wehner (AT) ecoBus (DOT) de> wrote Quote: I've just installed JBuilderX Foundation and noticed that the IDE is based on a JDK 1.4.2 located in subdirectory jdk1.4. The same is true for C++BuilderX Personal and for using other software, I also need to install another copy of Sun's JDK 1.4.2. This means 2 redundant copies of the same JDK. I think everybody would agree that this is a waste of disk space. One JDK 1.4.2 should suffice. Is it possible to advise JBuilderX (and C++BuilderX) to use a JDK 1.4.2 that is installed in another location, like C:jdk1.4.2 for example? Heinz Wehner (Karlsruhe, Germany) Back to top Ludovic HOCHET Guest Posted: Sat Dec 20, 2003 10:25 am    Post subject: Re: How to use a common JDK 1.4.2? In <JBuilder/CBX>/bin/jdk.config change the path to the jdk (initially: .../jdk1.4) to the path of the jdk you want to use. Please note though that JB10 and CBX don't use exactly the same version (JB10: 1.4.2_01 and CBX: 1.4.2) which means that they might not behave fully idententically if you change their host jdk to another one. HTH, Heinz Wehner a écrit : Quote: I've just installed JBuilderX Foundation and noticed that the IDE is based on a JDK 1.4.2 located in subdirectory jdk1.4. The same is true for C++BuilderX Personal and for using other software, I also need to install another copy of Sun's JDK 1.4.2. This means 2 redundant copies of the same JDK. I think everybody would agree that this is a waste of disk space. One JDK 1.4.2 should suffice. Is it possible to advise JBuilderX (and C++BuilderX) to use a JDK 1.4.2 that is installed in another location, like C:jdk1.4.2 for example? Heinz Wehner (Karlsruhe, Germany) -- Ludovic ----------------------------------------- "Les formes qui differencient les etres importent peu si leur pensees s'unissent pour batir un univers..." Yoko Tsuno (in 'Les titans' by Roger Leloup) [The shapes that differenciate beings are not important if their thoughts unite to build a universe] Back to top Heinz Wehner Guest Posted: Sun Dec 21, 2003 9:42 pm    Post subject: Re: How to use a common JDK 1.4.2? Hello Rock, thanks for your tip. I was already aware of this option but I think the alternative pointed out in another reply (new to me) by making the changes in binjdk.config is better. It allows to advise JBuilder to not only use the specified JDK for running the IDE but also for building projects. Another advantage is that the reconfiguration can be done without and before launching the IDE. Heinz Wehner (Karlsruhe, Germany) On Sat, 20 Dec 2003 12:49:03 +0700, "Rock" <evilhunter (AT) lycos (DOT) co.uk> wrote: Quote: Select menu "Tools->Configure JDKs..." then click "Change..." button, browser to new JDK location and click "OK". JBuilder'll set CLASSPATH to your new JDK location automatically, that's all. Rock "Heinz Wehner" <Heinz.Wehner (AT) ecoBus (DOT) de> wrote in message news:5217uv4hdcvqjep68o4np189j8etfh8n1k (AT) 4ax (DOT) com... I've just installed JBuilderX Foundation and noticed that the IDE is based on a JDK 1.4.2 located in subdirectory jdk1.4. The same is true for C++BuilderX Personal and for using other software, I also need to install another copy of Sun's JDK 1.4.2. This means 2 redundant copies of the same JDK. I think everybody would agree that this is a waste of disk space. One JDK 1.4.2 should suffice. Is it possible to advise JBuilderX (and C++BuilderX) to use a JDK 1.4.2 that is installed in another location, like C:jdk1.4.2 for example? Heinz Wehner (Karlsruhe, Germany) Back to top Heinz Wehner Guest Posted: Sun Dec 21, 2003 10:39 pm    Post subject: Re: How to use a common JDK 1.4.2? Hello Ludovic, thanks for the hint regarding the file "jdk.config". I now have only a single installation of Sun's latest JDK 1.4.2 that is used by JBuilderX, C++BuilderX and lots of other Java software. That freed almost 200MB of valuable disk space. I'm aware of the small risk that you've mentioned but if we have reached the point that Java software only runs reliably on a specific build of the JDK/JRE, then something went wrong anyway... I've just seen that there's a directory libtemp which is used by LaunchAnywhere's native launcher. It seems as if I'd ave to change the VM path in file temp.lax as well. Does anybody know which JBuilderX tasks need this native launcher? What is it good for? Heinz Wehner (Karlsruhe, Germany) On Sat, 20 Dec 2003 11:25:58 +0100, Ludovic HOCHET <personne@nullepart> wrote: Quote: In <JBuilder/CBX>/bin/jdk.config change the path to the jdk (initially: ../jdk1.4) to the path of the jdk you want to use. Please note though that JB10 and CBX don't use exactly the same version (JB10: 1.4.2_01 and CBX: 1.4.2) which means that they might not behave fully identically if you change their host jdk to another one. HTH, Heinz Wehner a écrit : I've just installed JBuilderX Foundation and noticed that the IDE is based on a JDK 1.4.2 located in subdirectory jdk1.4. The same is true for C++BuilderX Personal and for using other software, I also need to install another copy of Sun's JDK 1.4.2. This means 2 redundant copies of the same JDK. I think everybody would agree that this is a waste of disk space. One JDK 1.4.2 should suffice. Is it possible to advise JBuilderX (and C++BuilderX) to use a JDK 1.4.2 that is installed in another location, like C:jdk1.4.2 for example? Heinz Wehner (Karlsruhe, Germany) Back to top Ludovic HOCHET Guest Posted: Mon Dec 22, 2003 10:59 am    Post subject: Re: How to use a common JDK 1.4.2? Hallo Heinz, Quote: That freed almost 200MB of valuable disk space. ah only I'm disappointed ;) Quote: I'm aware of the small risk that you've mentioned but if we have reached the point that Java software only runs reliably on a specific build of the JDK/JRE, then something went wrong anyway... Well it is I think the case for all program that tries to work arround bugs in the libraries that it is using... Quote: I've just seen that there's a directory libtemp which is used by LaunchAnywhere's native launcher. It seems as if I'd ave to change the VM path in file temp.lax as well. Does anybody know which JBuilderX tasks need this native launcher? What is it good for? My guess it is only used if you run the uninstaller which is only helpfull to remove all the little windows things that one might not think about A+, -- Ludovic ----------------------------------------- "Les formes qui differencient les etres importent peu si leur pensees s'unissent pour batir un univers..." Yoko Tsuno (in 'Les titans' by Roger Leloup) [The shapes that differenciate beings are not important if their thoughts unite to build a universe] Back to top Heinz Wehner Guest Posted: Mon Dec 22, 2003 3:15 pm    Post subject: Re: How to use a common JDK 1.4.2? Hello Ludovic, On Mon, 22 Dec 2003 11:59:27 +0100, Ludovic HOCHET <personne@nullepart> wrote: Quote: I'm aware of the small risk that you've mentioned but if we have reached the point that Java software only runs reliably on a specific build of the JDK/JRE, then something went wrong anyway... Well it is I think the case for all program that tries to work arround bugs in the libraries that it is using... If Borland does indeed work-around any library bugs (and I think they should do this for show-stoppers only), they should document it. I'm not sure if that is really the case. Quote: I've just seen that there's a directory libtemp which is used by LaunchAnywhere's native launcher. It seems as if I'd have to change the VM path in file temp.lax as well. Does anybody know which JBuilderX tasks need this native launcher? What is it good for? My guess it is only used if you run the uninstaller which is only helpfull to remove all the little windows things that one might not think about. Yes, that could be. Actually, other than the uninstall entry and the handlers for project and source files, I can't spot anything else that is entered into the Windows registry. Regards, Heinz Back to top Gillmer J. Derge (TeamB) Guest Posted: Mon Dec 22, 2003 3:36 pm    Post subject: Re: How to use a common JDK 1.4.2? "Heinz Wehner" <Heinz.Wehner (AT) ecoBus (DOT) de> wrote Quote: If Borland does indeed work-around any library bugs (and I think they should do this for show-stoppers only), they should document it. Why? From a user's point of view, it shouldn't even be important to know that JBuilder is written in Java. It's an application. You run it and it works or it doesn't. How it's implemented is Borland's business. If the Microsoft Word source code includes a workaround for a C++ compiler bug, do you expect Microsoft to tell you about it? Of course not. You don't care about the Word source code or Microsoft's workarounds. You just want to be able to do word processing. Quote: I'm not sure if that is really the case. It is. For example, note the XPTreeUIFix, TabbedPaneFix, and SequencedEventFix JAR files listed in jbuilder.config. Who knows what other workarounds might be elsewhere. These are also an example of where the C++BuilderX JDK and the JBuilder X JDK may differ. cbuilder.config doesn't refer to XPTreeUIFix. Maybe that's a new bug introduced in JDK 1.4.2_01-b06. If so, then by switching JBuilder over to CBuilderX's JDK you may be breaking the fix. Or by switching CBuilderX over to JBuilder's JDK you may be introducing a new bug without adding the fix. Quote: I've just seen that there's a directory libtemp which is used by LaunchAnywhere's native launcher. FYI, I don't have that directory on my machine. -- Gillmer J. Derge (TeamB) Back to top Heinz Wehner Guest Posted: Mon Dec 22, 2003 11:59 pm    Post subject: Re: How to use a common JDK 1.4.2? Gillmer, Quote: If Borland does indeed work-around any library bugs (and I think they should do this for show-stoppers only), they should document it. Why? From a user's point of view, it shouldn't even be important to know that JBuilder is written in Java. It's an application. You run it and it works or it doesn't. How it's implemented is Borland's business. If the Microsoft Word source code includes a workaround for a C++ compiler bug, do you expect Microsoft to tell you about it? Of course not. You don't care about the Word source code or Microsoft's workarounds. You just want to be able to do word processing. My point is that not all is well if we all end up having dozens of different Java runtimes on our systems. We have already reached a state where the majority of Java applications come with their own private JRE. The situation then becomes somehow similar to the old MS-DOS times where we didn't have DLL's which forced us to include runtime libraries into the EXE file. Quote: I'm not sure if that is really the case. It is. For example, note the XPTreeUIFix, TabbedPaneFix, and SequencedEventFix JAR files listed in jbuilder.config. Who knows what other workarounds might be elsewhere. These are also an example of where the C++BuilderX JDK and the JBuilder X JDK may differ. cbuilder.config doesn't refer to XPTreeUIFix. Maybe that's a new bug introduced in JDK 1.4.2_01-b06. If so, then by switching JBuilder over to CBuilderX's JDK you may be breaking the fix. Or by switching CBuilderX over to JBuilder's JDK you may be introducing a new bug without adding the fix. I'm now using the latest JRE 1.4.2_03. I don't really see what might break as long as JBuilderX uses the patched JAR's. Am I missing something here? Quote: I've just seen that there's a directory libtemp which is used by LaunchAnywhere's native launcher. FYI, I don't have that directory on my machine. Thanks for the info. Heinz Wehner (Karlsruhe, Germany) Back to top Gillmer J. Derge (TeamB) Guest Posted: Tue Dec 23, 2003 12:23 am    Post subject: Re: How to use a common JDK 1.4.2? "Heinz Wehner" <Heinz.Wehner (AT) ecoBus (DOT) de> wrote Quote: I'm now using the latest JRE 1.4.2_03. I don't really see what might break as long as JBuilderX uses the patched JAR's. Am I missing something here? I don't know, but what I was getting at is this. Out of the box, C++BuilderX uses JRE 1.4.2-b28 and JBuilder X uses the slightly newer JRE 1.4.2_01-b06. JBuilder X includes XPTreeUIFix, but C++Builder X does not. That leads me to wonder why that fix wasn't included with C++Builder X. Of course, there are all sorts of reasons why that might be the case. Maybe nobody had noticed that bug before. Maybe they had noticed but didn't have a good fix. Or maybe that bug doesn't exist in JRE 1.4.2-b28. What if the XP Tree UI bug (whatever that is) is a new problem that was introduced accidentally in 1.4.2_01-b06? If that's the case -- and I have no idea if it is, but if so ... -- then switching C++Builder X over to JRE 1.4.2_01-b06 will introduce that bug into C++Builder X. But C++Builder X doesn't have that XPTreeUIFix.jar file, so it will have the bug but not the workaround. That's bad. Alternatively, what if you switch JBuilder to use C++Builder X's JDK? Then you've kept the fix in JBuilder, but you've switched to a JDK that didn't have the problem. Will the fix still work, or will it break something? We don't know. And what if you switch both to JRE 1.4.2_03? Does 1.4.2_03 still have the XP Tree UI bug? Does it need that fix? Again, we don't know. I'm not saying that your change definitely won't work. In fact, I think it probably will work. I'm just pointing out that there are fairly real reasons to wonder about differences even between JDK's with similar version numbers. It's not a completely theoretical argument. In fact, I think it was JBuilder 9 or maybe 8 where upgrading from 1.4.1 to a newer 1.4.1 completely broke the compiler. So just keep your eyes out for unanticipated problems. -- Gillmer J. Derge (TeamB) Back to top Heinz Wehner Guest Posted: Tue Dec 23, 2003 6:10 pm    Post subject: Re: How to use a common JDK 1.4.2? Gillmer, thanks for elaborating on the patches and upgrade issue. I understand that there is a slight risk for breaking Borland's fixes with new (and fixed) JRE's. However, this point confirms what I've already requested in a previous message. If Borland would document the bugs they have fixed in the base JRE, then we could check if a new JRE includes a fix or not. If it does, we could simply remove the references to the patched JAR and regain consistency. Heinz Wehner (Karlsruhe, Germany) On Mon, 22 Dec 2003 19:23:55 -0500, "Gillmer J. Derge (TeamB)" <spam (AT) gillmerderge (DOT) com> wrote: Quote: "Heinz Wehner" <Heinz.Wehner (AT) ecoBus (DOT) de> wrote in message news:v01fuvs13ioehm3knf1b2em8eo3i07ph4q (AT) 4ax (DOT) com... I'm now using the latest JRE 1.4.2_03. I don't really see what might break as long as JBuilderX uses the patched JAR's. Am I missing something here? I don't know, but what I was getting at is this. Out of the box, C++BuilderX uses JRE 1.4.2-b28 and JBuilder X uses the slightly newer JRE 1.4.2_01-b06. JBuilder X includes XPTreeUIFix, but C++Builder X does not. That leads me to wonder why that fix wasn't included with C++Builder X. Of course, there are all sorts of reasons why that might be the case. Maybe nobody had noticed that bug before. Maybe they had noticed but didn't have a good fix. Or maybe that bug doesn't exist in JRE 1.4.2-b28. What if the XP Tree UI bug (whatever that is) is a new problem that was introduced accidentally in 1.4.2_01-b06? If that's the case -- and I have no idea if it is, but if so ... -- then switching C++Builder X over to JRE 1.4.2_01-b06 will introduce that bug into C++Builder X. But C++Builder X doesn't have that XPTreeUIFix.jar file, so it will have the bug but not the workaround. That's bad. Alternatively, what if you switch JBuilder to use C++Builder X's JDK? Then you've kept the fix in JBuilder, but you've switched to a JDK that didn't have the problem. Will the fix still work, or will it break something? We don't know. And what if you switch both to JRE 1.4.2_03? Does 1.4.2_03 still have the XP Tree UI bug? Does it need that fix? Again, we don't know. I'm not saying that your change definitely won't work. In fact, I think it probably will work. I'm just pointing out that there are fairly real reasons to wonder about differences even between JDK's with similar version numbers. It's not a completely theoretical argument. In fact, I think it was JBuilder 9 or maybe 8 where upgrading from 1.4.1 to a newer 1.4.1 completely broke the compiler. So just keep your eyes out for unanticipated problems. Gillmer J. Derge (TeamB) Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First         BorlandTalk.com Forum Index -> JBuilder IDE All times are GMT Page 1 of 1   Jump to: Select a forum C++ Builder Newsgroups----------------C++ BuilderC++ Builder (ActiveX)C++ Builder (Announcements)C++ Builder (Command Line Tools)C++ Builder DatabasesC++ Builder Databases (ADO)C++ Builder Databases (Desktop)C++ Builder Databases (InterBase Express)C++ Builder Databases (Multi-Tier)C++ Builder Databases (SQL Servers)C++ Builder (Graphics)C++ Builder (IDE)C++ Builder (Internet)C++ Builder (Internet Socket)C++ Builder (Internet Web)C++ Builder (Jobs)C++ Builder (Language)C++ Builder (Language C++)C++ Builder (Compatibility with MFC)C++ Builder (Native API)C++ Builder (Non-Technical)C++ Builder (Students)C++ Builder (Third Party Tools)C++ Builder (Upgrade)C++ Builder (VCL)C++ Builder (VCL Components Usage)C++ Builder (VCL Components Development)C++ Builder (VCL Usage)C++ Builder (WinAPI)C++ Builder Installation Delphi Newsgroups----------------Delphi (General)Delphi ActiveX Controls UsageDelphi ActiveX Controls DevelopmentDelphi As400Delphi DatabasesDelphi Databases (ADO)Delphi Databases (dbExpress)Delphi Databases (Desktop)Delphi Databases (InterBase Express)Delphi Databases (Multi-Tier)Delphi Databases (SQL Servers)Delphi DeploymentDelphi GraphicsDelphi IDEDelphi InternationalizationDelphi InternetDelphi Internet Isapi-WebBrokerDelphi Internet WebSnapDelphi Internet WinsockDelphi JobsDelphi Language BASMDelphi Language ObjectPascalDelphi Model Driven Architecture (General)Delphi Model Driven Architecture (Third Party)Delphi MultimediaDelphi Native APIDelphi Non-TechnicalDelphi ObjectPascalDelphi OLE AutomationDelphi OO designDelphi OpenToolsAPIDelphi Reporting-ChartingDelphi RTLDelphi StudentsDelphi TeamSourceDelphi Thirdparty ToolsDelphi Thirdparty Tools (General)Delphi Thirdparty Tools (IntraWeb)Delphi Thirdparty Tools (RaveReports)Delphi UpgradeDelphi VCLDelphi VCL ComponentsDelphi VCL Components UsingDelphi VCL Components WritingDelphi WebServices SOAPDelphi WinAPIDelphi XMLDelphi Installationcomp.lang.pascal.delphi.components.misccomp.lang.pascal.delphi.components.usagecomp.lang.pascal.delphi.components.writingcomp.lang.pascal.delphi.databasescomp.lang.pascal.delphi.misccomp.sources.delphi JBuilder Newsgroups----------------JBuilderJBuilder AnnouncementsJBuilder Applet IssuesJBuilder As400JBuilder CompilerJBuilder CORBA/RMIJBuilder DatabasesJBuilder DB SwingJBuilder DebuggerJBuilder DeploymentJBuilder DocumentationJBuilder EnterpriseJBuilder HandheldJBuilder IDEJBuilder JavaJBuilder JavaAPIJBuilder Java LanguageJBuilder Java SwingJBuilder Java BeansJBuilder Java Beans UsageJBuilder Java Beans DevelopmentJBuilder JBCLJBuilder JDataStoreJBuilder JobsJBuilder LinuxJBuilder MacintoshJBuilder & MobileSetJBuilder MultiLingual AppsJBuilder Non-TechnicalJBuilder OpenToolsJBuilder Servlets (JSP)JBuilder StudentsJBuilder Team DevelopmentJBuilder Thirdparty ToolsJBuilder UpgradeJBuilder Installation InterBase Newsgroups----------------InterBaseInterBase Bug DiscussionInterBase GeneralInterBase IBConsoleInterBase OpenSourceInterBase ReplicationInterBase SQLInterBase ThirdpartyInterBase Installation Miscellaneous Borland Newsgroups----------------AppCenterAppServerEnteraVisiBroker  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum Powered by phpBB © 2001, 2006 phpBB Group SEO toolkit © 2004-2006 webmedic.