jira-importer commented on issue #535: URL: https://github.com/apache/maven-deploy-plugin/issues/535#issuecomment-2771549712
**[S L](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=thesnoozer)** commented Hi [Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte), thanks for the input. I'm completely aware that the default phase of the java-doc and sources is in package and I could fix the issue by setting the phase to any phase that will be executed earlier. The case I would like to create is kind of: I as a pom-creator should be allowed to set the execution of my plugin's to whatsoever phase (in this case deploy). I reguallary use install and don't want to waste time of the generation of javadoc's and sources. That's one of my main reason's why it's in deploy (I only want the javadoc+sources when I deploy my artifacts). However due to the fact that I have no control that the default-deploy seems to be executed as the first plugin in the deploy-phase I need to add the additional configuration. A valid workaround would also involve to set the execution of the default-deploy to the end of the deploy-phase. However, I think that's not possible due to the fact that maven executes the plugins how they are arranged in the pom. PS: I also played arround with deployAtEnd, but then the deploy will be skipped. -- 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
