This message was deleted.
# plugin-developments
Slackbot
12/19/2023, 2:12 PMThis message was deleted.
j
Javi
12/19/2023, 3:06 PMoutputs can be used outside of Gradle.
For example Dokka generates docs in a specific output which you need to know in order to be able to upload to a hosting
m
Martin
12/19/2023, 3:07 PMYou can still know from the task name, the task name is kind of public API
j
Javi
12/19/2023, 3:08 PMYou mean autogenerating the output path based on task name and so on?
m
Martin
12/19/2023, 3:08 PMyep
Martin
12/19/2023, 3:08 PMI get the "historical reasons" so it'll have to be progressive but if I'm writing a new plugin, I'd love to have Gradle allocate something for me
j
Javi
12/19/2023, 3:09 PMif one task can get the outputs of other tasks I don’t think specifying manually that path is relevant
Javi
12/19/2023, 3:09 PMfor me it is a good idea to remove that
plus1 1
Javi
12/19/2023, 3:10 PMIndeed it should help to non file outputs as Gradle implementation should write those outputs somehow in a file which is not indicated by the user to recover them later
Javi
12/19/2023, 3:10 PMSo it would be a good moment to unify that behavior is that is on the roadmap
m
Martin
12/19/2023, 3:11 PMnon file outputsThis was one of my question actually. Is it possible to have
StringMartin
12/19/2023, 3:11 PMFrom reading the documentation only, I wasn't 100% clear
j
Javi
12/19/2023, 3:11 PMI think there is an open issue about that so I think it is not possible
👍 1
m
Martin
12/19/2023, 3:12 PMMakes sense 👍
v
Vampire
12/19/2023, 3:13 PMThere is no way to auto-select an output path.
You could do something like
layout.buildDirectory.dir(task.name)m
Martin
12/19/2023, 3:14 PMI can do it manually but nothing beats something enforced by Gradle so that no one is ever tempted to overlap with my outputs.
Martin
12/19/2023, 3:14 PMOr at least not without violating/ignoring some warnings 😄
v
Vampire
12/19/2023, 3:15 PMIt could always happen, but at least newer Gradle versions detect such overlapping outputs, for example if you have task A with output to A task B which also outputs to A and task C which uses task A output as input, then Gradle will complain that C uses output of B wihtout an ordering constraing.
Vampire
12/19/2023, 3:16 PMIn Gradle 7 that was a deprecation warning, in Gradle 8 it is a hard failure
m
Martin
12/19/2023, 3:17 PMAgreed, I'm coming here from Gradle 8 failures actually. Just feels like this should be enforced before runtime
Martin
12/19/2023, 3:17 PMAlso makes it easier to develop plugin, feels like having a default location for outputs is a win in all cases
v
Vampire
12/19/2023, 3:46 PMFeel free to open a feature request for it if there is none yet. 🙂
👍 1
m
Martin
12/19/2023, 3:54 PMp
Pedro Lamarão
12/19/2023, 11:06 PMSome tasks must differentiate their output by some runtime variable. I have developed tasks that generate native code, and those tasks output path were something like "${task.name}/${task.target}/${project.name}.ext"
m
Martin
12/19/2023, 11:54 PM@Pedro Lamarão not sure I follow. Make the runtime variable an input and re-generate the output when it changes?
Martin
12/19/2023, 11:56 PMOr do you need to archive the outputs of different runs?
Martin
12/19/2023, 11:57 PMI guess there could be "advanced" use cases similar to
createTempFilep
Pedro Lamarão
12/19/2023, 11:57 PMYes, in my case, it is very convenient to have both outputs present. One may archive or publish them all at together.
👍 1
5 Views