I am writing an application in Eclipse, that has a servlet, and an android component. There are common classes to both so, being a bit of noob, I have moved the common classes into a new project to centralise the common code.
I then reference the common classes in my servlet and the android project by including the "common class" project in the build path for each. I do not get any compile errors as a result of using the, now centralised, common classes.
My concern is the impact on the servlet. When deploying the jar for the servlet, I merely export all my .class files and push it onto the server. Will the common classes project be automatically included now that I have included an additional project as well ?
If you have better ideas or best practice architecting common classes/multi-project builds, I am also interested to hear.