|Linking source vs. Required projects on build path vs. Project sets [message #1090018]
||Mon, 19 August 2013 15:45
| Scott Shipp
Registered: August 2013
I am not a newb to Eclipse by any means. I've actually been using it about 5 years. But there are things about it I experiment with from time to time, but never long enough to really understand them before I am whisked off into some other necessary development task.
There are three functions/concepts in Eclipse that fall into this category which I feel may provide a productivity boost if I were able to master them:
- Link source
- Required projects on build path
- Project sets
Can anyone explain the difference between each of these and how they might work together? I know they are all different things and not just options that are alike, but I am not sure why I would use any of them. I check out my projects from source control, and I use Maven to install them into the local repository. Once the main project's dependencies are installed this way, the main project compiles just fine. So it seems like Maven manages things just fine and maybe I don't need these features.
I occasionally want to look at the source from another project and get a message that the source is not linked so I just hit Ctrl+Shift+R and open the file in question. I have gone into build configuration and linked source before, which then allows me to hit F3 and get the declaration to open, but I am not sure if this is a huge gain in any way. I've also assigned three or more projects to a "Project Set" which doesn't seem to gain me anything, either, except now I can close/open three projects at once. There is a help entry for project sets that talks about sharing with others on the team; that might be useful. Finally, I don't ever use "required projects on the build path" window in the build configuration.
What am I missing?
Powered by FUDForum
. Page generated in 0.03129 seconds