[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3411 at 4/24/15 8:36 PM: -------------------------------------------------------------- I found better and simpler solution. Instead of renaming $\{target-dir\}/studio and have a bunch of changes in installer, I just changed where product is materialized under Mac OS X. In attached PR p2.director target dir is changed from $\{target-dir\}/studio to $\{target-dir\}/studio/jbdevstudio.app. That solution has all the benefits: 1. jbdevstudio.app location doesn't change; 2. jbdevstudio.app has the same structure as Eclipse.app and it is normal Mac OS X application package that contains all Eclipse artifacts (plug-ins, features and etc) inside; 3. jbdevstudio.ini is in right location and is not ignored anymore (BDS-3410 is fixed). The only drawback(?) tycho 0.23.0-SNAPSHOT should be used in jbdevstudio-product build. There are several unnecessary .png and .ico files but that is a different issue. was (Author: dgolovin): I found better and simpler solution. Instead of renaming ${target-dir}/studio and have a bunch of changes in installer, I just changed where product is materialized under Mac OS X. In attached PR p2.director target dir is changed from ${target-dir}/studio to ${target-dir}/studio/jbdevstudio.app. That solution has all the benefits: 1. jbdevstudio.app location doesn't change; 2. jbdevstudio.app has the same structure as Eclipse.app and it is normal Mac OS X application package that contains all Eclipse artifacts (plug-ins, features and etc) inside; 3. jbdevstudio.ini is in right location and is not ignored anymore (BDS-3410 is fixed). The only drawback(?) tycho 0.23.0-SNAPSHOT should be used in jbdevstudio-product build. There are several unnecessary .png and .ico files but that is a different issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)