[
https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17724:
-------------------------------------
Rob - if there is no way for wtp to detect #4 has changed and thus #3
need to publish - how does an #1 know it needs to publish when #2 changes ? Or is this the
same problem ?
WTP detects in advance what the situation is for each module and submodule. The problem
is, when it calls me, it only calls one module at a time. So WTP knows in advance that
the utility project has no change, and util2 has changes, but *I* don't know that.
Now, if all 4 projects were exploded, this wouldn't be a problem. I could make no
changes to project 3, and then make changes to project 4. But in this case, project 4
must live inside project 3, which means project 3 must know about the changes in it.
I believe I have utilities somewhere to discover the flags for child modules, or its
burried inside the zip runner... but there *is* a way. It's not impossible. I need to
work on the test cases, though.
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
Assignee: Rob Stryker
Priority: Blocker
Labels: respin-a
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)