Stanford:QaGuide - Revision history

Johner: /* My build fails since the sonar plugin was not found! What can I do? */

2011-01-06T16:32:07Z

‎My build fails since the sonar plugin was not found! What can I do?

2010-12-16T19:48:44Z

2010-12-16T19:22:59Z

20 revisions: Import from CF Pages (2)

2010-12-14T00:33:40Z

Additional information since we still got problems.

2010-12-13T17:24:24Z

path updated

2010-11-29T20:23:16Z

‎How-to for architects, test and project managers

2010-11-23T19:52:20Z

‎How to write the Maven script (pom.xml): some links to GWT added

2010-11-22T17:50:41Z

‎Related to reporting

2010-11-16T20:06:02Z

‎How to upload required artifacts (typicall jar-files) to Nexus repository

2010-11-16T20:05:28Z

‎How to upload required artifacts (typicall jar-files) to Nexus repository

@@ Line 181: / Line 181: @@
 What can you do? As the plugin update is not working as it is supposed to do, please remove the following two directories:
-# Maven local repository: <tt>/usr/local/data/hudson/.m2/repository/org/codehaus/mojo/sonar-maven-plugin</tt>
+# Maven local repository: <tt>sudo rm -r /usr/local/data/hudson/.m2/repository/org/codehaus/mojo/sonar-maven-plugin</tt>
-# Nexus repository: <tt>/usr/local/data/sonatype-work/nexus/storage/central/org/codehaus/mojo/sonar-maven-plugin</tt>
+# Nexus repository: <tt>sudo rm -r /usr/local/data/sonatype-work/nexus/storage/central/org/codehaus/mojo/sonar-maven-plugin</tt>
 Then run the build again. Now the repositories are updated and your build should run successfully.

← Older revision		Revision as of 19:48, December 16, 2010
Line 385:		Line 385:
	* http://maven.apache.org/plugins/maven-assembly-plugin/index.html		* http://maven.apache.org/plugins/maven-assembly-plugin/index.html
	* http://maven.apache.org/plugins/maven-dependency-plugin/ (includes the unpacking of artifacts into a directory)		* http://maven.apache.org/plugins/maven-dependency-plugin/ (includes the unpacking of artifacts into a directory)
		+
		+	[[Category:QualityAssurance]]

← Older revision		Revision as of 00:33, December 14, 2010
Line 185:		Line 185:

	Then run the build again. Now the repositories are updated and your build should run successfully.		Then run the build again. Now the repositories are updated and your build should run successfully.
		+
		+	If this fails do addtionally the following:
		+	# ssh to bmir-hudson1.standford.edu
		+	# Switch user: <tt>sudo su - hudson</tt>
		+	# if Maven path is not yet set:
		+	#* <tt>export M2_HOME=/usr/local/apache-maven-2.2.1</tt>
		+	#* <tt>export PATH=$PATH:$HOME/bin:$JAVA_HOME/bin:$M2_HOME/bin</tt>
		+	# Run one project from command line
		+	#* switch to one project <tt>cd /usr/local/data/hudson/jobs/Example-Project/workspace</tt>
		+	#* <tt>mvn -U sonar:sonar</tt> The -U forces the update. Now the maven plugin should be downloaded

	==Related to pom.xml==		==Related to pom.xml==

@@ Line 182: / Line 182: @@
 What can you do? As the plugin update is not working as it is supposed to do, please remove the following two directories:
 # Maven local repository: <tt>/usr/local/data/hudson/.m2/repository/org/codehaus/mojo/sonar-maven-plugin</tt>
-# Nexus repository: <tt>/var/nexus/sonatype-work/nexus/storage/central/org/codehaus/mojo/sonar-maven-plugin</tt>
+# Nexus repository: <tt>/usr/local/data/sonatype-work/nexus/storage/central/org/codehaus/mojo/sonar-maven-plugin</tt>
 Then run the build again. Now the repositories are updated and your build should run successfully.

@@ Line 1: / Line 1: @@
 =How-to for architects, test and project managers=
 In this section you find how tos which are related to convert projects from ANT to Maven, to write pom.xml files etc.
 =How to create a new or convert an existing project =

← Older revision	Revision as of 19:22, December 16, 2010
(No difference)

@@ Line 136: / Line 136: @@
 * Both repositories (snapshot and release) are defined in the <tt><distributionManagement></tt> section respectively in the <tt>/maven/conf/settings.xml</tt> file.
 * If you are deploying to tomcat, e.g. to perform integration tests, make sure that user and password match with tomcat manger credentials.
 * '''Please read the FAQ section with specific questions on how to write a pom.xml'''.

@@ Line 154: / Line 154: @@
 ===I do not get code coverage statistics for my integration tests. What can I do?===
 Currently nothing, this is the way maven handles the build process.
 ==Related to pom.xml==

@@ Line 80: / Line 80: @@
 # Uploaded file automatically in due course of a build process (this is '''recommended''' for "own" code as Snapshots and Releases).
 #* There is nothing to do besides adding the <distributionManagement> tag to the pom.xml and use the deploy plugin. The PC specific <tt>settings.xml</tt> has to point to the repository as described in the adminstrators guide in section TODO
-# Uploaded file using the Nexus interface ('''recommended only for third party artifacts'''). This option is described in the following subchapter.
+# Uploaded file using the Nexus interface ('''recommended only for third party artifacts'''). This option is described in the following:
 {|

@@ Line 74: / Line 74: @@
 ==How to upload required artifacts (typicall jar-files) to Nexus repository==
 There are multiple ways of adding resources to the repository
-# Direct copy (not recommended)
+# Direct copy ('''not recommended''')
 #* Copy resources directly to Nexus subfolder e.g. to <tt>/var/nexus/sonatype-work/nexus/storage/thirdparty/edu/stanford/bmir/core/icd</tt>.
 #* You need to put the file the right directory and give it the name indicating the version number, e.g. <tt>/edu/Stanford/bmir/core/protégé-1.0.jar</tt>
 #* Goto nexus and right click on third party repository: reindex respectively rebuild metadata
-# Uploaded file automatically in due course of a build process (this is recommended for "own" code as Snapshots and Releases).
+# Uploaded file automatically in due course of a build process (this is '''recommended''' for "own" code as Snapshots and Releases).
 #* There is nothing to do besides adding the <distributionManagement> tag to the pom.xml and use the deploy plugin. The PC specific <tt>settings.xml</tt> has to point to the repository as described in the adminstrators guide in section TODO
-# Uploaded file using the Nexus interface (recommended especially for third party artifacts). This option is described in the following subchapter.
+# Uploaded file using the Nexus interface ('''recommended only for third party artifacts'''). This option is described in the following subchapter.
 {|