jira-importer commented on issue #295: URL: https://github.com/apache/maven-deploy-plugin/issues/295#issuecomment-2771522656
**[Jürgen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=work_registries)** commented I can confirm this behaviour. If you define multiple executions for deploy:deploy-file, it appears as if once javadoc is set, it will retain its value for all subsequent deploy-file executions, in terms of artifact-id at least. Also, if a subsequent execution does not have javadoc property set, javadoc upload still happens because it was set in the previous execution configuration. For that matter, I tried using \<files>/\<classifier>/\<types> instead of \<javadoc> and got the same problem. Using maven 2.2.1, jdk 1.6.0_34 ``` <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-deploy-plugin</artifactId> <version>2.8.1</version> <executions> <execution> <id>ojdbc5</id> <phase>deploy</phase> <goals> <goal>deploy-file</goal> </goals> <configuration> <file>ojdbc5.jar</file> <artifactId>ojdbc5</artifactId> <packaging>jar</packaging> <javadoc>javadoc.zip</javadoc> </configuration> </execution> <execution> <id>ojdbc5_g</id> <phase>deploy</phase> <goals> <goal>deploy-file</goal> </goals> <configuration> <file>ojdbc5_g.jar</file> <artifactId>ojdbc5_g</artifactId> <packaging>jar</packaging> <javadoc>javadoc.zip</javadoc> </configuration> </execution> </executions> <configuration> <groupId>oracle.jdbc</groupId> <version>11.2.0.4.0</version> <classifier>manual</classifier> <createChecksum>true</createChecksum> <generatePom>true</generatePom> <uniqueVersion>false</uniqueVersion> <repositoryId>ext-releases-local</repositoryId> <repositoryLayout>default</repositoryLayout> <url>${ext-releases-local.repository.url}</url> </configuration> </plugin> ``` log output (a bit reedited) ``` [INFO] Uploading repository metadata for: 'artifact oracle.jdbc' [INFO] [deploy:deploy-file {execution: ojdbc5}] Uploading: XXX/ext-releases-local/oracle/jdbc/ojdbc5/11.2.0.4.0/ojdbc5-11.2.0.4.0-manual.jar 2042K uploaded (ojdbc5-11.2.0.4.0-manual.jar) [INFO] Uploading project information for ojdbc5 11.2.0.4.0 [INFO] Retrieving previous metadata from ext-releases-local [INFO] Uploading repository metadata for: 'artifact oracle.jdbc:ojdbc5' Uploading: XXX/ext-releases-local/oracle/jdbc/ojdbc5/11.2.0.4.0/ojdbc5-11.2.0.4.0-javadoc.jar 6265K uploaded (ojdbc5-11.2.0.4.0-javadoc.jar) [INFO] [deploy:deploy-file {execution: ojdbc5_g}] Uploading: XXX/ext-releases-local/oracle/jdbc/ojdbc5_g/11.2.0.4.0/ojdbc5_g-11.2.0.4.0-manual.jar 3343K uploaded (ojdbc5_g-11.2.0.4.0-manual.jar) [INFO] Uploading project information for ojdbc5_g 11.2.0.4.0 [INFO] Retrieving previous metadata from ext-releases-local [INFO] Uploading repository metadata for: 'artifact oracle.jdbc:ojdbc5_g' Uploading: XXX/ext-releases-local/oracle/jdbc/ojdbc5/11.2.0.4.0/ojdbc5-11.2.0.4.0-javadoc.jar [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR ``` Build error results from missing permissions of maven user to overwrite already uploaded ojdbc5-11.2.0.4.0-javadoc.jar artifact in ext-releases-local But clearly shows maven tries to upload "oracle/jdbc/ojdbc5/11.2.0.4.0/ojdbc5-11.2.0.4.0-javadoc.jar" twice, instead of "oracle/jdbc/ojdbc5_g/11.2.0.4.0/ojdbc5_g-11.2.0.4.0-javadoc.jar" -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
