jira-importer commented on issue #535: URL: https://github.com/apache/maven-deploy-plugin/issues/535#issuecomment-2771549714
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented Now you describe your **real** issue: you want to be able to specify attachments only for `deploy` (and not for `install`). > I as a pom-creator should be allowed to set the execution of my plugin's to whatsoever phase (in this case deploy). > And you can, but you still have to respect the default lifecycle. > You already noticed that the deploy-plugin is always called first, no matter the order of plugins, since that how it is defined in the lifecycle for all packaging types. > So your hack was to introduce introduce an extra execution block for the deploy-plugin. Now regarding the twice-upload: executions aren't aware of each other, so it's not possible to detect this within the plugin. (which implies that in the end I will close this as won't fix) I still want to state that after the package-phase the project should be for transfer, either `install` or `deploy`. I also think that it is up to the end user to decide if he/she wants to `install` the sources and javadoc, and not the pom-creator. If you still want control over the do/don't attach of these files, here are some options: - (preferred) make use the skip parameter of both plugins. You could introduce your own property to set them both at once. - Use a profile where for the attachment plugins. It's up to you to active it by default or not. - (hack, not verified) keep the execution-block in the deploy-plugin. In its global configuration set skip to true, in the execution block to false. You could ask for an option in the maven-install-plugin to ignore some classified files to be installed, but I will probably start another discussion on that one ;) -- 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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
