[
https://jira.jboss.org/jira/browse/JBIDE-6024?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-6024:
--------------------------------------
I found one exact scenario to replicate it:
1. EXECUTE: Create Seam Web Project in EAR deploymen
2. EXECUTE: Find created EAR project in server view, select it and invoke "Full
Publish" from context menu
3. ASSERT: That application starts without errors and available in browser
4. EXECUTE: Stop Server
4. EXECUTE: Restart eclipse
4. EXECUTE: Expand created seam project in server view
4. ASSERT: Only server item in tree has state in square brackets and it [ Stopped ]
5. ASSERT: All other items have no additional text in square brackets after node label
6. EXECUTE: Open WebContent/login.xhtml, add new line somewhere in text and save it.
7. EXECUTE: Wait until Server state in square brackets is changed to [ Stopped, Republish
]
8. ASSERT: Seam Web module under server has status [ Republish ]
9. EXECUTE: Start server
10. ASSERT: There are no errors in server console related to created project
check your workspace
.metadata/.plugins/org.jboss.ide.eclipse.as.core/${ServerName}1267822848903/deploy/${seamProjectName}-ear.ear/${seamProjectName}.war
folder. It should contains the only file that was changed on step 6.
JBoss AS adapter deploys only recently changed files and removes
everithing else
---------------------------------------------------------------------------------
Key: JBIDE-6024
URL:
https://jira.jboss.org/jira/browse/JBIDE-6024
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Environment: JBoss Tools 3.1.0.GA candidate v201003050540R-H56-GA
Reporter: Denis Golovin
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.1.1
The steps to replicate the issue are explained in this post
http://community.jboss.org/message/526847#526847.
I cannot confirm yet but it looks like problem should be replicated for any project after
couple hours of waiting.
I was able to get the same problems after I tried to change ad deploy files after 4
hours. Now it happens every time even after restoring deployment with Full Publish action
in Servers View
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira