| Re: [tycho-user] version of ‘eclipse.exe’ and ‘eclipsec.exe’ |
|
Hello Alex, Thanks for your prompt reply! I don’t think the version of ‘org.eclipse.rcp.configuration’ is the cause. These are the versions used in the various Eclipse versions: -
Our version : 1.0.0.v20130521-1847 -
Eclipse SDK 4.3 : 1.0.0.v20130521-1847 -
Eclipse SDK 4.3.1 : 1.0.0.v20130521-1847 -
Eclipse SDK 4.3.2 : 1.0.0.v20140117-0610 Looking at the size of the 32-bit version of ‘eclipse.exe’ -
Our version : 319,488 bytes -
Eclipse SDK 4.3 : 319,488 bytes -
Eclipse SDK 4.3.1 : 327,384 bytes -
Eclipse SDK 4.3.2 : 327,384 bytes I don’t see the correlation between the version of ‘org.eclipse.rcp.configuration’ and the ‘eclipse.exe’. So I don’t know what mechanism causes Eclipse SDK 4.3.1 to have another ‘eclipse.exe’ than Eclipse SDK 4.3. As for EMF, it is not a direct dependency from our ‘.product’ file, so I guess feature ‘org.eclipse.sdk’ must pull it in, without a version constraint. But now you mention it, when I look through the features of the materialized Eclipse, I see that feature ‘org.eclipse.e4.rcp’ has the following
requirement:
<requires>
<import
feature="org.eclipse.emf.common"
version="2.7.0"
match="compatible"/>
<import
feature="org.eclipse.emf.ecore"
version="2.7.0"
match="compatible"/>
</requires> So I guess that’s why it uses the 2.9.2 version, which is the highest one available today on the Kepler update site. Kind regards, Marcel From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
On Behalf Of Alex Blewitt Check the version of the org.eclipse.rcp.configuration; it may be downgrading the version of Eclipse to use. <feature id="org.eclipse.rcp.configuration" version="1.0.0.v20130521-1847"/> If you’re using EMF from the kepler update site then if you don’t have any version constraints then it will pick the latest one. At the time the Eclipse SDK was built, 2.9.2 wasn’t available so that’s why it’s
not in there - but if rebuilt today, it would have 2.9.2. Alex On 25 Apr 2014, at 11:22, Marcel Romijn <mromijn@xxxxxxxxxxxxxxxxxx> wrote:
Hello, We’re migrating from a PDE-based product build to a Maven/Tycho-based product build. Some steps require the creation of an Eclipse, enriched with 3rd Party features and in-house created features: - We
provide the product developers with a preconfigured Eclipse SDK, including often used tools - Finally
we materialize the product update-site into an installable product In both cases, the final result is defined in a ‘.product’ file and architecture specific modifications to the ‘eclipse.ini’ file are done with a ‘p2.inf’ file. Because of the development/QA train, we need to base our product on Eclipse 4.3.1 (for now). The resulting materialized Eclipse closely resembles the Eclipse SDK that is downloaded from: http://download.eclipse.org/eclipse/downloads/drops4/R-4.3.1-201309111000/ This makes me think that we’re on the right track. However, I see two differences: - The
‘eclipse.exe’ and ‘eclipsec.exe’ appear to be the same as the ones from Eclipse 4.3.0 instead of Eclipse 4.3.1. - The
materialized Eclipse uses on EMF features of version ‘2.9.2.v20131212-0545’, while Eclipse SDK download uses EMF features of version ‘2.9.1.v20130827-0309’ Can someone explain these differences? Are they worth worrying about, or are they harmless? I have attached a stripped-down version of a Maven/Tycho build that shows the problem. Running ‘mvn clean verify’ on the top-level ‘pom.xml’ produces a Windows 32-bit and 64-bit Eclipse 4.3.1, as described above. Marcel Romijn <example.zip>_______________________________________________ |