[
https://issues.jboss.org/browse/JBIDE-20476?page=com.atlassian.jira.plugi...
]
The Alchemist commented on JBIDE-20476:
---------------------------------------
Thanks, [~rob.stryker]. I'm on Mac OS X 10.10.5, BTW.
I have a bit more information, as I was just able to reproduce it:
* My WF 8.2 Server is set to "use workspace metadata"
* My WF 9.0.1 Server is set to "use the JBoss deploy folder"
1. I had disabled "Build Automatically" in Eclipse and built my project in Maven
from the command line.
2. Forgetting to re-check "Build Automatically", I clicked on Synchronize, which
produced the "File may be locked" errors.
3. After checking "Build Automatically", some Maven auto-generated files were
still missing, so I Cleaned my projects.
4. Still, Synchronize gave some errors, so I Removed the modules from the WF 8.2 Server,
and then Publish gave no errors.
Very strange and I don't think I'll be able to produce a small project to
reproduce it. I was just hoping it was an easy fix.
"File may be locked" warning if EAR is deployed to multiple
Servers
-------------------------------------------------------------------
Key: JBIDE-20476
URL:
https://issues.jboss.org/browse/JBIDE-20476
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Beta2
Environment: Eclipse Mars
Reporter: The Alchemist
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.3.x
I have multiple Server's in my Eclipse:
* Wildfly 8.2
* Wildfly 9.0.1
I have my application (two EARs) deployed to both of them, but when I try to Publish my
changes, it complains in the Eclipse error log that some files might be locked so the
publish was not completely successful.
Perhaps I shouldn't have the same EARs in two apps?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)