[
https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-17724:
---------------------------------------------
[~clerum] "with some jar deps brought in by maven" - that is what i'm
curious about here.
Does the exploded directory have any *.jar files in it ?
if yes - can you tell me which jars (simplest just point a github repo with the project
;)
My *guess* is that one of those jars has metadata that makes wtp see it as a EE dependency
and somehow (haven't found where yet) that triggers constant copying instead of only
copy when actually changed.
If this is the case you can actually go into the server, double click it and change the
Applicaiton reload behavior.
Check the "Customize application reload behavior..." and remove the \.jar$ part
and put \.xxx$ instead
Then it should not do the re-deploys (assuming you dont have any .xxx file endings ;)
Changes cause full redeployment of exploded WAR
-----------------------------------------------
Key: JBIDE-17724
URL:
https://issues.jboss.org/browse/JBIDE-17724
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Environment: Windows 8.1 x64
Java 7u51 x64
Luna x64
Reporter: Cody Lerum
Priority: Blocker
Fix For: 4.2.0.Beta3, 4.2.0.CR1
After moving to Luna from Kepler any changes to java or jsf resources are causing a full
redeployment of the exploded war to JBoss 7.1.3.Final
This prevents any updating of JSF resources or debugging java code.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)