[ https://jira.jboss.org/jira/browse/JBIDE-2652?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2652: -------------------------------------------- this seems to happen when I choose "Exploded archive" -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2652?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-2652: --------------------------------------- Attachment: destinationfoobar.png -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2652?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2652: -------------------------------------------- ok, the UI is definitly not listening to the version property and does not handle relative paths. e.g. in version 1.0, use workspace dialog and select current project and it will leave the field empty...that is wrong. and with blank field and filesystem it also resolves the relative path as if the project name is specified... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2652?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-2652. -------------------------------- Resolution: Done resolving as fixed. If max still has a problem with the text field remaining blank he should let me know and we should come up with a suitable alternative. Perhaps the ${archives_current_project} field would be more suitable than a blank, but as this is no longer a blocker, and it is now functional, I am resolving this issue. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2652?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-2652: ------------------------------------ ${archives_current_project} is just a supported variable to reference the current project name. Perhaps in the future it could be used more efficiently when multiple descriptors are allowed and you have a second descriptor stored in proj1/somefolder/someotherfolder/.packages.xml and you still want to reference the current project, but not by name (which was a jira issue requested by users). The ability to reference the current project but not by name was the requirement for ${archives_current_project} As for "." and "", I meant only that if the entire string was equal to "" or "." then it'd mean current project. This made sense as in all cases so far, the descriptors are at the root of the project. In the future when multiple descriptors are allowed, "." and "" may mean just relative to the descriptor (as that behavior has not been defined yet, it certainly won't cause any breakages). But this is not relevent to your example of /pinktowel/build/. as in that case the string is not equal to "." or "". It contains a . but is not equal to . Hope this makes sense. -- 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