You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In our team, we have an Eclipse workspace containing multiple Cucumber projets. All is running fine until an infinite build loop is starting. This loop does not starts at the Eclipse launch but only after a while (we have not identified a specific moment or action which triggers this infinite build loop). Until this infinite loop starts, the workspace is running fine. The inifinte loop can be "killed" by cancelling the task in the progress view of Eclipse but when a file is accessed/modified/saved, the loop starts again. We have to restart Eclipse to end this behavior.
We have found that when the Cucumber plugin configuration "Enable step definitions glue detection" is disabled, we do not have this infinite build loop.
Moreover, when this option is enabled and the infinite loop happens, the "Maven Workspace Build" view show the files target/classes/.cucumber/cucumber.glue.tmp and target/classes/.cucumber/cucumber.stepDefinitions.tmp as the files that trigger the build.
To resume, these files are updated, which then trigger a build, which then update these files, which then trigger the build, which change these files and so on.
To Reproduce
I have tried to reproduce this behavior in another workspace but unfortunately have not succeeded.
Expected behavior
The build should happen only once
Describe the bug
In our team, we have an Eclipse workspace containing multiple Cucumber projets. All is running fine until an infinite build loop is starting. This loop does not starts at the Eclipse launch but only after a while (we have not identified a specific moment or action which triggers this infinite build loop). Until this infinite loop starts, the workspace is running fine. The inifinte loop can be "killed" by cancelling the task in the progress view of Eclipse but when a file is accessed/modified/saved, the loop starts again. We have to restart Eclipse to end this behavior.
We have found that when the Cucumber plugin configuration "Enable step definitions glue detection" is disabled, we do not have this infinite build loop.
Moreover, when this option is enabled and the infinite loop happens, the "Maven Workspace Build" view show the files target/classes/.cucumber/cucumber.glue.tmp and target/classes/.cucumber/cucumber.stepDefinitions.tmp as the files that trigger the build.
To resume, these files are updated, which then trigger a build, which then update these files, which then trigger the build, which change these files and so on.
To Reproduce
I have tried to reproduce this behavior in another workspace but unfortunately have not succeeded.
Expected behavior
The build should happen only once
Desktop
The text was updated successfully, but these errors were encountered: