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

Don't eagerly instantiate modules loader in plugin #91

Closed
rjrudin opened this issue Apr 17, 2016 · 0 comments
Closed

Don't eagerly instantiate modules loader in plugin #91

rjrudin opened this issue Apr 17, 2016 · 0 comments
Assignees
Milestone

Comments

@rjrudin
Copy link
Contributor

rjrudin commented Apr 17, 2016

Doing so means a custom modules database name won't be used. I also can't find any reason to do this other than for the benefit of WatchTask, as LoadModulesCommand will instantiate the loader if it's not already when that command is executed.

@rjrudin rjrudin self-assigned this Apr 17, 2016
@rjrudin rjrudin added this to the 2.2.0 milestone Apr 17, 2016
rjrudin added a commit that referenced this issue Apr 17, 2016
@rjrudin rjrudin closed this as completed Apr 17, 2016
hansenmc pushed a commit to hansenmc/ml-gradle that referenced this issue Aug 19, 2016
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

1 participant