Versions Compared

Old Version 5

changes.mady.by.user Unknown User (georg_dembowski)

Saved on

compared with

New Version 6

changes.mady.by.user Unknown User (georg_dembowski)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: formatting shall be okay now (wiki markup edit)

...

Panel

Wiki Markup
\[INFO\] Scanning for projects...
\[INFO\] Searching repository for plugin with prefix: 'archetype'.
\[INFO\] \---------------------------------------------------------------------------\-
\[INFO\] Building Maven Default Project
\[INFO\]    task-segment: \[archetype:create\] (aggregator-style)
\[INFO\] \---------------------------------------------------------------------------\-
...
\[INFO\] <span style="color: #ff00ff">Defaulting package to group ID: org.apache.servicemix.samples.helloWorldSE</span>
...
\[INFO\] \****************\**\**\* End of debug info from resources from generated POM **\**\******************\*
\[INFO\] Archetype created in dir: C:\0hello-world-SE-SU-SA\\{color:#009900}hello-world-SE
\[INFO\] \-----------------------------------------------------------------------\-
\[INFO\] BUILD SUCCESSFUL
\[INFO\] \-----------------------------------------------------------------------\-

...

Doing automated testing of the code is possible as well. As ServiceMix' root POM disables testing, we have to be activate it for the subprojects that shall be tested. To do so, the <build> entity of our pom.xml has to be enriched by

No Format
        <pluginManagement>
     	         <plugins>
                    <plugin>
                          <groupId>org.apache.maven.plugins</groupId>
                          <artifactId>maven-surefire-plugin</artifactId>
                          <configuration>
                                <plugins>
			<plugin>
				  <groupId>org.apache.maven.plugins</groupId>
				  <artifactId>maven-surefire-plugin</artifactId>
				  <configuration>
						<skip>false</skip><!-- this overrides ServiceMix' root POM and forces to execute the tests -->
                         root POM and forces to execute the tests -->
				  </configuration>
                    			</plugin>
            	  </plugins>
        </pluginManagement>

where <skip>false</skip> is the relevant line of code. Now, when executing

...