You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jira-importer (via GitHub)" <gi...@apache.org> on 2025/04/02 07:00:03 UTC

[I] [MDEPLOY-27] Improper build number after deploying a snapshot of maven-javadoc-plugin [maven-deploy-plugin]

jira-importer opened a new issue, #218:
URL: https://github.com/apache/maven-deploy-plugin/issues/218

   **[Thorsten Scherler](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=thorsten)** opened **[MDEPLOY-27](https://issues.apache.org/jira/browse/MDEPLOY-27?redirect=false)** and commented
   
   I'm trying to use the beta-4 snapshot of the maven-javadoc-plugin and wanted to deploy it on my local maven proxy. The plugin is deployed via:
   
   $ mvn compile jar:jar
   (lots of messages)
   
   $ cd target
   $ mvn deploy:deploy-file -DrepositoryId=bender -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
   (lots of messages)
   
   The plugin jar gets copied to the proxy, and so far everything seems to be fine. In another project, I added the following lines to my pom.xml:
   
   \<build>
   \<plugins>
   \<plugin>
   \<groupId>org.apache.maven.plugins\</groupId>
   \<artifactId>maven-javadoc-plugin\</artifactId>
   \<version>2.0-beta-4-SNAPSHOT\</version>
   \<configuration>
   \<tag>created\</tag>
   \<maxmemory>256m\</maxmemory>
   \</configuration>
   \</plugin>
   ...
   \</plugins>
   \</build>
   
   Unfortunately the plugin cannot be downloaded from my proxy:
   
   $ mvn clean
   [INFO] Scanning for projects...
   [INFO] ----------------------------------------------------------------------------
   [INFO] Building base Repository
   [INFO]    task-segment: [clean]
   [INFO] ----------------------------------------------------------------------------
   Downloading: http://bender:9999/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.jar
   [INFO] ----------------------------------------------------------------------------
   [ERROR] BUILD ERROR
   [INFO] ----------------------------------------------------------------------------
   [INFO] Failed to resolve artifact.
   
   GroupId: org.apache.maven.plugins
   ArtifactId: maven-javadoc-plugin
   Version: 2.0-beta-4-20060322.180042-2
   
   Reason: Unable to locate resource in repository
   
   org.apache.maven.plugins:maven-javadoc-plugin:maven-plugin:2.0-beta-4-20060322.180042-2
   
   from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   bender (http://bender:9999/repository),
   snapshots-codehaus-org (http://snapshots.maven.codehaus.org/maven2)
   
   which is strange because I just deployed it. I looked into the proxy directories and wondered that the files are named differently:
   
   * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar
   * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.md5
   * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.sha1
   * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom
   * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.md5
   * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.sha1
   
   When I manually rename the -1.jar* files to -2.jar* the plugin is downloadable, and "mvn clean" above will work...
   
   To check the above behaviour I removed the deployed files/directories from my maven proxy and redeployed the javadoc plugin:
   
   $ mvn -X deploy:deploy-file -DrepositoryId=bender -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
   + Error stacktraces are turned on.
     [DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und Einstellungen\heit\.m2\plugin-registry.xml'
     [DEBUG] Building Maven global-level plugin registry from: 'c:\Programme\Apache\maven-2.0.2\conf\plugin-registry.xml'
     [INFO] Scanning for projects...
     [INFO] Searching repository for plugin with prefix: 'deploy'.
     [DEBUG] maven-deploy-plugin: resolved to version 2.2 from repository central
     [DEBUG] Retrieving parent-POM from the repository for project: null:maven-deploy-plugin:maven-plugin:2.2
     [INFO] ----------------------------------------------------------------------------
     [INFO] Building Maven Default Project
     [INFO]    task-segment: [deploy:deploy-file] (aggregator-style)
     [INFO] ----------------------------------------------------------------------------
     [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0.1
     [DEBUG]   org.apache.maven:maven-project:jar:2.0.1 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0.1
     [DEBUG]     org.apache.maven:maven-model:jar:2.0.1 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-utils:jar:1.0.5
     [DEBUG]       org.codehaus.plexus:plexus-utils:jar:1.0.5 (selected for runtime)
     [DEBUG]         classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: null:maven-profile:jar:2.0.1
     [DEBUG]     org.apache.maven:maven-profile:jar:2.0.1 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-container-default:jar:1.0-alpha-9
     [DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-containers:pom:1.0.3
     [DEBUG]       org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 (selected for runtime)
     [DEBUG]         org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG]         junit:junit:jar:3.8.1 (selected for runtime)
     [DEBUG]     org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 (selected for runtime)
     [DEBUG]       org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG]       classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
     [DEBUG]       junit:junit:jar:3.8.1 (selected for runtime)
     [DEBUG]     org.codehaus.plexus:plexus-utils:jar:1.0.5 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0.1
     [DEBUG]     org.apache.maven:maven-artifact-manager:jar:2.0.1 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0.1
     [DEBUG]       org.apache.maven:maven-repository-metadata:jar:2.0.1 (selected for runtime)
     [DEBUG]       org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime)
     [DEBUG]         org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0.1
     [DEBUG]       org.apache.maven:maven-artifact:jar:2.0.1 (selected for runtime)
     [DEBUG]     org.apache.maven:maven-artifact:jar:2.0.1 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0.1
     [DEBUG]   org.apache.maven:maven-plugin-api:jar:2.0.1 (selected for runtime)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0
     [DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0.1 (removed - nearer found: 2.0)
     [DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime)
     [DEBUG]     org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG]     org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (removed - nearer found: 1.0-alpha-9)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0
     [DEBUG]     org.apache.maven:maven-artifact:jar:2.0 (removed - nearer found: 2.0.1)
     [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0
     [DEBUG]     org.apache.maven:maven-repository-metadata:jar:2.0 (selected for runtime)
     [DEBUG]       org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG]     org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime)
     [DEBUG]       org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG]   org.apache.maven:maven-artifact:jar:2.0.1 (removed - nearer found: 2.0)
     [DEBUG]   org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
     [DEBUG]     org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
     [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.2:deploy-file' -->
     [DEBUG]   (f) file = c:\devel\maven\plugins\maven-javadoc-plugin\target\maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
     [DEBUG]   (s) localRepository = [local] -> file://C:\Dokumente und Einstellungen\heit\.m2\repository
     [DEBUG]   (f) pomFile = c:\devel\maven\plugins\maven-javadoc-plugin\target\exported-pom.xml
     [DEBUG]   (f) repositoryId = bender
     [DEBUG]   (f) uniqueVersion = true
     [DEBUG]   (f) url = file://H:/maven-proxy/target/repo-local
     [DEBUG]   - end configuration --
     [INFO] [deploy:deploy-file]
     [INFO] Retrieving previous build number from bender
     [DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT' could not be found on repository: bender
     [DEBUG] not adding permissions to wagon connection
     Uploading: file://H:/maven-proxy/target/repo-local/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060323.110138-1.jar
     26K uploaded
     [INFO] Retrieving previous metadata from bender
     [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin' could not be found on repository: bender
     [INFO] Uploading repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin'
     [DEBUG] not adding permissions to wagon connection
     [INFO] Retrieving previous metadata from bender
     [DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT' could not be found on repository: bender
     [INFO] Uploading repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT'
     [DEBUG] not adding permissions to wagon connection
     [INFO] Retrieving previous build number from bender
     [DEBUG] not adding permissions to wagon connection
     Uploading: file://H:/maven-proxy/target/repo-local/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060323.110138-2.pom
     10K uploaded
     [INFO] Retrieving previous metadata from bender
     [INFO] Uploading repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin'
     [DEBUG] not adding permissions to wagon connection
     [INFO] Retrieving previous metadata from bender
     [INFO] Uploading repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT'
     [DEBUG] not adding permissions to wagon connection
     [INFO] ----------------------------------------------------------------------------
     [INFO] BUILD SUCCESSFUL
     [INFO] ----------------------------------------------------------------------------
     [INFO] Total time: 1 second
     [INFO] Finished at: Thu Mar 23 12:01:38 CET 2006
     [INFO] Final Memory: 2M/4M
     [INFO] ----------------------------------------------------------------------------
   
   As you can see in the debug output, when Maven uploads the plugin metadata, the POM file has a different build number than the uploaded Jar. It seems that the build number is increased during the Jar and POM file uploads and not _after_ all uploads.
   
   
   ---
   
   **Affects:** 2.2
   
   **Issue Links:**
   - [MDEPLOY-33](https://issues.apache.org/jira/browse/MDEPLOY-33) [deploy-file] When deploying a snapshot version with the pomFile specified, POM and artifact get different build numbers
    (_**"is duplicated by"**_)
   - [MDEPLOY-32](https://issues.apache.org/jira/browse/MDEPLOY-32) Snapshot deployment with deploy:deploy-file, specifying the pom and file results in invalid files uploaded
    (_**"is duplicated by"**_)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [MDEPLOY-27] Improper build number after deploying a snapshot of maven-javadoc-plugin [maven-deploy-plugin]

Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #218:
URL: https://github.com/apache/maven-deploy-plugin/issues/218#issuecomment-2771515926

   **[Brett Porter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brettporter)** commented
   
   I see you were using 2.2
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [MDEPLOY-27] Improper build number after deploying a snapshot of maven-javadoc-plugin [maven-deploy-plugin]

Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #218:
URL: https://github.com/apache/maven-deploy-plugin/issues/218#issuecomment-2771515923

   **[Brett Porter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brettporter)** commented
   
   are you using the latest SVN version? Pretty sure this is fixed...
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org