Java EE dependencies not added to lib [message #515035] |
Wed, 17 February 2010 09:28  |
Eclipse User |
|
|
|
Hi,
I have a web project that references some other Jars on the build path. I've gone into the project properties --> Java EE Module Dependcies, it also relies on a utility project. I check the utility project and the jars required. When I publish, it only copies the utility project but not the other jars selected. This seems like it may be a bug but I'm not sure if I'm missing something here.
I'm using Ganymede version 3.4.2, build M20090211-1700
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Java EE dependencies not added to lib [message #520289 is a reply to message #520227] |
Thu, 11 March 2010 14:48  |
Eclipse User |
|
|
|
Matt Rossner wrote:
> Actually, looks like I just copy/pasted the wrong file. The settings
> file is like this:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="IbeeCommon">
> <wb-resource deploy-path="/" source-path="/src"/>
> </wb-module>
> </project-modules>
>
>
> Anyway, I've tried making a new workspace with just a basic
> configuration and sure enough Jars get copied over correctly. I've
> compared all the .classpath and .setting files and I don't really see
> any difference but on my project it just doesn't work.
>
> For a while I'm just using an Ant script to copy the missing jars
> whenever I do a clean on the server but it would be really nice to get
> this working properly.
In this new workspace, import the problem projects, making sure to copy
the projects over to the new workspace. Then see if they misbehave in
the new workspace. The source of the behavior could be something
"odd/corrupt" in the metadata associated with the workspace.
Cheers,
Larry
|
|
|
Powered by
FUDForum. Page generated in 0.04103 seconds