Difference between the Visual Studio and Command-Line Executions

Editor
May 14, 2009 at 9:05 AM

This is how Visual Studio executes a Clean/Build/Install.

Name: NPanday's Maven Phase Algorithm
Description: Algorithm that differs the Visual Studio Execution.from Console Command.


  1.All Project - Is triggered when the user right click in the solution explorer and select “All NPanday Projects” and ANY of  the maven phase.
           1.1. Save All Documents that are Open in VS 
           1.2. Retrieve the Solution that is open in VS.
           1.3. Loop through all the project in the solution.
           1.4. Check If it has a Web reference, if it has it will update the webreference. ***this is to update the webreference and build the wsdl.
           1.5. Execute the pom.xml of the solution may it be Clean/Build/Install. ***this is the actual execution in the command-line.
  2. Current Project - Is triggered when the user right click in the solution explorer and select “Current NPanday Projects” and ANY of the maven phase.
           2.1. Save All Documents that are Open in VS.
           2.2. Retrieve Current Pom.xml and Current Project
                   2.2.1. If Pom.xml does not exist, set errorMsg to pomNotFoundError.
                   2.2.2. If the packaging in the pom.xml is “pom”, set errorMsg to pomMayNotBeProjectPomsError.
           2.3. Check If it has a Web reference, if it has it will update the webreference. ***this is to update the webreference and build the wsdl.
           2.4. Execute the pom.xml of the solution may it be Clean/Build/Install. ***this is the actual execution in the command-line.

 

The steps 1.2 and 2.2 is where NPanday looks for the pom.xml to execute your selected action may it be clean, build or install. What NPanday is aiming is to behave the same as the command-line counterpart.