The new build system is very cool and a lot faster, so that's great ☺!

However I just had a small stratego error, I tried to import a non-existing module after renaming some file.

The error I got:

11:05 | INFO  | o.m.s.e.m.b.PreJavaBuilder     - Building language project eclipse:///metac
11:05 | INFO  | Build log                      - Incrementally rebuild inconsistent units
11:05 | ERROR | Build log                      - Required builder failed. Error occurred in build step "Compile Stratego code": no rebuild of failing builder
11:05 | INFO  | Build log                      - Failing builder was required by "Generate sources".
11:05 | ERROR | o.m.s.e.m.b.Builder            - Cannot build language project eclipse:///metac; build failed unexpectedly
build.pluto.builder.RequiredBuilderFailed: Required builder failed. Error occurred in build step "Compile Stratego code": no rebuild of failing builder
	at build.pluto.builder.RequiredBuilderFailed.getCause(RequiredBuilderFailed.java:37) ~[na:na]
	at build.pluto.builder.BuildManager.requireInitially(BuildManager.java:253) ~[na:na]
	at build.pluto.builder.BuildManagers.build(BuildManagers.java:62) ~[na:na]
	at org.metaborg.spoofax.meta.core.SpoofaxMetaBuilder.plutoBuild(SpoofaxMetaBuilder.java:159) ~[na:na]
	at org.metaborg.spoofax.meta.core.SpoofaxMetaBuilder.compilePreJava(SpoofaxMetaBuilder.java:117) ~[na:na]
	at org.metaborg.spoofax.eclipse.meta.build.PreJavaBuilder$1.run(PreJavaBuilder.java:55) ~[na:na]
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.metaborg.spoofax.eclipse.meta.build.PreJavaBuilder.build(PreJavaBuilder.java:67) ~[na:na]
	at org.metaborg.spoofax.eclipse.meta.build.Builder.build(Builder.java:46) ~[na:na]
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) [org.eclipse.equinox.common_3.7.0.v20150402-1709.jar:na]
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) [org.eclipse.equinox.common_3.7.0.v20150402-1709.jar:na]
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:486) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:405) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.ui.actions.BuildAction$1.runInWorkspace(BuildAction.java:287) [org.eclipse.ui.ide_3.11.0.v20150825-2158.jar:na]
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) [org.eclipse.core.resources_3.10.1.v20150725-1910.jar:na]
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) [org.eclipse.core.jobs_3.7.0.v20150330-2103.jar:na]

This tells me something in my code was wrong somewhere, but doesn't help me identify the problem, which could make it very hard to fix the error.

Submitted by Arian on 4 January 2016 at 11:14

On 4 January 2016 at 11:19 Gabriël Konat commented:

In a previous build, it should have given you information about the error. It won't re-run a failed Stratego compilation when there are no changes ("no rebuild of failing builder"). If you clean, it should tell you what went wrong. This behavior can be kind of annoying though, I'll have a look if we can re-run failing builders without changes anyway.


On 4 January 2016 at 11:25 Arian commented:

Ah, yes I see. It's there indeed. Maybe it can be made a bit more user friendly.


On 14 January 2016 at 15:27 Gabriël Konat commented:

There is a better explanation now. I've cleaned up the build log a lot, it now only shows an exception when something in the build really throws an exception.


On 14 January 2016 at 15:27 Gabriël Konat closed this issue.

Log in to post comments