Skip to content
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

Mark DetectMojo goal with thread safety info #42

Closed
seime opened this issue Nov 4, 2019 · 4 comments
Closed

Mark DetectMojo goal with thread safety info #42

seime opened this issue Nov 4, 2019 · 4 comments
Milestone

Comments

@seime
Copy link

seime commented Nov 4, 2019

DetectMojo should be marked with thread safety information - or big warning is shown during parallel builds

[WARNING] *****************************************************************
[WARNING] * Your build is requesting parallel execution, but project      *
[WARNING] * contains the following plugin(s) that have goals not marked   *
[WARNING] * as @threadSafe to support parallel building.                  *
[WARNING] * While this /may/ work fine, please look for plugin updates    *
[WARNING] * and/or request plugins be made thread-safe.                   *
[WARNING] * If reporting an issue, report it against the plugin in        *
[WARNING] * question, not against maven-core                              *
[WARNING] *****************************************************************
[WARNING] The following plugins are not marked @threadSafe in XXX : 
[WARNING] kr.motd.maven:os-maven-plugin:1.6.2
[WARNING] Enable debug to see more precisely which goals are not marked @threadSafe.
[WARNING] *****************************************************************
@trustin
Copy link
Owner

trustin commented Nov 7, 2019

Thanks for reporting. Are you interested in sending a pull request?

@seime
Copy link
Author

seime commented Apr 28, 2020

@trustin PR submitted by team member :)

@trustin trustin closed this as completed May 23, 2020
@trustin trustin added this to the 1.7.0 milestone May 23, 2020
@uweschaefer
Copy link

@trustin i apologize for coming off as pushy, as you obviously are a busy man.
However: Are there any plans on when to release 1.7.0? There seem to be no issues left assigned to the milestone and this fix would certainly be appreciated 😆

@trustin
Copy link
Owner

trustin commented Aug 6, 2020

@uweschaefer I'm very sorry for not releasing a new version. Let me try some time this week. 🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants