- This topic has 10 replies, 2 voices, and was last updated 19 years, 11 months ago by Riyad Kalla.
-
AuthorPosts
-
erikbrownMemberWhen I deploy (and re-deploy) my web project to Tomcat, only a subset of the JARs that are referenced in my project are deployed to the lib directory of my webapp in Tomcat.
I tried selecting all four check boxes under “Library Deployment Policies” in Window->Preferences->MyEclipse->J2EE Project->Web Project->Deployment. This didn’t completely fix the problem. I don’t have any dependent java projects, but I checked “Use Smart Deployment…” anyway.
When I used eclipse to change the libraries that weren’t being deployed to “user libraries”, then MyEclipse would deploy them properly. This is not acceptable though, since I’m using a code generation tool for these libraries. This means that every time I run the codegen tool, I’ll have to go back into eclipse and change these libraries to be user libraries, otherwise they won’t be deployed by MyEclipse. Of course, I don’t want this extra overhead.
It’s almost as though the checkbox for “Jars on web project build-path” in the “Library Deployment Policies” tab isn’t being recognized properly by MyEclipse?
I’m using:
MyEclipse Plug-in 3.8.4+QF2-BetaFor3.1
Eclipse 3.1.0M4
Tomcat 5.5.7
JDK 1.5.0Thanks,
Erik
Riyad KallaMemberErik,
I’m willing to bet anything that this is just a refresh issue… try and run your code gen tool, refresh your project (Right click on root, REFRESH) and then deploy… did it work?This happens with people using Ant and other scripts that gen JARs as well, they forget to refresh and Eclipse isn’t aware of the files so MyEclipse isn’t aware of them either.
erikbrownMemberThis happened even after I closed/re-opened eclipse. So, it leads me to believe that it is not a refresh issue.
Erik
Riyad KallaMemberDid you try refreshing? Actually executing “Refresh”?
erikbrownMemberNo. I hadn’t refreshed the eclipse project (F5) before. So, I went ahead and tried it by going to File->Refresh, by clicking on the project and refreshing, and by also hitting F5. After I re-deployed, in each case, the libraries in question were not copied over 🙁
Same goes for when I closed and re-opened eclipse (as I mentioned before).
Any other ideas?
Riyad KallaMemberWell let’s check the log file for exceptions:
1) Close down MyEclipse
2) Go to <workspace dir>\.metadata and erase the .log file
3) Fire up MyEclipse
4) Deploy your app
5) Now open the new .log file in the .metadata directory and paste the exception here for me to look at.
erikbrownMemberI tried steps 1-5. No .log file was generated. I re-did 1-5 after manually creating .log. No exceptions were generated. I still think it has something to do with how MyEclipse on eclipse 3.1M4 is handling the checkbox for “Jars on web project build-path” in the “Library Deployment Policies” tab.
Suggestions?
Riyad KallaMemberDo these JARs actually live in your WEB-INF/lib directory? Are they external JARs? Are they a User Library? etc
Riyad KallaMemberReply from a PM
They don\’t live in my WEB-INF/lib directory. They are both installed as part of two seperate plug-ins (Jena and Kazuki). The are technically considered to be libraries by eclipse. They are not user libraries. Although, when I do make them user libraries they ARE deployed properly. It\’s just that I figured that MyEclipse would be able to handle these jars even if they are not user libraries.
In Eclipse a “library-looking-thing” is not always a library, and subsequently the code handling those “libraries” is not all the same. We will need to know what kind of container or library these plugins are using for us to support them. As you found out the workdaround is to change them to user libraries OR link them as External JARs in your build path.
erikbrownMemberYeah, the workaround is not as bad as I thought. I originally thought I would have to change these libraries to user libraries constantly, but it doesn’t look like that is the case any more.
I appreciate your support very much.
Riyad KallaMemberYou’re welcome. I am going to close this thread but I have filed an issue for us to look into alternative JAR container deployments so that this may be addressed in a future release.
-
AuthorPosts