robross0606

the `gradle.plugin` artifacts are the real artifacts for this plugin. They are tied together by the parent POM: ``` +--- com.palantir.git-version:com.palantir.git-version.gradle.plugin:0.12.0-rc2 | \--- gradle.plugin.com.palantir.gradle.gitversion:gradle-git-version:0.12.0-rc2 | +--- org.eclipse.jgit:org.eclipse.jgit:4.5.4.201711221230-r | | +---...

I'm now thoroughly confused. I switched over to the old-style buildscript declaration and now I"m getting failures attempting to pull your plugin as a dependency. Apparently, this URL no longer...

Ahh, looks this one exists instead: https://plugins.gradle.org/m2/com/lazan/dependency-export/com.lazan.dependency-export.gradle.plugin/0.5/ Your readme instructions have a slight typo in the old-style buildscript declaration. This: ``` dependencies { classpath "com.lazan:gradle-dependency-export:0.5" } ``` needs to be...

I'm totally lost with the differences in how these plugins are deployed and represented on the servers, depending upon whether the syntax is the old or new style. In the...

Yep, that's where I got the correct syntax. This is different than what you have in your readme which was the first confusing part. The new style syntax also doesn't...

This did not work either. The problem is that the JAR files under /gradle/plugin/ in your export do not have an associated POM file in the export. ``` +---gradle |...

The POM files *are* available on the public server: https://plugins.gradle.org/m2/gradle/plugin/com/lazan/gradle-dependency-export/0.5/gradle-dependency-export-0.5.pom They're just not being exported by your plugin.

Yes, it is very confusing. I'm not familiar with it myself, but looks to me almost like this is an adaptation to move forward with the new-style syntax while still...

Not great, but an idea. I'll give it a try.

The suggested syntax didn't work at all. You get: `Could not find method poms() for arguments [gradle.plugin.com.lazan:gradle-dependency-export:0.5@pom] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.` It doesn't like the use of `poms` instead...