Hi, I want to retire a lot of old and legacy code in the code-coverage-api plugin in order to simplify the development experience (e.g., there are duplicate classes and jelly views). It is difficult for new contributors to start development when they do not know which classes and views are actually still used. Since there might be still some users that use the old and deprecated steps I am wondering how to do that in the best way.
1) Move the old code to a new plugin with new plugin id. Make that new plugin a dependency of the code-coverage-api plugin. Benefits: Everything is out of sight, not-used dependencies can be moved as well. Clean restructuring of the plugin. 2) Move the old code to a different source folder. Maven does support that but I am not sure if our maven-hi plugin does. Benefits: no new plugin is required, but dependencies need to be shared for both parts of the code. 3) Move the old code to a maven sub module in a new folder. Maven does support that but I am not sure if the rest of our build infrastructure does. Or is there even another option that I do not see? My favorite is option 1), but that requires to create a new plugin in the jenkinsci organization. Ulli -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5D44F363-6A45-4430-B82F-581CF815E14B%40gmail.com.
