You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The flow tool prohibits uploading of multiple artifacts that are created during the build process. Under specific cases uploading multiple artifacts should be allowed.
A single build of a maven/gradle project can produce multiple jar files. It is very common for the source files and the javadocs to be packaged as jar files and uploaded to a maven repository. These jar files include a classifier after the version number. The main application/library jar file does not does not contain a classifier. An example can be found here: Central Repository - Spring Core.
Update the logic for publishing build artifacts for java projects to include all files that specify a classifier along with the file with no classifier. The list of classifiers that should be published should be added to buildConfig.json at artifactoryConfig.artifact(ory?)Classifiers. The artifact that gets deployed should be the file that contains no classifiers. The check for a single artifact for deployment can still be done, but after the files with classifiers have been filtered out.
Pattern for filenames (for each classifier, when classifier(s) provided): "{projectInfo.name}-{version}{'-' + classifier}.{artifactoryConfig.artifactType}"
Pattern for filename when classifiers not provided (existing logic): "{projectInfo.name}-{version}.{artifactoryConfig.artifactType}"
The text was updated successfully, but these errors were encountered:
Problem:
The flow tool prohibits uploading of multiple artifacts that are created during the build process. Under specific cases uploading multiple artifacts should be allowed.
A single build of a maven/gradle project can produce multiple jar files. It is very common for the source files and the javadocs to be packaged as jar files and uploaded to a maven repository. These jar files include a classifier after the version number. The main application/library jar file does not does not contain a classifier. An example can be found here: Central Repository - Spring Core.
The classifier can be any arbitrary string.
Proposal:
Update the logic for publishing build artifacts for java projects to include all files that specify a classifier along with the file with no classifier. The list of classifiers that should be published should be added to buildConfig.json at
artifactoryConfig.artifact(ory?)Classifiers
. The artifact that gets deployed should be the file that contains no classifiers. The check for a single artifact for deployment can still be done, but after the files with classifiers have been filtered out.Example buildConfig.json:
List of files published:
The file that is deployed:
Pattern for filenames (for each classifier, when classifier(s) provided):
"{projectInfo.name}-{version}{'-' + classifier}.{artifactoryConfig.artifactType}"
Pattern for filename when classifiers not provided (existing logic):
"{projectInfo.name}-{version}.{artifactoryConfig.artifactType}"
The text was updated successfully, but these errors were encountered: