Vendordep Templating.

[thenetworkgrinch]

Outputs filled out vendordep file to $buildDir/repos/ with filled in variables from the gradle config.

[rzblue]

It would be better to generate this as an artifact that gets published

[thenetworkgrinch]

Like this? I am not sure how to add it to MavenPublication. I tried doing

vendordep(MavenPublication) {
                artifact vendordepJson

                artifactId = "${baseArtifactId}-vendordep"
                groupId artifactGroupId
                version pubVersion
            }

but it didnt recognize the artifact type as valid even though it outputs a file.

[thenetworkgrinch]

I just made a zip task which wraps up the generated vendordep and is able to publish it to maven.

I still dont think this is necessary or a good idea? Why would you want to publish your vendordep to maven when its supposed to be hosted and accessible?

The current version where it outputs the vendordep to $buildDir seems fine and really would be better off if it outputted to $buildDir/repos. That way vendors can copy $buildDir/repos over to their webhost and have it be done.

[ThadHouse]

On lines 172 and 177 of build.gradle, add addTaskToCopyAllOutputs(vendordepJsonZip) and build.dependsOn vendordepJsonZip