[ https://jira.jboss.org/jira/browse/JBIDE-2666?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2666: -------------------------------------------- If I close the project explorer I get this instead and just have project archives view open: java.lang.NullPointerException at org.jboss.ide.eclipse.archives.ui.util.composites.ArchiveSourceDestinationComposite.getTranslatedGlobalPath(ArchiveSourceDestinationComposite.java:277) at org.jboss.ide.eclipse.archives.ui.util.composites.ArchiveSourceDestinationComposite.validateAndUpdateWidgets(ArchiveSourceDestinationComposite.java:235) at org.jboss.ide.eclipse.archives.ui.util.composites.ArchiveSourceDestinationComposite.variablesPressed(ArchiveSourceDestinationComposite.java:154) at org.jboss.ide.eclipse.archives.ui.util.composites.ArchiveSourceDestinationComposite.variablesButtonPressed(ArchiveSourceDestinationComposite.java:143) at org.jboss.ide.eclipse.archives.ui.util.composites.ArchiveSourceDestinationComposite$4.widgetSelected(ArchiveSourceDestinationComposite.java:129) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider.createFileset(ArchivesActionProvider.java:282) at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider.access$1(ArchivesActionProvider.java:279) at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider$2.run(ArchivesActionProvider.java:129) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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-2666?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-2666: ------------------------------------ I know I've made this comment before, but I feel compelled to elaborate on this. I think perhaps I should limit the variable feature to only user-defined variables. The reasons are many, but it basically comes down to that I cannot control what these variables return. It could be completely random. For example, the variable "container_loc" returns hte location of the currently SELECTED container. This means that if you have a fileset using this variable, it will change ALL THE TIME. If you open in an editor Project1/src/File1.java, change it, and then in the outline go select Project2/src/OtherClass.java, then go back and save File1.java, the LAST SELECTED / CURRENTLY SELECTED file is *actually* OtherClass.java. Some of these dynamic variables change themselves based on what was selected. Others change themselves all the time based on anything and everything. In fact, I could program a Dynamic Variable that returns a random container in the workspace, making it pretty much impossible to make this a repeatable build. One of the variables actually OPENS a DIALOG BOX each time it's accessed! (file prompt / folder prompt) However: I have used the variable in your example: ${resource_loc:/Test8} in the creation of a fileset. It worked properly. I'm somewhat curious as to where you're using the full example you've provided ${resource_loc:/projectA/.classpath}, since that does not seem an appropriate variable to use either in the destination of an archive, or the base folder of a fileset. All nodes that I can tell require a folder, not a resource. Where would you be using this variable representing a specific resource? -- 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-2666?page=com.atlassian.jira.plu... ] Rob Stryker reassigned JBIDE-2666: ---------------------------------- Assignee: Rob Stryker -- 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-2666?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-2666. -------------------------------- Resolution: Done I'm resolving this as fixed. It seems they *do* work, completely. The primary issue here is that when creating a fileset or archive directory is to know how each variable resolves themselves. In this case, ${resource_loc:/Project1} resolves to the FULL STRING of the ABSOLUTE location of that resource. Example: Workspace root: ----> /my/workspace Project1 ----> /my/workspace/Project1 (raw variable) ${resource_loc:/Project1} ---> /my/workspace/Project1 (filesystem relative) ${resource_loc:/Project1} -----> /my/workspace/Project1 (workspace relative) ${resource_loc:/Project1} ----> /my/workspace/my/workspace/Project1 The key here is that the variable resolves to an absolute path, not a workspace-relative path. Because dynamic variables can be anything at all, from random numbers to complete garbage to something useful, I cannot be checking every variable to see if its a path, if its workspace relative, or filesystem relative. I feel strongly the warning in the title-area dialog should be warning enough that they might want to change their "workspace-relative" variable to filesystem relative. Fixed. Screenshot attached. -- 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-2666?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2666: -------------------------------------------- Yay! -- 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