Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64005

Please add documentation for all parameters of the nexus-artifact-uploader plugin

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Jenkins ver. 2.205
      nexus artifact updater plugin version 2.13

      Several parameters are missing documentation.
      E.g. GroupID has no documentation at all. It appears to be used to create a hierarchy in the target repository. This is useful information to show to the user. If there is no dot (.) in the groupId no upload appears to happen at all. Such a requirement should be documented as well.

       

      ArtifactId is another parameter that has no documentation at all.

       

      The documentation for `Classifier` says "Classifier of the artifact." Unfortunately that does not explain anything to me.

          [JENKINS-64005] Please add documentation for all parameters of the nexus-artifact-uploader plugin

          Logan Mzz added a comment -

          Logan Mzz added a comment - bram_mertens  Classifier is a component of Maven coordinates system. See https://books.sonatype.com/mvnex-book/reference/simple-project-sect-simple-core.html#simple-project-sect-maven-coordinates  

          Bram Mertens added a comment -

          loganmzz: thanks for that link. That explains "Classifier" in a maven context.

          However the plugin page specifically says "This plugin goal is to upload artifacts generated from non-maven projects to Nexus" and "Uploading maven artifacts snapshots is not supported by this plugin.".

          Bram Mertens added a comment - loganmzz : thanks for that link. That explains "Classifier" in a maven context. However the plugin page specifically says "This plugin goal is to upload artifacts generated from non-maven projects to Nexus" and "Uploading maven artifacts snapshots is not supported by this plugin.".

          Logan Mzz added a comment - - edited

          non-maven projects includes "Maven-related" dependency resolvers (Ivy, Gradle, etc.).

          Basically pathes are resolved this way in "Maven-related" dependency management : ${groupIdPath}/${artifactIdPath}/${version}/${artifactId}-${version}-${classifier}.${ext}

          Notes: 

          • "*Path" means dots (".") are replaced by path separator ("/")
          • "-${classifier}" suffix is optional and not used if classifier is empty/not specified
          • "${ext}" depends on artifact type. In most cases its same but can differ for non-canonical type (e.g. tar.gz, tgz, ...)

          Logan Mzz added a comment - - edited non-maven projects includes "Maven-related" dependency resolvers (Ivy, Gradle, etc.). Basically pathes are resolved this way in "Maven-related" dependency management : ${groupIdPath}/${artifactIdPath}/${version}/${artifactId}- ${version} -${classifier}.${ext } Notes:  "*Path" means dots ( "." ) are replaced by path separator ( "/" ) "-${classifier}" suffix is optional and not used if classifier is empty/not specified "${ext}" depends on artifact type. In most cases its same but can differ for non-canonical type (e.g. tar.gz , tgz , ...)

            pskumar448 Suresh Kumar
            bram_mertens Bram Mertens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: