Bom pom with dependencymanagement section would be an addition to clusters. Clusters have actual dependencies in them.
So we may have regeneration of clusters and bom per release and update with "human understandable" name. We need a way to prevent regenerating existing version specification. Start to make sense :D Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : lundi 13 juillet 2020 12:05 À : dev <[email protected]> Objet : Re: Apache NetBeans 12.0-u1is available for testing. On Mon, 13 Jul 2020 at 10:52, Eric Barboni <[email protected]> wrote: > I'm not sure to understand what is the BOM approach, ... > Upgrading with spec version, > you have to look each entry, map the spec version to the > release you want. (IDE tool needed) maven version plugin can help > getting only last version. (20 changes to do) Exactly, the BOMs could be like current cluster files, but with modules under dependency management rather than dependencies (eg. as in https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html) That way you'd have one or more BOM for version RELEASE-120-1 with all the modules and their spec versions in it, and the correct versions would be picked up everywhere used. But it will likely need some UI changes in the IDE. The BOM would be the mapping you're talking about between platform version and spec version? Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
