Skip to content

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

@dst97

Description

@dst97

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestsemver:majorA major change breaking backwards compatibilitysize:LThis can be dealt with in 2-3 weeks

    Type

    No type

    Projects

    Status

    In Progress: v0.7

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions