Closed paleozogt closed 2 years ago
Yes the goal is that all the tasks can be used directly. For xcodebuild this works, and the goal is that this can be done will all tasks.
Ah, I didn't know you were already headed in that direction. :)
Is there a branch I can test on and provide feedback?
I have an XCode project with multiple targets. With 0.15.5, it seems that I can use the
XCodeBuildTask
directly, which is pretty convenient:However, doing the same with archive or package doesn't work:
It always archives the same thing no matter what
target
is set to.Digging into the code, it seems like the
XcodeBuildArchiveTask
is always looking inproject.xcodebuild
for parameters (such asproject.xcodebuild.applicationBundle
) which means that no matter how we parameterize the task it will only ever use the default from the mainxcodebuild
DSL.It's great that these tasks look to the
xcodebuild
DSL for defaults, but the tasks should be more modular and allow for directly inputting parameters (likeXcodeBuildTask
does).