wooga / atlas-unity

90%

master: 52%

LAST BUILD ON BRANCH PR-52

branch: PR-52

CHANGE BRANCH

x

Reset

• PR-52
• master
• PR-35
• PR-37
• PR-40
• PR-41
• PR-42
• PR-43
• PR-45
• PR-46
• PR-47
• PR-48
• PR-49
• PR-54
• PR-53
• PR-55
• PR-59
• PR-60
• PR-61
• PR-64
• PR-62
• PR-65
• PR-66
• PR-67
• PR-69
• PR-72
• PR-73
• PR-74
• PR-75
• PR-76
• PR-77
• PR-79
• PR-80
• PR-81
• PR-82
• PR-83
• PR-84
• PR-86
• PR-87
• PR-91
• release/2.x
• PR-93
• PR-94
• PR-96
• PR-97
• PR-98
• PR-99
• PR-100
• PR-101
• PR-102
• PR-104
• PR-106
• PR-107
• PR-92
• PR-95
• PR-109
• PR-108
• PR-110
• PR-111
• PR-112
• PR-113
• PR-115
• PR-116
• PR-118
• PR-119
• PR-121
• PR-122
• PR-123
• PR-124
• PR-125
• PR-126
• PR-127
• PR-128
• PR-129
• PR-131
• PR-132
• PR-133
• PR-134
• PR-135
• PR-138
• PR-137
• PR-139
• PR-140
• PR-141
• PR-136
• PR-142
• PR-143
• PR-144
• PR-146
• PR-147
• PR-148
• PR-150
• PR-151

Fix unity 2019 logfile handling

Description
===========

Unity 2019 changed the behavior of the `-logFile` switch. To print to
`stdout` we must provide `-` as the file path which signals Unity to
print the log to `stdout`. This behavior works also on windows now so I
enabled the logoutput on windows when the Unity version is >= 2019.

Most of the test setup is very brittle at the moment. The tests don't
run with a real Unity installation because of setup and runtime
considerations. The way I path the unity version for tests is not
optimal and will change in the future.

To execute the version check for all batchmode actions, I added a
`protected` getter to fetch the Unity version beeing executed. I still
use the `ArtifactVersion` object but I have plans to change this in the
future and make this part of the public API.

Changes
=======

![FIX] ![UNITY] 2019 logfile handling
![ADD] [unity-version-manager-jni] as dependency to fetch the Unity version

[unity-version-manager-jni]:    https://github.com/wooga/unity-version-manager-jni