Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use JavaExec instead of DefaultTask for Gradle Task grader{Private,Public}Run #159

Open
dst97 opened this issue Nov 7, 2022 · 0 comments
Labels
feature request semver:major A major change breaking backwards compatibility size:L This can be dealt with in 2-3 weeks
Milestone

Comments

@dst97
Copy link
Contributor

dst97 commented Nov 7, 2022

Currently, class GraderRunTask is using DefaultTask as basic class.

In IntelliJ, when a DefaultTask is started, gradle uses resources from the IDE. Especially, gradle does not create a new process. It is very likely that this behavior results in the following issues:

  • On the one side, the process running the gradle task terminates only when the IDE is terminates. This might be the reason for overflowing heap space which is an known issue.
  • On the other side, the process of the IDE does not allow to create java agents at runtime. This can be explicitly allowed for JavaExec gradle tasks.

Using JavaExec instead of DefaultTask might solve these issues.

@alexstaeding alexstaeding added size:L This can be dealt with in 2-3 weeks bug semver:major A major change breaking backwards compatibility feature request and removed bug labels Nov 10, 2022
@alexstaeding alexstaeding moved this to In Progress: v0.7 in Jagr Development Fall 2022 Nov 10, 2022
@alexstaeding alexstaeding added this to the v0.7 milestone Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request semver:major A major change breaking backwards compatibility size:L This can be dealt with in 2-3 weeks
Projects
Status: In Progress: v0.7
Development

No branches or pull requests

2 participants