| Dependent jars not published to Tomcat [message #729732] |
Mon, 26 September 2011 17:05  |
Eclipse User |
|
|
|
I have a large workspace with multiple projects which all go into a web application project. These projects reference large numbers of dependent JARs from various sources, all under the control of Maven.
I recently moved from Eclipse Galileo to Eclipse Indigo and now my Tomcat installation is not receiving any of the dependent JAR files which are supposed to be published into WEB-INF/lib. I only see the three or four JAR files from my projects, not the hundred-plus other JARs that this app needs to run.
Anyone know why this might be?
|
|
|
|
|
| Re: Dependent jars not published to Tomcat [message #730131 is a reply to message #729747] |
Tue, 27 September 2011 12:55  |
| Eclipse User |
|
|
|
On 9/26/2011 5:58 PM, Tom wrote:
> Thanks for the reply!
>
> Sorry, I probably should have provided some more detail initially. Yes,
> this is a workspace which uses both M2E and WTP plugins. It builds the
> WAR file just fine outside of Eclipse using Maven 3.0.3, which is the
> same installation of Maven that I have my Eclipse pointed to. All of the
> problems seem limited to the Eclipse-Tomcat relationship.
>
> I am using M2E Plugin 1.0.0 and WTP plugin 3.3.1, and Tomcat 6.0.32.
>
> This all seemed to work fine under Galileo with M2E .12 and whatever WTP
> plugin I was using then, so I suspect it's something in the new
> environment I have not set up correctly.
There were some changes that occurred in WTP going from Galileo to
Helios that might affect this. Most visible is that the J2EE Module
Dependencies properties page got replaced with a Deployment Assembly
page. Is this project one that migrated from Galileo to Indigo? In your
Markers or Problems (sorted by Type) view, do you see "Classpath
Dependency Validator Message" warnings? Finally, is the project in
Eclipse a single Dynamic Web Project with just direct dependencies on
the jars, or are there also some Utility projects the web project
depends on and those project have dependencies on jars that need to make
their way into the webapp?
Cheers,
Larry
|
|
|
| Re: Dependent jars not published to Tomcat [message #730220 is a reply to message #730131] |
Tue, 27 September 2011 19:00 |
| Eclipse User |
|
|
|
Yes, I remember seeing the classpath dependency errors, so that was one of the problems.
I managed to solve most of the problems by doing what I considered a fairly desperate move: I deleted all the projects from Eclipse, deleted the .project, .classpath and .settings folder contents from each project, and imported them back into my workspace. Going through that process cleared out most of the gremlins.
|
|
|
Powered by
FUDForum. Page generated in 0.05729 seconds
Home