jira-importer commented on issue #468:
URL: 
https://github.com/apache/maven-deploy-plugin/issues/468#issuecomment-2771543496

   **[Stephen 
Connolly](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stephenc)**
 commented
   
   I am -1 on the currently attached patch for the following reason
   
   It mandates that the deploy:deploy-file be run in a directory that has a 
pom.xml
   
   There are a lot of people who use deploy:deploy-file to get their non-maven 
projects deployed to maven repositories. These people may not have a pom.xml 
(and while I agree that they _should_ they are currently not required to do 
so), or they may not call the pom file pom.xml rather someartifact.pom
   
   For that reason I am against the currently attached patch.
   
   A patch which has test cases and does not require the user to do
   
   mvn deploy:deploy-file -Dfile=someartifact.jar -DpomFile=someartifact.pom -f 
someartifact.pom
   
   but instead lets them do
   
   mvn deploy:deploy-file -Dfile=someartifact.jar -DpomFile=someartifact.pom
   
   rather than the current
   
   mvn deploy:deploy-file -Dfile=someartifact.jar -DpomFile=someartifact.pom 
-Durl=...
   
   if someartifact.pom contains the deployment url
   
   would seem like a good improvement
   


-- 
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]

Reply via email to