-
Notifications
You must be signed in to change notification settings - Fork 114
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
Ignore maven-remote-resources-plugin:bundle goal #4
Conversation
m2eclipse does not know how to map the maven-remote-resources-plugin:bundle goal, which causes a warning on project import
I'm not that enthusiast about adding such stuff in m2e. Efforts would rather be directed towards the "offending" Maven plugins to work better inside Eclipse IDE (and other incremental builders) https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html |
I can understand that. Without having looking into it, I suspect it would be quite a lot more work, though, and the current situation - the warning which, to me at least, makes m2e "look broken/incomplete" - definitely feels suboptimal for users. I agree that this change doesn't "fix" the underlying issue, but I think it would at least create a better user experience, especially since m2e already skips some goals (although I'm not aware of the underlying reasons for that, which may be different). |
I can understand that. Without having looking into it, I suspect it would be quite a lot more work, though, and the current situation - the warning - definitely feels suboptimal to users. I agree that this change doesn't "fix" the underlying issue, but I think it would at least create a better user experience, especially since m2e already skips some goals (although I'm not aware of the underlying reasons for that, which may be different). |
3 similar comments
I can understand that. Without having looking into it, I suspect it would be quite a lot more work, though, and the current situation - the warning - definitely feels suboptimal to users. I agree that this change doesn't "fix" the underlying issue, but I think it would at least create a better user experience, especially since m2e already skips some goals (although I'm not aware of the underlying reasons for that, which may be different). |
I can understand that. Without having looking into it, I suspect it would be quite a lot more work, though, and the current situation - the warning - definitely feels suboptimal to users. I agree that this change doesn't "fix" the underlying issue, but I think it would at least create a better user experience, especially since m2e already skips some goals (although I'm not aware of the underlying reasons for that, which may be different). |
I can understand that. Without having looking into it, I suspect it would be quite a lot more work, though, and the current situation - the warning - definitely feels suboptimal to users. I agree that this change doesn't "fix" the underlying issue, but I think it would at least create a better user experience, especially since m2e already skips some goals (although I'm not aware of the underlying reasons for that, which may be different). |
m2eclipse does not know how to map the maven-remote-resources-plugin:bundle goal, which causes a warning on project import
Since the more common "process" goal is already ignored, it would seem useful to ignore this goal too.