- This topic has 3 replies, 2 voices, and was last updated 19 years, 7 months ago by
.
-
Posts
-
I am using Eclipse 3.0.1 & MyEclipse 3.8.4
When you have a web project which depends on classes in another web project, and you have the deployment settings set to deploy jar files or classes into when you deploy your web project, the dependency doesn’t get deployed. If I change the dependency so it is a standard java project, it does get deployed. Seems like classes in a dependency project should get deployed regardless of the type of project it is.
davis,
Your findings are correct, common core libraries must be plain Java projects. The reason we don’t support web project dependencies is because it opens an entire black box of how to “combine” two web projects together where everyone’s definition and use case will be slightly different. For you, it’s just the classes. For another user it’s some of the JSPs, for another user, it’s only the newest web.xml file and any libraries that do not match, etc… since there is no spec for this and no other IDE we know of support this, we decided to do as much as we would where the spec was clear (combining Web + Java project) but left the corner cases up to Ant scripts where users needed them and could write them their selves depending on each unique environment.I guess the problem is that it doesn’t really tell you why it is not working, so if you forget that this is the behavior, you can really pull your hair out trying to figure out why the dependency isn’t deploying. Perhaps a warning when you select a web project as a dependency?
I guess the problem is that it doesn’t really tell you why it is not working, so if you forget that this is the behavior, you can really pull your hair out trying to figure out why the dependency isn’t deploying. Perhaps a warning when you select a web project as a dependency?
Agreed, we should have nailed this last time around, I’m sorry for the trouble.
