Community
Participate
Working Groups
The UI seems a bit inconsistent in terms of the usage of the first '/' being used in the Deployment Assembly page. There is two way that I see people can add jars into their WEB applications: 1. By directly adding it to the Web Project ------------------------------------------------------- In this case the Deployment Assembly page allows for adding the reference with a '/' or without it. 2. By indirectly adding it to the Web project, by adding it to the EAR level ----------------------------------------------- When it is added into the EAR, the reference goes into the manifest of the Web project and the Deployment Assembly page doesn't allow to edit this entry. This references contains a '/' and can't be edited. The '/' at the begging may not mean much but we should be consistent in terms of how the UI behaves and what can be specified, if one doesn't allow to edit it and always have the /, then the other scenario should do the same.
Assigning to Chuck for initial investigation.
Was this affected at all by recent Deployment Assembly work?
Not that I am aware. It has been there from since the new page is there.
I believe Bug 331044 fixed the '/' inconsistency. The Deploy Path column in the Deployment Assembly page now always shows paths as relative. A lot of changes have gone into the Deployment Assembly page since this bug was opened. Please update to the latest WTP version and let us know if you still see any of the inconsistencies that you mentioned.
Resolving bug since inconsistency issues have been fixed.