[
https://issues.jboss.org/browse/JBIDE-14697?page=com.atlassian.jira.plugi...
]
Rastislav Wagner commented on JBIDE-14697:
------------------------------------------
I tried the steps above with a little modification to be sure what's happening:
STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java ->
Build Path -> User Libraries)
STEP: add some external JARs to myLib1, leave myLib2 empty
STEP: create project with archives support
STEP: create some archive in the project
STEP: add new user library fileset in the archive (myLib1)
STEP: deploy archive on AS/EAP (I used EAP 6.1)
ASSERT: myLib1 is deplyed on server, I can see it in deployments folder and the deployed
JAR contains added external libraries
STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset
STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it
FAIL: there is still myLib1 in archives explorer, not myLib2 as it should be
STEP: deploy archive
ASSERT: myLib1 is now renamed to myLib2
ASSERT: check deployments folder and the content of deployed JAR
FAIL: content of deployed JAR should be empty (because myLib2 is empty) but it contains
myLib1 jars
So there are some UI issues but not just them.
User library fileset cannot be modified
---------------------------------------
Key: JBIDE-14697
URL:
https://issues.jboss.org/browse/JBIDE-14697
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: archives
Affects Versions: 4.1.0.Beta1
Reporter: Jaroslav Jankovič
Assignee: Rastislav Wagner
Fix For: 4.2.0.Beta2
STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java ->
Build Path -> User Libraries)
STEP: create project with archives support
STEP: create some archive in the project
STEP: add new user library fileset in the archive (myLib1)
STEP: select myLib1 in archives explorer, invoke its context menu and select Edit
fileset
STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it
FAIL: there is still myLib in archives explorer, not myLib2 as it should be
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira