There are other IDEs that enable showWhatIsNewPageAfterUpdate option, so it's better to reuse the implementation.
GitOrigin-RevId: 64aa54c0a088f920d00c09d7c0eca09861b3b553
...as a replacement for 'show-on-update' attribute in 'whatsnew' tag in ApplicationInfo.xml
IntelliJ IDEA has been migrated to use the new property.
GitOrigin-RevId: 13f502c36c30b971f028d732e3c67202cb11c11c
The logic which constructs the full URL is moved to ExternalProductResourceUrls's implementations, allowing third-party IDEs to have their own schemas of URLs for context help.
IntelliJ IDEA has been migrated to use the new property.
GitOrigin-RevId: b57b021c07eb84fdd0dd968e057100156a646fb1
...instead of using 'productUrl' in *ApplicationInfo.xml. Third-party IDEs can organize their sites differently, so it's better not to suppose that URLs of their download pages always end with '/download'.
Now this convention is specified for JetBrains' IDEs only in BaseJetBrainsExternalProductResourceUrls.
IntelliJ IDEA has been migrated to use the new property.
GitOrigin-RevId: 366569f01a8ad84094bc600692774c31d8e3eff2
IntelliJ IDEA Community and Ultimate are migrated to use the new approach. Since other JetBrains IDEs didn't use this feature, and the corresponding method wasn't part of public API, no fallback implementation in LegacyExternalProductResourceUrls is provided.
GitOrigin-RevId: a50912b65d4fc44a3fcf7e59d615092c0372b581
It appears that IDEA Community and Ultimate use the same external URLs, so it doesn't make to have two different implementations of ExternalProductResourceUrls for them. So intellij.idea.customization.base module is introduced to define the common IntelliJIdeaExternalResourceUrls implementation.
GitOrigin-RevId: 997596458fb391b7033e11a9c15851e72cfeaef1
