I am working on the conversion of an existing Ant/file build infrastructure towards a Gradle/Artifactory infrastructure. But I am having troubles with a multi-project multi-artifact configuration.
My root project basically comprises a configuration project with configuration injection. Subprojects work with a shared source directory and have to be linked against platform-specific API’s. Therefore, I would like to reuse the classifier attribute to indicate to which API version it was build. I am also using external tooling to create platform specific builds, for which no gradle plugins exist (yet). I can easily re-use this tooling by making use of ant and the gradle-ant integration structure, which works great by the way. I am especially pleased with the possibility of setting Ant classpaths with Gradle configurations which provides a seamless integration path, with gradle dependency management as a bonus!
I can build my root project and generate multiple artifacts attached to it, however only the root pom is published when I deploy to artifactory using uploadArchives. I want to generate a seperate pom for each extra artifact with a custom maven classifier, because the code is the same, but the platform API’s vary. There was a wiki entry that describes pom filtering, but the maven classifier attribute is just not recognised.
I can see in the APIDocs that the PomModel doesn’t export the classifier attribute, so how can I achieve this?