[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-975) Project Archives created WAR file contain duplicated libs

[ http://jira.jboss.com/jira/browse/JBIDE-975?page=comments#action_12379904 ] Viacheslav Kabanovich commented on JBIDE-975: --------------------------------------------- I found following problems in plugins org.jboss.ide.eclipse.archives.core and org.jboss.ide.eclipse.archives.ui: 1) New Archive -> WAR wizard presets 3 file-sets (second page): lib, classes, WebContent. If libraries are located in WebContent/WEB-INF/lib, then file-set 'lib' is subset of file-set 'WebContent', but 'WebContent' does not excludes *.jar files. This alone makes jar files to be copied twice to the war. I think that it is safe to preset property excludes=**/WEB-INF/lib/*.jar for file-set 'WebContent'. Anyway, user has opportunity to edit file sets in Project Archives view. Though, it would be nice to have opportunity to modify file sets already in New WAR wizard, because if by some reason the preset structure is not appropriate, user still has to finish wizard resulting in a wrong war. 2) File-set 'lib' has as source the project root folder. It may be what is needed, to collect all *.jar files in project, however the problem is that method ModelTruezipBridge.getFiles(IPath[], IArchiveFileSet) that calculates destination paths for war entries, always keeps relative path of filtered file to source folder which explains paths like /WEB-INF/lib/WebContent/WEB-INF/lib/x.jar. The second problem can be solved in different ways: a) add property 'flat' to IArchiveFileSet, so that if it is true, only file names without relative path to source will be appended to destination root; b) modify source in preset file-set 'lib' to be actual lib folder instead of project root. I am committing changes to org.jboss.ide.eclipse.as.core.extensions.archives.WarArchiveType: 1) Setting excludes pattern "**/WEB-INF/lib/*.jar" to 'WebContent' file-set. 2) Setting source of 'lib' file-set to %project%/%WebContent%/WEB-INF/lib. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira