Version 3.0

[coolya]

Over the years this plugin has gathered lots of legacy. Parts of the code base still originate from the gradle 5.x era. We have kept lots of the behaviour in-place to ensure backward compatibility. For version 2.0 I think it's time to cut that legacy and not care about breaking changes but try to improve the usage of the plugin.

This issue is used to collect ideas and outline new features we want to add. Feel free to comment your ideas into this issue so that we can discuss them.

Changes planned:

• Usage of gradle properties in all DSL parts the end users write in their build script
• Proper configuration phase handling. No more afterEvaluate and dependency resolving during configuration. e.g. gradle help and gradle tasks shall not download anything
• namespace for the plugins Consider namespaces for plugins: download-jbr -> de.itemis.mps.download-jbr and so on #98
• removal of "generate project libraries" task Consider deprecating and removing GenerateLibrariesXml task #62
• support for MPS 2021.+ only

Festure ideas:

• download JBR: switch from maven dependencies to https://cache-redirector.jetbrains.com/intellij-jbr/ also see JBRResolver
• Rework GitBasedVersioning to handle missing git gracefully. Configuration of the version pattern would be nice as well.
• User JetBrains Maven repository to download MPS. (would require handling the annoying path problem given that the folder in the zip file always contains the MPS version number)

[bkolb]

Have you seen this? https://lp.jetbrains.com/gradle-intellij-plugin/ Maybe this can be helpful as well (would be great if MPS itself would use it...)