-
Bug
-
Resolution: Not an Issue
-
P3
-
7.0.0
-
JMC 7.1 Sprint 3, JMC 7.1 Sprint 4, JMC 7.1 Sprint 5
For previous versions of JMC, it was configured to be associated with JFR recordings.
This was done in the Info.plist, and looked like this:
<key>CFBundleDocumentTypes</key> <array> <dict> <key>CFBundleTypeName</key> <string>Java Flight Recording</string> <key>CFBundleTypeIconFile</key> <string>jmc.icns</string> <key>CFBundleTypeRole</key> <string>Viewer</string> <key>LSHandlerRank</key> <string>Owner</string> <key>LSItemContentTypes</key> <array> <string>com.oracle.java.flightrecording</string> </array> </dict> </array> <key>UTExportedTypeDeclarations</key> <array> <dict> <key>UTTypeConformsTo</key> <array> <string>public.data</string> <string>public.content</string> </array> <key>UTTypeDescription</key> <string>Java Flight Recording</string> <key>UTTypeIconFile</key> <string>jmc.icns</string> <key>UTTypeIdentifier</key> <string>com.oracle.java.flightrecording</string> <key>UTTypeReferenceURL</key> <string>http://docs.oracle.com/javase/7/docs/technotes/guides/jfr/</string> <key>UTTypeTagSpecification</key> <dict> <key>public.filename-extension</key> <array> <string>jfr</string> </array> </dict> </dict> </array>
When fixing JMC-5891, this was too complex for the Maven plug-in used to alter the Info.plist, so need to figure out some other way to get this in.
In old JMC build system, there was a separate Info.plist that was copied into the build in a post-processing step. See also JMC-5840