Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

[[sec:publishing_custom_artifacts_to_maven]]
== Adding custom artifacts to a publication

--
Instead of thinking in terms of artifacts, you should embrace the variant aware model of Gradle.
It is expected that a single module may need multiple artifacts.

          <association>
            <type>String</type>
            <multiplicity>*</multiplicity>
          </association>
          <description><![CDATA[Restricts the classes/resources from the current artifact's CoreExtension class realm that are exposed. Values ending with ".*" expose all classes/resources which are directly contained in the given package in binary form. 

                      }.artifacts.resolvedArtifacts.map { artifacts ->
                          artifacts.collect { it.id }
                      }
                )
                outputFile = layout.buildDirectory.file('ids.txt')
            }
        '''

        when:
        configurationCacheRun ':printArtifactIds', '-s'

    @Nullable
    String getClassifier();

    /**
     * Specifies if the artifact already embeds its own dependencies.
     * This is the case for JEE packages or similar artifacts such as
     * WARs, EARs, etc.
     *
     * @return if the artifact's dependencies are included in the artifact
     */
    boolean isIncludesDependencies();

    /**