Skip to main content
Jump to: navigation, search

Difference between revisions of "Stardust/Source Code"

m
(Running the Build)
 
(68 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Installing Git ==
+
= Browsing the Source Code =
  
To checkout the source code your need to install git. You have different options, for instance:
+
For initial quick browsing of the source code please go to http://git.eclipse.org/c/?q=stardust.
  
*[http://git-scm.com/ git scm] installs a minimal environment to run Git. It comes with a Bash,a Perl interpreter and the Git executable plus dependencies.
+
= Overview  =
*[http://code.google.com/p/msysgit/ msysgit] installs a build environment for Git on Windows. It includes git scm.
+
  
After installing a git environment you can open a git shell to run git commands (git bash or git-cmd.bat)<br>
+
This documentation covers the local build of stardust. You can use the command line or build directly in the Eclipse IDE.  
  
== Downloading the Source Code ==
+
== Command Line Build  ==
 +
 
 +
=== Installing Git  ===
 +
 
 +
To checkout the source code you need to install git first. You have different options:
 +
 
 +
*[http://git-scm.com/ git scm] installs a minimal environment to run Git. It comes with a Bash,a Perl interpreter, the Git executable plus dependencies.
 +
*[http://msysgit.github.io/ msysgit] installs a build environment for Git on Windows. It includes git scm. After installtion you can open a git shell to run git commands (git bash or git-cmd.bat).<br>
 +
 
 +
=== Clone git Repositories ===
 +
 
 +
*Create a new folder, e.g. '''C:\\stardust''', and open a git shell there. (bash on Linux/Win or git-cmd.bat on Win)
 +
*Copy the following commands to a file named '''cloneStardust.cmd''' or '''cloneStardust.sh''' file.
 +
*Save it to the '''stardust''' folder and execute it.
 +
<pre>git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.build.tools.git build.tools
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.components.git components
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.deploy.jee.git deploy.jee
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.documentation.git documentation
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.engine.git engine
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.examples.git examples
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.git org.eclipse.stardust
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ide.git ide
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ide.simulation.git ide.simulation
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ide.wst.git ide.wst
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.product.git product
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.reporting.rt.git reporting.rt
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.repository.git repository
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ui.common.git ui.common
 +
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ui.web.git ui.web
  
#Create a new folder and open a git shell in it. (bash on Linux/Win or git-cmd.bat on Win)
 
#Copy the following commands in a cloneStardust.cmd or scloneStardust.sh file and run it (or run the commands individually)
 
<pre>git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.build.tools.git build.tools
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.ui.common.git common
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.components.git components
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.documentation.git documentation
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.engine.git engine
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.ide.git ide
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.ide.simulation.git ide.simulation
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.ide.wst.git ide.wst
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.git org.eclipse.stardust
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.product.git product
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.reporting.rt.git reporting.rt
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.reporting.app.web.git reporting.app.web
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.reporting.ui.git reporting.ui
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.ui.web.git ui.web
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.repository.git repository
 
git clone http://git.eclipse.org/gitroot//stardust/org.eclipse.stardust.ui.common.git ui.common
 
 
</pre>  
 
</pre>  
If you run git clone behind a HTTP proxy specify proxy details first.  
+
<br> If you run git clone behind a HTTP proxy specify proxy details first.  
 
<pre>git config --global http.proxy http://&lt;user&gt;:&lt;password&gt;@proxy:port</pre>  
 
<pre>git config --global http.proxy http://&lt;user&gt;:&lt;password&gt;@proxy:port</pre>  
== Building Stardust  ==
+
Now you have the default checkout which is the '''master''' branch.
  
==== Build Tools  ====
+
Following branches are available:
  
To build Stardust from the source code you check out as described above you need [http://ant.apache.org/ Apache Ant] and [http://maven.apache.org/download.html Apache Maven]. If you do not already have those tools installed please download them from their official websites and install them according to their installation instructions in a location of your choice, later called ANT_HOME and M2_HOME. We suggest Ant 1.8.4 and Maven 3.0.4, but other similar versions should work as well. After those preparations are done perform the following steps ( also see the readme.txt in the product folder).
+
'''Please find in [[Stardust/Source Code/Branch strategy|Branch strategy]] explained which branch to use.'''
  
==== Environment-specific Changes  ====
+
For more details on the differences between stardust versions, please look at the [http://projects.eclipse.org/projects/soa.stardust project website].
  
Make sure your environment variables ANT_HOME, M2_HOME and JAVA_HOME are set correctly and ant and maven are on your path. In the following all relative paths are relative to the build folder - the one in which you downloaded the source code. Create a file called private.properties in the folder build.tools\etc. Modify the file with a text editor and add the following content:  
+
If you like to clone a specific branch add '''"-b &lt;branch-name&gt;"''' to the git command. To work on a stable source please use release tags as checkout. We have a help script (linux) to do git commands on all stardust repositories:  
<pre>java16.home=[your java home path]
+
<pre>cd &lt;root-of-your-stardust-checkout&gt;
m2.home=[your maven home path]
+
build.tools\bin\git-all.sh checkout v1.0.0.20130612-0325-R</pre>
</pre>  
+
 
for instance:<br> ''java16.home=C:/Program Files/Java/jdk1.6.0_32''
+
We tag every milestone and release build. See git for details.
  
''m2.home=C:/tools/apache-maven-3.0.4''
+
=== Build Stardust  ===
  
==== Maven Configuration ====
+
==== Prerequisites ====
  
Open your maven settings.xml file (either in your user home\.m2 folder or in your maven_home\conf folder) and add this entry in the&lt;servers&gt; tag:&nbsp;<source lang="sql">
+
*JDK - we suggest Java 1.7
<server>
+
*[http://ant.apache.org/ Apache ANT] - we suggest Ant 1.8
  <id>stardust-3rdparty-repo</id>
+
*[http://maven.apache.org/download.html Apache Maven] - we suggest Maven 3.2.5
  <username>stardust.contributor</username>
+
  <password>\{DESede\}BKab8uCs+3KRLHy/l2AeHQ==</password>
+
</server>
+
</source> (Copy exactly as is. No need to replace anything here.)
+
  
==== Running the Builds ====
+
==== Running the Build ====
  
Make sure your machine is connected to the internet, open a command line in your build folder and then execute these two commands replacing [build_tools_home] with the absolute path to you build.tools sub folder:
+
To maybe cover the different build configurations in branches, we have a '''readme.md''' available in the source tree. Please follow the steps described in [http://git.eclipse.org/c/stardust/org.eclipse.stardust.product.git/tree/README.md?h=release/4.1.0 readme.md] residing in '''product''' folder.
<pre>set MAVEN_OPTS=-Xmx768m -XX:MaxPermSize=128m</pre> <pre>mvn -f product/components-pom.xml -Pipp-build -Dbuild.tools.home=[build_tools_home] install</pre>
+
For instance:<br>
+
  
mvn -f product/components-pom.xml -Pipp-build -Dbuild.tools.home=c:/stardustbuild/build.tools install<br>
+
===== Version Qualifier =====
  
Depending on your connection speed and other factors the completion of the second command can take up to several hours. After the build of the components has finished successfully, you should find the resulting artefacts in your local maven repository. Now the eclipse p2 repository with the Stardust eclipse plug-ins can be built. Run the following command replacing&nbsp;[build_tools_home] with the absolute path to your build.tools sub folder:
+
The concrete value of the .qualifier version part may be set to a define value by appending "-DforceContextQualifer=<qualifier value>".
<pre>mvn clean install -f product/pom.xml -Pfull-build,force-overwrite,ipp-build -Dbuild.tools.home=[build_tools_home]</pre>
+
Please note, that if you do not provide an explicit Stardust version and qualifier, build artifacts will use the default build version (which is currently 9.9.9-SNAPSHOT). You should check startust/org.eclipse.stardust/org.eclipse.stardust-parent/pom.xml for the ipp.version, which should equal the version you are
for instance:
+
using in your overall build.
  
''mvn clean install -f product/pom.xml -Pforce-overwrite,ipp-build -Dbuild.tools.home=c:/stardustbuild/build.tools''
+
==== Where to go from here?<br>  ====
  
This will trigger the build of the p2 repository. After the build has finished successful, you will find the repository in the sub folder&nbsp;: <br>  
+
Now you can use the build result, '''a local eclipse update site''',&nbsp;to install Stardust. Follow the instructions in the section [[Stardust/Knowledge Base/Getting Started/Installation#Local_Eclipse_Update_Site|Local Eclipse Update Site (offline)]]<br>
  
''stardust/repository/org.eclipse.stardust.modeling.repository/target/repository/ ''
+
If you like to consume our '''archetypes''', e.g. tomcat7 web archive, via maven please find documentation here: [http://wiki.eclipse.org/Stardust/Knowledge_Base/Build_and_Change_Management/Maven/Basic_Setup Maven - Basic Setup]
  
and zipped as an update site:  
+
Next check out the resource in the [[Stardust/Knowledge Base|Stardust Knowledge Base]], especially the [[Stardust/Knowledge Base#Getting_Started|Getting Started]] section. You may also want to check out the [http://www.eclipse.org/forums/index.php?t=thread&frm_id=225 Forum] to post questions or just exchange thoughts with the community.<br>
 +
To access the '''online help''' please consult [http://help.eclipse.org/topic/org.eclipse.stardust.docs.dev/html/toc.html help.eclipse.org]
  
''stardust/repository/org.eclipse.stardust.modeling.repository/target/org.eclipse.stardust.modeling.repository.zip ''
+
==== Troubleshooting<br>  ====
  
== Binary Distribution  ==
+
If you experience any problems downloading the source code or building Stardust then please contact us via the [http://www.eclipse.org/forums/index.php?t=thread&frm_id=225 Forum].<br>
  
All Stardust source code has been submitted to the Eclipse git repository. A complete binary distribution requires libraries which are still pending approval by Eclipse legal, hence no binary distribution is available yet. One will be available for download form the project website as soon as the libraries have been approved.
+
===== Errors fetching Dependencies<br>  =====
  
== Compliance  ==
+
If you encounter errors during the build that indicate <u>missing dependencies</u> which could not be fetched from the repositories then try cleaning the ivy cache folder .ivy in your <span style="font-style: italic;">user.</span>''home'' (e.g. C:\Users\your.name\.ivy, if it exists) and the maven repository (check settings.xml in ''M2_HOME''/etc and/or ''user.home''/.m2 to determine the location).<br>
  
*The products libraries have been reviewed for license conflicts.  
+
If your are using <u>Maven 3.0.4 behind a proxy</u> please see [[Stardust/Knowledge Base/Build and Change Management/Maven/Basic Setup#Troubleshooting|here]] on how to fix the issue.
*Dependencies that did not comply with the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License] (EPL) have been replaced
+
*The source has been submitted to the Eclipse foundation where it was reviewed with regards to intellectual property rights and licensing.
+
*The source was refactored. All package names were change to the eclipse package names.
+

Latest revision as of 12:14, 21 December 2016

Browsing the Source Code

For initial quick browsing of the source code please go to http://git.eclipse.org/c/?q=stardust.

Overview

This documentation covers the local build of stardust. You can use the command line or build directly in the Eclipse IDE.

Command Line Build

Installing Git

To checkout the source code you need to install git first. You have different options:

  • git scm installs a minimal environment to run Git. It comes with a Bash,a Perl interpreter, the Git executable plus dependencies.
  • msysgit installs a build environment for Git on Windows. It includes git scm. After installtion you can open a git shell to run git commands (git bash or git-cmd.bat).

Clone git Repositories

  • Create a new folder, e.g. C:\\stardust, and open a git shell there. (bash on Linux/Win or git-cmd.bat on Win)
  • Copy the following commands to a file named cloneStardust.cmd or cloneStardust.sh file.
  • Save it to the stardust folder and execute it.
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.build.tools.git build.tools
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.components.git components
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.deploy.jee.git deploy.jee
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.documentation.git documentation
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.engine.git engine
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.examples.git examples
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.git org.eclipse.stardust
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ide.git ide
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ide.simulation.git ide.simulation
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ide.wst.git ide.wst
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.product.git product
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.reporting.rt.git reporting.rt
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.repository.git repository
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ui.common.git ui.common
git clone http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.ui.web.git ui.web


If you run git clone behind a HTTP proxy specify proxy details first.

git config --global http.proxy http://<user>:<password>@proxy:port

Now you have the default checkout which is the master branch.

Following branches are available:

Please find in Branch strategy explained which branch to use.

For more details on the differences between stardust versions, please look at the project website.

If you like to clone a specific branch add "-b <branch-name>" to the git command. To work on a stable source please use release tags as checkout. We have a help script (linux) to do git commands on all stardust repositories:

cd <root-of-your-stardust-checkout>
build.tools\bin\git-all.sh checkout v1.0.0.20130612-0325-R

We tag every milestone and release build. See git for details.

Build Stardust

Prerequisites

Running the Build

To maybe cover the different build configurations in branches, we have a readme.md available in the source tree. Please follow the steps described in readme.md residing in product folder.

Version Qualifier

The concrete value of the .qualifier version part may be set to a define value by appending "-DforceContextQualifer=<qualifier value>". Please note, that if you do not provide an explicit Stardust version and qualifier, build artifacts will use the default build version (which is currently 9.9.9-SNAPSHOT). You should check startust/org.eclipse.stardust/org.eclipse.stardust-parent/pom.xml for the ipp.version, which should equal the version you are using in your overall build.

Where to go from here?

Now you can use the build result, a local eclipse update site, to install Stardust. Follow the instructions in the section Local Eclipse Update Site (offline)

If you like to consume our archetypes, e.g. tomcat7 web archive, via maven please find documentation here: Maven - Basic Setup

Next check out the resource in the Stardust Knowledge Base, especially the Getting Started section. You may also want to check out the Forum to post questions or just exchange thoughts with the community.
To access the online help please consult help.eclipse.org

Troubleshooting

If you experience any problems downloading the source code or building Stardust then please contact us via the Forum.

Errors fetching Dependencies

If you encounter errors during the build that indicate missing dependencies which could not be fetched from the repositories then try cleaning the ivy cache folder .ivy in your user.home (e.g. C:\Users\your.name\.ivy, if it exists) and the maven repository (check settings.xml in M2_HOME/etc and/or user.home/.m2 to determine the location).

If your are using Maven 3.0.4 behind a proxy please see here on how to fix the issue.

Back to the top