Bukama commented on PR #655:
URL: 
https://github.com/apache/maven-deploy-plugin/pull/655#issuecomment-4413370793

   Interesting: The four ITs with JIRA-issueID overwrite `deployAtEnd` value to 
`true` fail. This is the new default in version 4.x of the plugin, but we are 
testing 3.x so this should not make any difference when choosing the path to 
deploy.
   
   
   I still could not figure out why the `distributionManagement` is ignored for 
subprojects
   
   
   ```
   <!-- Set in parent of the IT project -->
   
   <distributionManagement>
     <repository>
       <id>it</id>
       <url>file:///${basedir}/target/repo</url>
     </repository>
   </distributionManagement>
   
   
   // All files are deployed there
   [INFO] Uploading to it: 
file:///D:\Github\Maven\maven-deploy-plugin\target\it\MDEPLOY-170_deploy-at-end-configperproject/target/repo/org/apache/maven/its/mdeploy-170/configperproject/1.0/configperproject-1.0-build.pom
   
   // Even subprojects files
   [INFO] Uploading to it: 
file:///D:\Github\Maven\maven-deploy-plugin\target\it\MDEPLOY-170_deploy-at-end-configperproject/target/repo/org/apache/maven/its/mdeploy-170/module1/1.0/module1-1.0.pom
   ```
   
   The file exists there (See screenshot below), but the verify script checks 
the target folder inside each subproject
   
   
   ```
   verify-script:
   
   assert new File( basedir, 
"target/repo/org/apache/maven/its/mdeploy-170/configperproject/1.0/configperproject-1.0.pom"
 ).exists()
   assert new File( basedir, 
"module1/target/repo/org/apache/maven/its/mdeploy-170/module1/1.0/module1-1.0.pom"
 ).exists()
   assert !( new File( basedir, 
"module2/target/repo/org/apache/maven/its/mdeploy-170/module2/1.0/module2-1.0.pom"
 ).exists() )
   
   
   Assertion failed:
   
   assert new File( basedir, 
"module1/target/repo/org/apache/maven/its/mdeploy-170/module1/1.0/module1-1.0.pom"
 ).exists()
   | | |
   | 
D:\Github\Maven\maven-deploy-plugin\target\it\MDEPLOY-170_deploy-at-end-configperproject
 false
   
D:\Github\Maven\maven-deploy-plugin\target\it\MDEPLOY-170_deploy-at-end-configperproject\module1\target\repo\org\apache\maven\its\mdeploy-170\module1\1.0\module1-1.0.pom
   
   ```
   
   The file exists, but in the target repository of the parent
   
   
`D:\Github\Maven\maven-deploy-plugin\target\it\MDEPLOY-170_deploy-at-end-configperproject\target\repo\org\apache\maven\its\mdeploy-170\module1\1.0`
   
   <img width="1566" height="557" alt="image" 
src="https://github.com/user-attachments/assets/95c23e68-cdd8-4c3d-b564-a1e27ca56f7c";
 />
   
   
   
   So what has changed here in Maven 4? 


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