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.

Sign up for GitHub

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

Jump to bottom

Add support for reachability analysis of DI-container-managed code #6

Open
pettermahlen opened this issue Jun 11, 2015 · 1 comment
Open

Add support for reachability analysis of DI-container-managed code #6

pettermahlen opened this issue Jun 11, 2015 · 1 comment
Labels
enhancement

Comments

@pettermahlen
Copy link
Member

This could involve things like scanning classes (in all classpath entries) for @Inject annotations and implementations of Provider. See http://atinject.googlecode.com/svn/trunk/javadoc/javax/inject/package-summary.html for a description of JSR-330 (which is really very hard to find on the internets).
@pettermahlen
Copy link
Member Author

From @mattnworb:

@petter: I like your idea for @Inject etc. Another simple workaround in addition could be to allow the user to specify additional classes to include in the reachable part, i.e. apollo.HttpServerModule

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pettermahlen