[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2652) Archives dialog/model gets foobared very easily

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12425624#action_12425624 ] 

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. 

> Archives dialog/model gets foobared very easily
> -----------------------------------------------
>
>                 Key: JBIDE-2652
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2652
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 3.0.0.alpha
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.0.0.alpha
>
>         Attachments: destinationfoobar.png
>
>
> See screenshot....
> Last timeI edited this archive the destination folder was blank and set to relative to workspace...now it is some weird concrete path which I *never* set and when I generate it actually generates into this directory !?
> Im setting this as blocker since it happens to me constantly and it messes up users filesystem!

-- 
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