That might be implemented using tycho application packaging or PDE build features.
It would let us:
- have any number of JBDS distribution we want (for WEB, SOA and etc development);
- simplified installer build, because build script would just create installer from JBDS distribution and EAP;
- no meta info generation during installation required;
- have only one way to launch JBDS using jbds.exe/jbds/jbds.app platform dependent launcher.
- change root feature from Eclipse Platform to JBDS and make JBDS real eclipse based product;
- trigger update for jbds by updating JBDS feature version;
- control list of available update sites in preferences.
- blocks
-
JBDS-1382 No obvious icon is present to launch JBDS after installation on Mac
-
- Closed
-
-
JBDS-976 JBDS does not have a branded icon on Mac OS X
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
