Mac How To Edit Info.plist For Java 1.7
Thanks for the links. I've created all the directories and files, now I just need figure out what to put in the Info.plist because they say Xcode generates it for you, but I don't think they support Java projects anymore. Your site is one of the best out there for development. Thanks for what you provide. Stay Private and Protected with the Best Firefox Security Extensions The Best Video Software for Windows The 3 Free Microsoft Office Photo Editor Alternatives Get the.
Greetings, admonishment: below is definitely a lot of gory details of getting ImageJ running with Java 1.7x on a Macintosh. If this is definitely not really of interest to you then you can strike the delete switch now. Overview: Apple created it'h own Java and application bundler that utilized unique Information.plist keywords, but Apple stopped performing therefore with Java 1.6x. Currently if you require new Java variations you'll have to perform significantly of the function yourself to compile ImageJ and produce the bundle. Unfortunately Coffee 1.7 and increased will not really operate on devices running Mac pc OS Times10.6 and lower, so for compatibility you'd need to stick with Apple's Coffee 1.6. My version of ImageJ (centered on ImageJ 1.43, working on Mac 10.9) had been plagued with recurring accidents that experienced something to perform with relocating, resizing and/or accessing image windows.
It crashed like that it had been not achievable to debug the program code to discover the precise place in the code where it crashéd, and it crashéd at arbitrary places in the system. About every third work would crash like this. A google search suggested as a factor java 1.6 as a possible culprit, therefore I went about installing and operating java 1.7. Bouncing to the end of my story, with Coffee 1.7.060 I possess had none of the windows-related crashes that affected my system formerly. Along the method I learned a several important factors about Macs and Coffee. Through Coffee 1.6, Apple made it's i9000 own version of Java but they ceased with that version.
My Macintosh does automatic improvements of most programs, including Java, so my Macintosh had already Orcacle't Coffee JRE 1.7x. Many web pages and programs that operate Java on my device already operate with this Coffee 1.7, however when running through a terminal windowpane or when using Xcode to put together ImageJ, the device uses the latest developer version of Java, which had been Apple company's Java 1.6x. If you open up a airport window you can sort ‘Java - edition' to notice which designer version you have got. This is usually because Mac pc updates only the JRE, not really the JDK. To obtain everything working Java 1.7x you possess to download and install the 0racle JDK 1.7x.
With JDK 1.7.060 set up, after compiling my version of lmageJ with Xcode, Xcodé would begin up the program and it would operate using Coffee 1.7x. However, when making use of the ImageJ desktop computer icon the program would not start, with an mistake message to the effect that Coffee 1.6x is certainly needed. Back when Apple made their own Coffee, they also produced their very own program that created application bundles for each plan. Someone upward in NIH ImageJ-land used this program to develop the application bundle that affiliates the ImageJ desktop symbol with the jogging of ImageJ. You can appear at this program package by right-cIicking over the desktop computer symbol and selecting “Shów in Finder”; insidé Finder right-click over the ImageJ64.app and go for “Display Package Contents”; and inside the bundle contents there will be the Information.plist file; inside the Coffee subdirectory can be ij.container; and inside thé MacOS subdirectory is the ‘JavaApplicationStub'. The package deal invokes Coffee/ij.jar using MacOS/JavaApplicationStub and states executable choices in Information.plist.
How To Edit Info.plist In Mac
For my lab, whenever I got an up to date version of my ij.jar I would duplicate it into this Material/Java/ folder. For my very own make use of though I edited the Information.plist document to stage to my regional ij.container: homedir/ImageJ/ij.container. This will get around the need to generate a fresh application bundle every period ij.jar is up to date. I furthermore added an JVMOption tag in Info.plist that sets my maximum system executable storage to something properly large for my Mac pc's 20G of Memory, making use of ‘-Xmx18000m' in the industry for the execution-time option. ImageJ enables you set the memory allocations within the ‘Edit'->'Options' menus product and stores the preferences in IJ.prefs, nevertheless Xcode does not notice this. I need furthermore to point to my regional plugins listing which is done with another JVMOption tag ‘-Dplugins.dir=homédir/ImageJ/plugins' 6. The program bundle runs JavaApplicationStub that has been created using Apple company's bundler device and Java1.6x and therefore would not really operate the brand-new ij.jar compiled using Java 1.7x.
To obtain an appropriate application package, since Apple stopped delivering their own device, you require to make use of the tool provided by Oracle: Sticking with their instructions, I included code to the construct.xml that is usually/was utilized to put together ImageJ and used ‘Ant' in a fatal home window to create the application deal. It also transforms out that Apple company stopped like ‘Ant' in the program so that had to end up being downloaded and installed from.
This produces an software bunch that is usually equivalent to the initial one for lmageJ, but the real executable is now named JavaAppLauncher rather than JavaApplicationStub. Almost there. Along with their very own edition of Java 1.6 and very own application bundler tool, Apple furthermore used their very own keys/tags within Details.plist that are usually various from those utilized by Oracle. Therefore in the brand-new application bunch I experienced to transpose the secrets/tags from the initial Info.plist into the brand-new one.
Find Of particular significance for me had been that I earlier pointed to my regional ij.container using the ‘ClassPath' key/tag, and right now I add a thread label to JVMOptions with contents ‘-cp' (where ‘cp' appears for course route) and then the next string tag under JVMOptions is usually the actual route to my ij.jar, e.g. homedir/ImageJ/ij.container Fortunately the plugin.dir and storage settings labels are usually the same as just before. In overview, Apple produced it'h own Java and program bundler that used unique Details.plist keywords, but Apple company stopped performing therefore with Java 1.6x.
Presently if you need new Coffee variations you'll have got to perform significantly of the work yourself to generate the package. Unfortunately Java 1.7 and increased will not really operate on devices running Mac OS X10.6 and lower, therefore for compatibility you'd require to stay with Apple's Coffee 1.6. Ultimately this will all have got to obtain proved helpful out in the major ImageJ and/or Fiji packages, but for me I have my work-around. I do not yet know how ij.jar structured on java 1.7x will run on Master of science Windows-based PCs. Walter U'Dell, PhD Assistant Professor Dept. Rays Oncology McKnight Human brain lnst. Rm LG-177 PO Container 100385 UF Wellness Cancer Middle University of Fl Gainesville, Florida 32610 352-273-9030 - ImageJ sending listing.
My iMac provides 1.7 but my MacAir evidently automatically up to date to 1.8: Roberts-MacBook-Air: nate$ javac -edition javac 1.8.005 Roberts-MacBook-Air: nate$ java -version java version '1.8.005' Java(TM) SE Runtime Atmosphere (develop 1.8.005-m13) Coffee HotSpot(TM) 64-Bit Machine VM (construct 25.5-m02, blended mode) I've not been active on either machine lately. I hope to move to 1.8 when my new work personal computer gets there and I install Ubuntu 14.04. Thanks a lot for the dialogue. On Wednesday, Jul 7, 2014 at 3:58 PM, Walter U'Dell authored. >hello, >>forewarning: below is definitely a lot of gory details of getting ImageJ working with >Java 1.7x on a Mac. If this will be not of interest to you then you can hit the >delete switch now.
>>Summary: Apple developed it'beds own Coffee and software bundler that utilized >unique Details.plist keywords, but Apple stopped carrying out so with Coffee 1.6x. >Currently if you need new Coffee versions you'll possess to do very much of the work >yourself to compile ImageJ and make the package. Unfortunately Coffee 1.7 >and higher will not operate on devices running Mac pc OS X10.6 and lower, therefore for >compatibility you'd require to stay with Apple's Coffee 1.6. >>My version of ImageJ (centered on ImageJ 1.43, working on Macintosh 10.9) had been >plagued with repeated failures that experienced something to do with shifting, >resizing and/or being able to view image home windows. It crashed like that it had been not >feasible to debug the code to discover the precise location in the program code where it >crashéd, and it crashéd at random areas in the system. About every third >work would lock up like this. A google lookup suggested as a factor java 1.6 as a >probable culprit, therefore I proceeded to go about setting up and working java 1.7.
Leaping >to the finish of my tale, with Java 1.7.060 I have got had none of them of the >windows-related failures that affected my plan earlier. >>Along the way I learned a few important items about Macs and Coffee. Through Java 1.6, Apple produced it's i9000 own edition of Coffee but they >stopped with that edition.
My Mac pc does automated updates of many programs, like Java, so my >Mac had already Orcacle's Coffee JRE 1.7x. Many web web pages and applications that >run Java on my device already run with this Coffee 1.7, however when operating >through a fatal window or when using Xcode to put together ImageJ, the >device utilizes the latest developer version of Coffee, which had been Apple's Coffee >1.6x. If you open a airport windowpane you can form ‘Java - version' to discover >which developer version you have got. This will be because Mac pc updates only the JRE, >not really the JDK. To obtain everything running Coffee 1.7x you possess to download and >set up the 0racle JDK 1.7x. With JDK 1.7.060 installed, after obtaining my version of lmageJ with >Xcode, Xcodé would start up the program and it would operate using Java 1.7x.
>Nevertheless, when making use of the ImageJ desktop icon the system would not start, >with an error information to the impact that Coffee 1.6x is usually needed. Back when Apple produced their very own Java, they furthermore produced their own program >that developed application bundles for each system. Someone upward in NIH >ImageJ-land used this system to develop the software bunch that >affiliates the ImageJ desktop image with the jogging of ImageJ. You can look >at this program package deal by right-cIicking over the desktop computer symbol and >selecting “Show in Finder”; inside Finder right-click ovér the ImageJ64.app >and go for “Present Package Items”; and inside the bundle articles there >is certainly the Information.plist file; inside the Coffee subdirectory can be ij.jar; and inside >the MacOS subdirectory can be the ‘JavaApplicationStub'. The pack creates >Java/ij.jar using MacOS/JavaApplicationStub and says executable options in >Details.plist. For my laboratory, whenever I had an up to date edition of my ij.jar I would copy >it into this Contents/Java/ folder.
For my own make use of though I modified the >Info.plist document to stage to my local ij.container: homedir/ImageJ/ij.jar. This >gets around the want to create a brand-new application package every time ij.container >is updated. I furthermore included an JVMOption tag in Details.plist that sets my >maximum program executable storage to something properly large for my >Mac pc's 20G of Ram memory, making use of ‘-Xmx18000m' in the industry for the execution-time >option. ImageJ enables you arranged the memory allocations within the >‘Edit'->'Choices' menus product and shops the preferences in IJ.prefs, nevertheless >Xcode does not see this.
I require also to point to my local plugins >directory website which is definitely completed with another JVMOption label >‘-Dplugins.dir=homédir/ImageJ/plugins' >>6. The program bundle operates JavaApplicationStub that was created making use of >Apple's bundler device and Coffee1.6x and thus would not really run the new ij.container >put together using Coffee 1.7x.
To accomplish an appropriate application bundle, >since Apple stopped supplying their own tool, you need to make use of the device >supplied by Oracle: >>>>Sticking with their instructions, I added program code to the construct.xml that is certainly/was used >to put together ImageJ and used ‘Ant' in a fatal windowpane to make the >software deal. It also transforms out that Apple stopped including ‘Ant' in >the program so that acquired to become downloaded and set up from >. >This generates an software deal that can be comparable to the first one for >lmageJ, but the actual executable is usually now called JavaAppLauncher rather than >JavaApplicationStub. Almost there. Along with their personal version of Java 1.6 and very own >software bundler device, Apple also utilized their own tips/tags within >Details.plist that are various from those utilized by Oracle. Thus in the brand-new >application package I acquired to transpose the tips/tags from the authentic >Information.plist into the new one.
Find >>>>Of particular importance for me had been that I previously pointed to my regional >ij.jar using the ‘ClassPath' essential/tag, and today I include a line label to >JVMOptions with contents ‘-cp' (where ‘cp' stands for class route) and >after that the following string label under JVMOptions is certainly the actual route to my ij.container, >e.gary the gadget guy. homedir/ImageJ/ij.container >Thankfully the plugin.dir and storage settings tags are usually the exact same as before. >>In summary, Apple created it'beds own Coffee and program bundler that utilized >distinctive Info.plist keywords, but Apple company stopped performing therefore with Java 1.6x. >Presently if you require new Coffee versions you'll have got to perform very much of the work >yourself to develop the package deal.
Unfortunately Coffee 1.7 and higher will not >run on devices running Macintosh OS X10.6 and lower, so for compatibility you'd >require to stay with Apple company's Coffee 1.6. >Eventually this will all have to get proved helpful out in the major ImageJ and/or >Fiji bundles, but for me I have got my work-around.
I do not yet know how >ij.container centered on java 1.7x will run on MS Windows-based Computers. >>>Walter U'Dell, PhD >Assistant Professor >Dept. Light Oncology >McKnight Mind lnst. Rm LG-177 >PO Box 100385 >UF Health Cancer Middle >University of Arizona >Gainesville, Florida 32610 >>352-273-9030 >>>>>>- >ImageJ mailing listing: >- When I has been 12 I thought I would live forever. So far, therefore good. ImageJ posting list. Hello there Walter, thank you for the comprehensive account!
Simply rapidly (because I have little period this 7 days) to clarify the Fiji/ImageJ2 circumstance: On Mon, 7 Jul 2014, Walter U'Dell had written: >Eventually this will all have got to obtain worked out in the main ImageJ >and/or Fiji packages, but for me I have my work-around. I do not however understand >how ij.jar centered on java 1.7x will run on Master of science Windows-based Personal computers. You probably understand that we perform not use the software bundler and after heading through the challenge you defined, you furthermore know why. We already possess some technique to run with a different Java version: Nevertheless, in my fingers, Coffee 7 had been not as stable on MacOSX. Besides, I have got a MacBook that will be simply too small for MacOSX later on than 10.6, and in particular in the academic environment, I amount I feel not by yourself.
So Coffee 7 is simply out of get to. I would be excited, of program, if you assisted us improve the ImageJ.ápp and Fiji.ápp packages! Ciao, Johannes - ImageJ mailing list.
Hello there Walter, On Tué, 8 Jul 2014, Walter U'Dell published: >thanks for your info. In relation to the deal, last night I forwarded to >Wayne the pack that I ultimately used effectively, after getting >this email from him. >>In situation you find it useful furthermore, I'm content to send out ot on tó you. If yóu >require me to work on a version for Fiji I can consider that (after nowadays's >BRA-GER video game of course), but I don't have much expertise with Fiji. As I directed out, we cannot just force customers to up grade their working system.
So I question that we can simply make use of the application bundler you utilized. It might function for you, but we have got a bigger responsibility than that.:-( Besides, we possess very a bit of program code added to provide backwards-compatibility, including the ability to stipulate the quantity of RAM to book without getting to edit Material/Info.plist, and like assistance to make use of the exact same package deal for 32-bit and for 64-bit.
Ciao, Johannes - ImageJ emailing list. Hello there Johannes, I feel using a Macintosh running OS Back button Yosemite (10.10) with Java jdk 1.7.071 installed. I would including to run Fiji or ImageJ making use of the control supplied at the link in the earlier write-up.
Desktop publishing software for mac. Apple fanchildren always come across as the kind of people who own a car but can't change the oil or a tire. You just have to have some knowledge about PC hardware.
When I perform that, with the command changed for the jdk edition and details of the installation path, I still get the irritating message 'To open 'Fiji' you require to set up the heritage Coffee SE 6 runtime.' Can be the order line method recognized to function properly with Yosemite, or is usually there something else I can attempt? >Hi Johannes, >I have always been making use of a Macintosh working OS X Yosemite (10.10) with Coffee jdk 1.7.071 >installed. I would like to run Fiji or ImageJ making use of the order offered at >the hyperlink in the previous blog post. When I do that, with the control changed for >the jdk version and specifics of the set up route, I nevertheless obtain the >annoying information 'To open 'Fiji' you require to set up the heritage Coffee SE 6 >runtime.'
>>Will be the control line technique recognized to function properly with Yosemite, or can be >presently there >something else I can attempt? >>Karen >>>>- >View this message in circumstance: >>Delivered from the ImageJ mailing list archive at Nabble.com. >>- >ImageJ sending checklist: >- ImageJ sending list.
Items - This Technote identifies the numerous Macintosh-specific runtime attributes that can end up being provided to a Java application operating on Macintosh OS Back button. The attributes vary in function from nourishing required details to a packaged '.app' Coffee software wrapper, to making a Coffee application more Mac-like.
Numerous strategies of indicating these qualities to a given application are also discussed. The details in this Technote is applicable to Coffee development on Macintosh OS Times 10.1.3 or afterwards, with Coffee 1.3.1 Upgrade 1, and the December 2002 Designer Tools versions of Project Creator or MRJAppBuilder. Nov 14 2002 Coffee Application Attributes for Mac pc OS Times Java applications on Mac OS X can end up being supplemented with a number of distinctive runtime attributes to improve their user experience. These attributes can become stipulated via command-Iine, or, in thé case of a packaged '.app' Coffee program, they are typically selected in one of two data files: MRJApp.qualities, and Information.plist. The qualities in issue are described in the dining tables beneath. The 'Default' column in the dining tables signifies the default beliefs that the runtime takes on if no worth is chosen by you when packaging your program. They can end up being assembled into three major categories: needed, graphics, and Macs properties.
Needed Application Properties The qualities shown in Desk 1 need to become existing and legitimately described in order for a '.app' Java application to launch properly. They are needed to resolve the program's major course and locate all of your program's needed libraries. If not really existing, or defined with improper ideals, the Java runtime will likely answer with a number of mistakes on launch. Please take note that these attributes are composed for yóu by defauIt if your software is created in ProjectBuilder.
If you select not really to use Project Creator, you must establish the attributes yourself (see ). These attributes are not necessary if you are usually launching your program using the command-Iine java executable. Necessary application properties. Residence Default Functionality com.apple company.mrj.application.main none of them Specify the fully-qualified class name of the class filled with the application's primary method. Com.apple.mrj.program.classpath none of them Specify file system pathways to all necessary codebases (directories and/or JAR data files). Notice: Find for dictionary equivaIents of these properties using Project Builder.
Program Launch Qualities The qualities outlined in Table 2 allow programmers to utilize conventional command-line startup qualities to Coffee programs on Mac pc OS Back button. Java start properties for Mac pc OS X Property or home Default Function com.apple company.mrj.program.parameters nothing Space-separated checklist of disputes which are parsed to create the Thread approved to main com.apple company.mrj.software.workingdirectory none of them Sets the present working directory website for the program. Com.apple.mrj.software.vm.options none of them Space-separated list of choices to VM (y.g -Xms2m) Notice: Find for dictionary equivaIents of these attributes using Task Creator. Graphical Application Properties Using Hardware Velocity: Under Java 1.3.1 on Macintosh OS Times 10.2 (Jaguar), Hardware Acceleration for Swing and 2D images has ended up allowed by default. If you are usually experiencing issues with visual application functionality or stability on Jaguar, try out disabling hardware speeding by setting up the com.apple.hwaccel key to fake, using one of the methods outlined in this téchnote. To disable equipment speeding permanently:. Log on to.
DownIoad the hwaccelinfotool. Open Airport terminal and type sudo /usr/nearby/bin/hwaccelinfotool (you will become asked for your security password). Enter the returned string into the hwaccelexclude.qualities document inside /Library/Coffee/Home/lib and conserve the document. For use of hardware speed in Mac pc OS Times 10.1.x, make sure you seek advice from the for information on enabling hardware velocity in your Java apps. Any users of 10.1.x are usually strongly persuaded to download the Java 1.3.1 Update 1 bundle for that program via Software program Upgrade.
'Macintosh' Software Properties The properties shown in Desk 4 are usually are all elective, and offer Mac-like or various other common look-and-feel enhancements to your software without any additional code. Attributes runs with an asterisk (.) just have impact when using the Aqua appearance and feel in Golf swing applications. Java Macintosh attributes for Mac pc OS A House Default Functionality com.apple.macos.useScreenMenuBar. fake Puts Swing selections in the Mac pc OS menus bar, if using the Aqua appearance and sense. Java applications produced with Task Contractor will possess this set to genuine com.apple.macos.use-fiIe-dialog-packages fake If established to real, causes java.awt.FileDialog to deal with program (.app) packages and installer (.pkg) packages as documents instead of folders, and will not really allow menu into them.
Notice for JFileChooser equivalents com.apple company.macos.smallTabs. fake If established to correct, dividers will presume a smaller sized font size which in effect will shrink the overall size of each tabs. The Aqua HI Guidelines dictate that dividers should have got two feasible dimensions com.apple.mrj.program.apple.menus.about.title nothing If defined, an 'In relation to.' Command will be added to the top of the software menu, and can end up being detected by joining a com.apple.mrj.AboutHandler. Coffee applications made with Project Designer will possess this set to inital name of your task com.apple.mrj.software.growbox.intrudes genuine Leads to resizable windows grow-bóx to intrude intó AWT/Swing articles (if changed off, base of window is moved down 15 pixels). Com.apple company.mrj.application.live-resize fake Enables reside resizing of home windows. Setting Program Properties The attributes detailed in the table over can end up being implemented in three various ways, depending on the equipment you are usually making use of and the means in which you want to set up the application: using the command-Iine, or, in thé case of a.app product packaging, the MRJApp.properties and Information.plist documents.
How To Edit Info.plist In X Code
For more info on app product packaging beyond the subsequent sections, make sure you send to the area of. Command-Line Performance Mac OS X provides the regular JDK command line equipment for designers.
Therefore, when starting an unpackaged Coffee software from the command collection, the two listed above in Desk 1 should not really be utilized, in favour of the standard command-line standards of the classpath and major class.