[
https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17724:
-------------------------------------
[~pdecat] You are aware that if the module does not restart, your changes to the utility
project will not be picked up by the server, correct? With that in mind, I'm curious
what would be the benefit here of NOT restarting the module. Users such as yourself would
then complain that the module was republished, but your changes to the utility jar are not
in effect on the server.
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-b
Fix For: 4.2.0.Beta3, 4.2.0.CR1
Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip
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)