Hi, I will soon call a vote to release nb-repository-plugin that allow to change the targeted repository for populating. We used snapshot version for 11.2 release of artefacts.
Then, I would like to refactor the maven utilities (archetype, nb-repository-plugin, nbm-maven-plugin,...) in one repo to be able to vote for all at once instead of seven artefacts and have same version for all. I have a non-clear opinion for now. I have the following workflow issue: Harness artefacts need a released NetBeans artefacts on maven central. Suppose, we have a nbm-plugin (version A) used in the wizard in NetBeans that use harness done with RELEASE112. Harness is changing because any reason, it's not possible to prepare a new nbm plugin You need to wait for NetBeans 11.3 to be released and the RELEASE113 to be publish At this time you can create nbm-plugin (version B) to use RELEASE113 harness but this will not be proposed in the wizard. (Only manual version bump can help) Maybe we should make the wizard scan for last version of the plugin instead of hardcoding it. (Don't have to wait for release +1 to get new, just a few day until plugin is deployed) This strategy may also applied to the maven archetype. Any idea welcome. Best Regards Eric --------------------------------------------------------------------- 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
