[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2666) Project archives does not seem to work with eclipse variables with arguments

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-2666:
--------------------------------------------

Just because some of the variables are non-related does not mean you shouldn't be allowed to use them. I don't buy that argument - user variables can change too.

If you don't like the variables evaluating constantly then cache the results for each package (not globally for all packages), but Im not sure that is needed since most usage of these would specify a parameter to avoid the full dynamacity.

About your question a folder is also a resource - I was just using .classpath as an example.

> Project archives does not seem to work with eclipse variables with arguments
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-2666
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2666
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 3.0.0.alpha
>            Reporter: Max Rydahl Andersen
>             Fix For: 3.0.0.beta1
>
>
> Trying to use ${resource_loc:/projectA/.classpath} resulted in below stacktrace and the text field just ended up being ${resource_loc} 
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> 	at org.eclipse.swt.SWT.error(SWT.java:3777)
> 	at org.eclipse.swt.SWT.error(SWT.java:3695)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> 	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)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.ide.eclipse.archives.ui.providers.ArchivesContentProviderDelegate.shouldRefreshProject(ArchivesContentProviderDelegate.java:117)
> 	at org.jboss.ide.eclipse.archives.ui.providers.ArchivesContentProviderDelegate$1$1.run(ArchivesContentProviderDelegate.java:101)
> 	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
> 	... 22 more

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