| Helios bug? - project dependencies [message #718933] |
Thu, 25 August 2011 12:00  |
Eclipse User |
|
|
|
Project A is a Dynamic Web Project.
Project B is a Java Project (or Utility Project) used to contain libraries and their configuration.l
In Ganymede you could set A to depend on B, and A would see B's classes and config files in the classpath. This worked well when writing/compiling, and it worked when running apps on Tomcat.
In Helios this process is broken. If you take the same steps compilation works fine, but when you start Tomcat from within Eclipse to run the webapp A, you get ClassNotFoundException on classes that are in project B.
Yes, we could manually copy the config files into project A's WEB-INF/classes, and copy the exported JAR of project B into WEB-INF/lib, but that is NOT how Eclipse is supposed to work.
It could be a bug, but my guess is that the project dependency model changed from Ganymede to Helios and that we now need to setup project dependencies in a different way. Can someone enlighten me on the new procedure?
|
|
|
| (no subject) [message #718942 is a reply to message #718933] |
Thu, 25 August 2011 12:05  |
| Eclipse User |
|
|
|
On 25-Aug-11 10:00, Bruno Melloni wrote:
> Project A is a Dynamic Web Project.
>
> Project B is a Java Project (or Utility Project) used to contain
> libraries and their configuration.l
>
> In Ganymede you could set A to depend on B, and A would see B's classes
> and config files in the classpath. This worked well when
> writing/compiling, and it worked when running apps on Tomcat.
>
> In Helios this process is broken. If you take the same steps compilation
> works fine, but when you start Tomcat from within Eclipse to run the
> webapp A, you get ClassNotFoundException on classes that are in project B.
>
> Yes, we could manually copy the config files into project A's
> WEB-INF/classes, and copy the exported JAR of project B into
> WEB-INF/lib, but that is NOT how Eclipse is supposed to work.
>
> It could be a bug, but my guess is that the project dependency model
> changed from Ganymede to Helios and that we now need to setup project
> dependencies in a different way. Can someone enlighten me on the new
> procedure?
The Eclipse Deployment Assembly in Helios replaced the old JEE Module
Dependency mechanism (still used in Galileo). Perhaps there's an answer
there? Anyway, I'm betting the Eclipse web tools forum would be a better
place to ask this since Project A is a Dyanamic Web Project.
|
|
|
Powered by
FUDForum. Page generated in 0.09190 seconds
Home