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

[Rob Stryker (JIRA)]

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

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? 



> 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