[
https://jira.jboss.org/jira/browse/JBIDE-2693?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-2693.
--------------------------------
Fix Version/s: 3.0.0.beta1
Resolution: Done
Assignee: Rob Stryker
Resolved with changes.
To verify:
EXECUTE: create a project
EXECUTE: create a package (com.test), and a few files (a.txt, b.txt inside the
package)
EXECUTE: create a project archives for this file
EXECUTE: create a fileset under this archive (** as includes, **/*.jar as excludes)
EXECUTE: right-click on the archive and deploy it to a jboss server (make sure all
boxes in the wizard are checked, always deploy, automatically deploy)
EXECUTE: create a new file
VERIFY: jar file in the workspace contains the new file you just added
VERIFY: jar file in the server deploy folder contains the new file you just added
Deploying of project archives modules buggy
-------------------------------------------
Key: JBIDE-2693
URL:
https://jira.jboss.org/jira/browse/JBIDE-2693
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.0.alpha
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.0.0.beta1
Project archives and its automatic build worked decently, however, file additions or
removals were not represented immediately without a full build. In the Deployable
archive, the same was true.
The issue stems from the fileset caches not being updated at the correct time (at all,
previously only on model changes)
--
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