KingSpring opened a new issue, #37512:
URL: https://github.com/apache/shardingsphere/issues/37512

   ## Bug Report
   
   
   ### Which version of ShardingSphere did you use?
   master
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   all
   
   ### Expected behavior
   The build command  
   ```
   ./mvnw clean install -P"release,default-dep" -T1C -DskipTests
   ```  
   should complete successfully on Windows (Git Bash / WSL / PowerShell) and 
produce the distribution tarball.
   
   ### Actual behavior
   When running the command **without** the quotes around the profiles:  
   ```
   ./mvnw clean install -Prelease,default-dep -T1C
   ```  
   Maven fails with the following error:
   
   ```
   所在位置 行:1 字符: 31
   + ./mvnw clean install -Prelease,default-dep -T1C
   +                               ~
   参数列表中缺少参量。
       + CategoryInfo          : ParserError: (:) [], 
ParentContainsErrorRecordException
       + FullyQualifiedErrorId : MissingArgument
   ```
   
   The build stops immediately and no artifacts are produced.
   
   ### Reason analyze (If you can)
   On Windows shells (Git Bash, PowerShell, CMD) the comma in 
`-Prelease,default-dep` is interpreted as a parameter separator by the shell, 
so Maven receives two separate tokens:  
   1. `-Prelease`  
   2. `default-dep`  
   
   The second token is then treated as an unknown lifecycle phase instead of 
part of the profile list.  
   Quoting the list (`-P"release,default-dep"`) prevents the comma from being 
mis-interpreted and passes the entire string as a single Maven property.
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   1. Clone the repository on Windows.  
   2. Open Git Bash or PowerShell.  
   3. Run  
      ```
      ./mvnw clean install -Prelease,default-dep -T1C
      ```  
   4. Observe the immediate “Unknown lifecycle phase” error.
   


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