Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Gemini/DBAccess/CommitterGuide/HowToBuild"

(Background)
Line 1: Line 1:
= Eclipse IDE =
+
== Eclipse IDE ==
 
To compile and run the projects in Eclipse, you have to open the gemini.dbaccess.targetdef project,  
 
To compile and run the projects in Eclipse, you have to open the gemini.dbaccess.targetdef project,  
 
open the file gemini.dbaccess.target with the Target Editor and execute "Set as Target Platform"
 
open the file gemini.dbaccess.target with the Target Editor and execute "Set as Target Platform"
  
= Maven Build =
+
== Maven Build ==
 
# install Maven 3.
 
# install Maven 3.
 
# go into the directory mvn_parent/  
 
# go into the directory mvn_parent/  
Line 10: Line 10:
  
  
= Tips and Tricks for Maven Builds =
+
== Tips and Tricks for Maven Builds ==
 
You may need to configure the proxy settings. In case you are behind a firewall, edit the file  
 
You may need to configure the proxy settings. In case you are behind a firewall, edit the file  
 
/mvn_parent/settings.xml and replace the TODOs with the right proxy settings. If you have configured the settings.xml:
 
/mvn_parent/settings.xml and replace the TODOs with the right proxy settings. If you have configured the settings.xml:
Line 17: Line 17:
 
#* mvn -fae -s settings.xml clean install
 
#* mvn -fae -s settings.xml clean install
  
= Static Code Analysis for Maven Builds =
+
== Static Code Analysis for Maven Builds ==
 
If you add findbugs:findbugs at the end of the command line, you will find information from findbugs in the different
 
If you add findbugs:findbugs at the end of the command line, you will find information from findbugs in the different
 
/target directories:  
 
/target directories:  
> mvn clean install findbugs:findbugs
+
* mvn clean install findbugs:findbugs
  
 
Note: This could be aggregated and displayed in late stage by Hudson.
 
Note: This could be aggregated and displayed in late stage by Hudson.
  
  
= Background =
+
== Background ==
 
Some remarks on what the Maven build does:
 
Some remarks on what the Maven build does:
 
* the folder /mvn_parent contains a pom.xml which is the "parent" of all subprojects. Every bundle which is build has its own pom.xml file
 
* the folder /mvn_parent contains a pom.xml which is the "parent" of all subprojects. Every bundle which is build has its own pom.xml file
Line 31: Line 31:
 
* features, which include the bundles of the supported database platforms are also built.
 
* features, which include the bundles of the supported database platforms are also built.
 
* an update site is generated: /gemini.dbaccess.updatesite . You find the p2 repository under /target/site/ a p2 containing the features and all plugins included.
 
* an update site is generated: /gemini.dbaccess.updatesite . You find the p2 repository under /target/site/ a p2 containing the features and all plugins included.
 +
 +
[[Category:Gemini_DBAccess|DBAccess]]

Revision as of 07:46, 9 January 2013

Eclipse IDE

To compile and run the projects in Eclipse, you have to open the gemini.dbaccess.targetdef project, open the file gemini.dbaccess.target with the Target Editor and execute "Set as Target Platform"

Maven Build

  1. install Maven 3.
  2. go into the directory mvn_parent/
  3. run the build and tests by entering on the command line:
    • mvn clean install


Tips and Tricks for Maven Builds

You may need to configure the proxy settings. In case you are behind a firewall, edit the file /mvn_parent/settings.xml and replace the TODOs with the right proxy settings. If you have configured the settings.xml:

  1. go into the directory mvn_parent/
  2. run on the command line:
    • mvn -fae -s settings.xml clean install

Static Code Analysis for Maven Builds

If you add findbugs:findbugs at the end of the command line, you will find information from findbugs in the different /target directories:

  • mvn clean install findbugs:findbugs

Note: This could be aggregated and displayed in late stage by Hudson.


Background

Some remarks on what the Maven build does:

  • the folder /mvn_parent contains a pom.xml which is the "parent" of all subprojects. Every bundle which is build has its own pom.xml file
  • Maven builds every bundle. Result are in the /target folder of the respective directory.
  • features, which include the bundles of the supported database platforms are also built.
  • an update site is generated: /gemini.dbaccess.updatesite . You find the p2 repository under /target/site/ a p2 containing the features and all plugins included.

Back to the top