-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0 - migration plugin should say if something is wrong #1630
Comments
That text is just a general warning. Indeed, it should list/highlight deprecated properties and problems from your 1.x build file. Not quite sure what the problem is without an actual sample and expected vs actual. |
As far as I'm concerned, just use any IJ plugin built with IntelliJ Platform Gradle Plugin 1 and try to use |
@YannCebron Any hints on how to get this migration plugin to get to work would be appreciated. |
@YannCebron Can you reproduce this with my hints? The issue blocks me from migrating, please support. |
If it helps, I'll provide a sample @hsz |
Please provide all logs, and your setup so I could verify what exactly issues you face. |
@hsz In a new trial, I was able to figure out all necessary changes without using the migration plugin. |
Describe the need of your request
Using plugin id("org.jetbrains.intellij.platform.migration") version "2.0.0-beta3"
It always says:
But it doesn't say what's wrong with my build.
Proposed solution
The migration plugin should enumerate what's wrong or, if everything is okay, it should say it found no issue.
Alternatives you've considered
No response
Additional context
I am not using publishPlugin and signPlugin, only patchPluginXml. For this last one, I found no documentation about this. We have documentation for plugin v1 https://plugins.jetbrains.com/docs/intellij/tools-gradle-intellij-plugin.html#tasks-patchpluginxml, but how to migrate patchPluginXml to plugin v2 (if needed, I have no idea)? I can package my plugin with success. I guess the migration plugin simply found no issue, but I'm not sure.
The text was updated successfully, but these errors were encountered: