May I also suggest the following pattern for future release consideration?
Maven'like / semver.org : using X.Y.Z
* The netbeans "product" would be X.Y with any value for Z being 100%
compatible with X.Y
* Thus an executable netbeans jar of netbeans-x.y.z.jar and maybe
netbeans-x.y.jar which wraps and executes the newest x.y.z.jar
available (maybe downloading it from the netbeans site for auto-upgrade
* the executable JAR would be the slim netbeans application framework
with the following unremovable plugins:
- plugin manager
- plugin for 'distributions' like
: ee
: base
: php
: the different setups as the old netbeans.org
* Each distribution specifies a set of plugins
- each plugin has an x.y.z
If needed, netbeans...jar and each plugin...jar may be basically a BOM
(bill of materials) that contains required JAR files (think of a FAT
JAR, shade, or SpringBoot executable JAR)
Thank you, Frederick Bloom
hanasaki
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
