Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319117 - WTP does not deploy new libraries without restart of eclipse
Summary: WTP does not deploy new libraries without restart of eclipse
Status: CLOSED INVALID
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: jst.server (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Angel Vera CLA
QA Contact: Angel Vera CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-07 08:29 EDT by Jasper Floor CLA
Modified: 2010-11-02 15:16 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jasper Floor CLA 2010-07-07 08:29:24 EDT
I set up a Dynamic Web Project with JSF 1.2 capabilities and jboss 5.1 targeted runtime. When deploying the first time I was missing some jars, a not unexpected result. I added the jars to the classpath and I explicitly set them to deploy unde Java EE Module dependencies. The libraries would not be deployed no matter what I did except for restarting eclipse. 

Of interest possibly is that I also have Jboss Tools installed and Jrebel.

I don't recall ever having this problem before. Up until 6 months ago I worked with MyEclipse but now only with Eclipse for JavaEE and various plugins. Some of my colleagues report having had this problem.
Comment 1 Jasper Floor CLA 2010-07-07 08:32:14 EDT
I should, perhaps, have mentioned that I repeatedly did a full publish, clean, clean & full publish or remove & clean & add & clean & full publish.
Comment 2 Angel Vera CLA 2010-07-14 16:03:37 EDT
It is possible that this is an server adapter issue, but is hard to say with the details that you have given us. 

Try to restart the server as well rather than eclipse, let us know if that works.

There are two JBoss adapter out there one provided by WTP remote server adapters and another one provided by the JBoss tools, not sure which one you are using. If you are using the JBoss tooling is most likely the case you are using their server adapter, they might be familiar with this scenario as well. 

Check in the deployment directory and see if your files are setup correctly. The typical deployment directory is something like ...\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmpXX
the directory name might change depending on how many servers you have.
Comment 3 Angel Vera CLA 2010-08-18 15:26:56 EDT
Any updates?
Comment 4 Angel Vera CLA 2010-11-02 15:16:40 EDT
No response given so far. Closing as part of cleaning effort. Please reopen if this is still an issue and provide more information.