Eclipse Community Forums: Eclipse Process Manager (Stardust) » Today's clone of the -b I_4

Help

Home

Home » Archived » Eclipse Process Manager (Stardust) » Today's clone of the -b I_4_3 question

Show: Today's Messages :: Show Polls :: Message Navigator

Today's clone of the -b I_4_3 question [message #1092409]

Thu, 22 August 2013 19:12

David Malkovsky

Messages: 4
Registered: July 2009

Junior Member

I just did a git clone using "-b I_4_3" as noted in other forum posts as the branch to use; for example:

git clone -b I_4_3 http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.build.tools.git build.tools

When I do that I notice that it appears there have been changes for the SR1 RC1 release. For example in product/product-parent/pom.xml I see changes like:

<eclipse-platform.version>4.3.1RC1</eclipse-platform.version>

and
<emf-runtime.version>2.9.1RC1</emf-runtime.version>

among other changes.

Should this change have be made to the I_4_3 tagged sources? Isn't that tag meant to match released sources?

I found the complete set of changes at http://git.eclipse.org/c/stardust/org.eclipse.stardust.build.tools.git/commit/?h=I_4_3

This is not how I would typically image branching be used. What is the scheme being employed? Should we still be using the I_4_3 branch as the branch to be integrating with the 4.3 Kepler release code?

It appears that you are using I_4_3 as the integration branch is there some other tag we should be using for the stable code base that matches the initial 1.0 release?

Is this still too bleeding edge to be used by the general community?

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092772 is a reply to message #1092409]

Fri, 23 August 2013 07:18

Sven Rottstock

Messages: 29
Registered: December 2012

Junior Member

--- repeated post due to forum errors

[Updated on: Tue, 27 August 2013 08:23]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092788 is a reply to message #1092409]

Fri, 23 August 2013 07:43

Sven Rottstock

Messages: 29
Registered: December 2012

Junior Member

Indeed, branch I_4_3 is used for the latest Kepler development. This means that we're pushing all SR1 related changes into it. But for each milestone and release build we're tagging the sources. So if you want to use the stable sources then you have to checkout one of the release tags (at the moment we have only one release tag, namely v1.0.0.20130612-0325-R). You can easily do this in the Git bash as follows:

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

The git-all.sh script steps into each Stardust repository and executes the git command: git checkout v1.0.0.20130612-0325-R

After we had released Stardust 1.0.0 we have merged all changes from I_4_3 into master. From this point on, master should contain the latest stable release sources. And as far as I know we want to continue this pattern. This means all branches like I_4_3 are used as a development branch and the master contains the production sources.

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092789 is a reply to message #1092409]

Fri, 23 August 2013 07:44

Sven Rottstock

Messages: 29
Registered: December 2012

Junior Member

--- repeated post due to forum errors

[Updated on: Tue, 27 August 2013 08:23]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092831 is a reply to message #1092409]

Fri, 23 August 2013 08:49

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:02]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092855 is a reply to message #1092409]

Fri, 23 August 2013 09:04

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:02]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092860 is a reply to message #1092409]

Fri, 23 August 2013 09:08

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:02]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092869 is a reply to message #1092409]

Fri, 23 August 2013 09:15

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:03]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092873 is a reply to message #1092409]

Fri, 23 August 2013 09:16

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:03]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092874 is a reply to message #1092409]

Fri, 23 August 2013 09:16

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:03]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092881 is a reply to message #1092409]

Fri, 23 August 2013 09:26

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:04]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092882 is a reply to message #1092409]

Fri, 23 August 2013 09:26

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:04]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1092910 is a reply to message #1092409]

Fri, 23 August 2013 10:10

Robert Emsbach

Messages: 186
Registered: October 2011
Location: Singapore

Senior Member

--- repeated post due to forum errors

[Updated on: Mon, 26 August 2013 06:04]

Report message to a moderator

Re: Today's clone of the -b I_4_3 question [message #1093001 is a reply to message #1092409]

Fri, 23 August 2013 12:23

David Malkovsky

Messages: 4
Registered: July 2009

Junior Member

FWIW, I was able to get the maven builds running (see http://wiki.eclipse.org/Stardust/Source_Code#Running_the_Builds) using the clone of the repository as of 22Aug2013 by adding the following jars (from a co-worker's build machine):

org.eclipse.xsd.jar
org.eclipse.osgi.jar
org.eclipse.equinox.registry.jar
org.eclipse.equinox.common.jar
org.eclipse.emf.ecore.xmi.jar
org.eclipse.emf.ecore.jar
org.eclipse.emf.ecore.change.jar
org.eclipse.emf.common.jar
org.eclipse.core.runtime.jar

into the build.tools/lib/org/eclipse/ directory.

Report message to a moderator

Previous Topic:	Stardust 1.0 with maven
Next Topic:	How to try out Lightdust / Browser Modeler?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 00:25:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter