Home » Modeling » Epsilon » [Patch] Exclude /org.eclipse.epsilon.workflow/bin from runtime Eclipse application classpath(Minor bugfix for a regression in the Ant tasks when running Epsilon from source in Eclipse Helios)
| [Patch] Exclude /org.eclipse.epsilon.workflow/bin from runtime Eclipse application classpath [message #638104] |
Tue, 09 November 2010 22:48  |
|
Hi everyone,
Today, I decided to (finally!) upgrade to Helios my 3-workspace setup for Epsilon. I like to stay on the bleeding edge, so I keep a workspace with the latest revision of the Epsilon source code. From there, I run a second workspace with my metamodels, which hosts a third workspace where I try out the editors.
I noticed that my Ant tasks were not working anymore in this setup (they did just fine in Eclipse Galileo), but they worked if I installed Epsilon from its update site or the Marketplace. After some debugging, I found out that the classloader used to load the LoadModel Ant task was different from the Ant classloader. After pulling out some hairs over the rest of the day, I stumbled over this page:
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/ant_contributing_task.htm
I checked the various guidelines and surely enough, the org.eclipse.epsilon.workflow project did not have its bin/ output folder excluded from the runtime classpath while running runtime Eclipse applications. I just had to uncheck the folder in the "Plugin Development -> Runtime Classpath" page of the project's properties, and everything works like a charm again.
In case you're interested, I have pasted an equivalent patch at the end of this message. It's quite trivial, so I didn't think it would merit a proper bug report. If you need it anyway, just ask  .
Cheers,
Antonio
diff --git a/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse.pde.core.prefs b/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse.pde.core.prefs
index 344553d..b0e7d06 100644
--- a/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse.pde.core.prefs
+++ b/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse.pde.core.prefs
@@ -1,3 +1,4 @@
-#Wed Feb 21 12:24:26 GMT 2007
-eclipse.preferences.version=1
-resolve.requirebundle=false
+#Tue Nov 09 23:26:41 CET 2010
+eclipse.preferences.version=1
+resolve.requirebundle=false
+selfhosting.binExcludes=/org.eclipse.epsilon.workflow/bin
[Updated on: Tue, 09 November 2010 22:48] Report message to a moderator |
|
|
| Re: [Patch] Exclude /org.eclipse.epsilon.workflow/bin from runtime Eclipse application classpath [message #638186 is a reply to message #638104] |
Wed, 10 November 2010 09:57  |
 Dimitrios Kolovos
Messages: 1776
Registered: July 2009 |
Senior Member |
|
|
Hi Antonio,
Many thanks for investigating and letting us know! We'll apply this
patch and commit to the SVN shortly.
Cheers,
Dimitris
Antonio García wrote:
> Hi everyone,
>
> Today, I decided to (finally!) upgrade to Helios my 3-workspace setup
> for Epsilon. I like to stay on the bleeding edge, so I keep a workspace
> with the latest revision of the Epsilon source code. From there, I run a
> second workspace with my metamodels, which hosts a third workspace where
> I try out the editors.
>
> I noticed that my Ant tasks were not working anymore in this setup (they
> did just fine in Eclipse Galileo), but they worked if I installed
> Epsilon from its update site or the Marketplace. After some debugging, I
> found out that the classloader used to load the LoadModel Ant task was
> different from the Ant classloader. After pulling out some hairs over
> the rest of the day, I stumbled over this page:
>
> http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/ant_contributing_task.htm
>
>
> I checked the various guidelines and surely enough, the
> org.eclipse.epsilon.workflow project did not have its bin/ output folder
> excluded from the runtime classpath while running runtime Eclipse
> applications. I just had to uncheck the folder in the "Plugin
> Development -> Runtime Classpth" page of the project's properties, and
> everything works like a charm again.
>
> In case you're interested, I have pasted an equivalent patch at the end
> of this message. It's quite trivial, so I didn't think it would merit a
> proper bug report. If you need it anyway, just ask :).
>
> Cheers,
> Antonio
>
>
> diff --git
> a/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse .pde.core.prefs
> b/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse .pde.core.prefs
> index 344553d..b0e7d06 100644
> ---
> a/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse .pde.core.prefs
> +++
> b/plugins/org.eclipse.epsilon.workflow/.settings/org.eclipse .pde.core.prefs
> @@ -1,3 +1,4 @@
> -#Wed Feb 21 12:24:26 GMT 2007
> -eclipse.preferences.version=1
> -resolve.requirebundle=false
> +#Tue Nov 09 23:26:41 CET 2010
> +eclipse.preferences.version=1
> +resolve.requirebundle=false
> +selfhosting.binExcludes=/org.eclipse.epsilon.workflow/bin
>
|
|
| | | |
| Re: [Patch] Exclude /org.eclipse.epsilon.workflow/bin from runtime Eclipse application classpath [message #661616 is a reply to message #657986] |
Fri, 25 March 2011 15:07 |
Steffen Zschaler
Messages: 266
Registered: July 2009 |
Senior Member |
|
|
Hi Louis,
I am sorry to report that I still seem to be having problems with this.
I have updated from SVN, but when I try to run a workflow, I get the
following error trace:
> !SESSION 2011-03-25 15:03:16.659
> -----------------------------------------------
> eclipse.buildId=M20110210-1200 java.version=1.6.0_22 java.vendor=Sun
> Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32,
> NL=en_GB Framework arguments: -product org.eclipse.platform.ide
> Command-line arguments: -product org.eclipse.platform.ide -data
> D:\workspaces\epsilon/../bla -dev
> file:D:/workspaces/epsilon/.metadata/.plugins/org.eclipse.pd e.core/bla/dev.properties
> -os win32 -ws win32 -arch x86 -consoleLog !ENTRY
> org.eclipse.ant.launching 4 0 2011-03-25 15:03:29.873 !MESSAGE Failure
> of Background Ant Build !STACK 1
> org.eclipse.core.runtime.CoreException:
> D:\workspaces\bla\foo\workflow\build.xml:50:
> java.lang.NullPointerException at
> org.eclipse.ant.core.AntRunner.handleInvocationTargetExcepti on(AntRunner.java:452)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:384) at
> org.eclipse.ant.internal.launching.launchConfigurations.AntL aunchDelegate$1.run(AntLaunchDelegate.java:298)
> at java.lang.Thread.run(Unknown Source) Caused by:
> D:\workspaces\bla\foo\workflow\build.xml:50:
> java.lang.NullPointerException at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:116)
> at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:15 4) at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> 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.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348) at
> org.apache.tools.ant.Target.execute(Target.java:357) at
> org.apache.tools.ant.Target.performTasks(Target.java:385) at
> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1337)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1306 ) at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
> at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
> at org.apache.tools.ant.Project.executeTargets(Project.java:118 9) at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:662)
> at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:495)
> 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.ant.core.AntRunner.run(AntRunner.java:378) ... 2 more
> Caused by: java.lang.NullPointerException at
> org.eclipse.epsilon.workflow.tasks.EpsilonTask.getProjectRep ository(EpsilonTask.java:86)
> at
> org.eclipse.epsilon.workflow.tasks.emf.LoadModel.executeImpl (LoadModel.java:39)
> at
> org.eclipse.epsilon.workflow.tasks.EpsilonTask.execute(Epsil onTask.java:40)
> 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.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:106)
> ... 24 more
I actually seem to be getting this twice.
Any suggestions?
Steffen
On 04/03/2011 19:38, Louis Rose wrote:
> Hi Antonio, Dimitris,
>
> Thanks for fixing this! I've just stumbled onto this bug too, and an
> update from SVN fixed the problem.
>
> I thought it was worth adding that, on my machine at least, the
> problem was confusingly reported as a NullPointerException in
> EpsilonTask#getProjectRepository(). Calls to getProject() from
> EpsilonTask were returning null.
>
> Cheers,
> Louis.
|
|
|
Goto Forum:
Current Time: Sat Apr 27 01:38:47 GMT 2024
Powered by FUDForum. Page generated in 1.03266 seconds |
] 
Search
Help
Register
Login
Home
