On Tue, 29 Oct 2019 at 15:53, Eric Barboni <[email protected]> wrote: > You cannot do a RELEASE112.1 in the > org.netbeans(api,modules,clusters,external) without rebuild the whole > NetBeans stack because every pom will need the RELEASE112.1 version on > dependencies nbm being a side artefacts. > It's not possible to overwrite a released artefacts you cannot do a > RELEASE112 again.
Yes, I know artefacts can't be overwritten, so thought as much. Kind of makes it even harder to push a patch release for Maven modules. Would be good if that was not the case, but I guess it's not a short term (ie. 11.2 update) mechanism. And Maven probably won't get nb-javac module fix, although that's probably not that much of an issue. Still think it worth considering longer term. Means only one set of NBMs need signing and maintaining, and may remove some issues around using Apache mirrors for the UCs. How feasible is changing the modules to use spec version and RELEASE11X just for overarching POM files? 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
