Hide
Currently the model is:
1) I want to use some type X
2) hunt down the jar with the thing in that you need
3) add it to the project dependencies (.classpath/maven pom/build.gradle)
4) start using the types within it.
For many kinds of project some of the jars *you might want* is known. E.g. a spring project or a boot project. Under this jira I'm proposing a generally applicable eclipse feature where eclipse is aware of some set of jars that you might want to add to your project. When asking for content assist there is a category for types from these jars, if you *do* select those types you get the jar automatically added to your dependencies (intelligently updating .classpath/pom or gradle file).
The set of jars a project can use in this way may depend on a projects nature.
The particular use case I have in mind is Spring Boot where there are a number of starters provided. Through simple content assist for types in those jars, your project automatically pulls in the starters it needs.
Show
Currently the model is:
1) I want to use some type X
2) hunt down the jar with the thing in that you need
3) add it to the project dependencies (.classpath/maven pom/build.gradle)
4) start using the types within it.
For many kinds of project some of the jars *you might want* is known. E.g. a spring project or a boot project. Under this jira I'm proposing a generally applicable eclipse feature where eclipse is aware of some set of jars that you might want to add to your project. When asking for content assist there is a category for types from these jars, if you *do* select those types you get the jar automatically added to your dependencies (intelligently updating .classpath/pom or gradle file).
The set of jars a project can use in this way may depend on a projects nature.
The particular use case I have in mind is Spring Boot where there are a number of starters provided. Through simple content assist for types in those jars, your project automatically pulls in the starters it needs.
Improvement
Minor
