Buckminster Headless and Eclipse 3.7.2 ? [message #810421] |
Wed, 29 February 2012 23:19  |
Eclipse User |
|
|
|
I hope this is the proper area but if not if an administrator could move the thread I would be grateful. Simply put is the expectation that the current Buckminster headless update site should work with Eclipse 3.7.2?
It seems that there is some kind of conflict with Buckminster and Equinox 3.7.2 around Simple Configurator. Equinox 3.7.2 appears to have 1.0.200.v20110815-1438 but the Buckminster update site has 1.0.200.v20110502-1955 which results in an error during installation.
The steps to reproduce:
- Download Eclipse 3.7.2 for Java Developers
- Launch Eclipse. Install New Software. Add Buckminster Headless site for Eclipse 3.7. Select Buckminster product
I know the Buckminster site says to use the director for the headless product but the steps listed above work perfectly fine under Eclipse 3.7.1.
The full error when those steps are tried with Eclipe 3.7.2:
Cannot complete the install because of a conflicting dependency.
Software being installed: Buckminster Product 1.4.0.v20111129-1531 (org.eclipse.buckminster.product.feature.group 1.4.0.v20111129-1531)
Software currently installed: Eclipse IDE for Java Developers 1.4.2.20120213-0813 (epp.package.java 1.4.2.20120213-0813)
Only one of the following can be installed at once:
Simple Configurator 1.0.200.v20110502-1955 (org.eclipse.equinox.simpleconfigurator 1.0.200.v20110502-1955)
Simple Configurator 1.0.200.v20110815-1438 (org.eclipse.equinox.simpleconfigurator 1.0.200.v20110815-1438)
Cannot satisfy dependency:
From: Eclipse IDE for Java Developers 1.4.2.20120213-0813 (epp.package.java 1.4.2.20120213-0813)
To: org.eclipse.epp.package.java.feature.feature.group [1.4.2.20120213-0813]
Cannot satisfy dependency:
From: Buckminster Product 1.4.0.v20111129-1531 (org.eclipse.buckminster.product.feature.group 1.4.0.v20111129-1531)
To: org.eclipse.equinox.simpleconfigurator [1.0.200.v20110502-1955]
Cannot satisfy dependency:
From: EPP Java Package 1.4.2.20120213-0813 (org.eclipse.epp.package.java.feature.feature.group 1.4.2.20120213-0813)
To: org.eclipse.platform.feature.group [3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q]
Cannot satisfy dependency:
From: Eclipse Platform 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q (org.eclipse.platform.feature.group 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q)
To: org.eclipse.rcp.feature.group [3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272]
Cannot satisfy dependency:
From: Eclipse RCP 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272 (org.eclipse.rcp.feature.group 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272)
To: org.eclipse.equinox.simpleconfigurator [1.0.200.v20110815-1438]
Any feedback is appreciated.
|
|
|
|
|
[buckminster-dev] Buckminster builds and non-greedy optional dependencies? [message #811782 is a reply to message #810522] |
Fri, 02 March 2012 15:28   |
Eclipse User |
|
|
|
As you know, p2 publisher in Eclipse 3.8 (and 4.2), since Juno M1 now
publishes runtime optional dependencies with "greedy=false".
I plan to do some tests and checks against our "common repo" to see who
might not be doing that, yet, and open bugs, or send notes to cross-project
lists with details and advice. From quick inspection, I already see some
cases of the metadata saying "opposite" things: greedy for a bundle in one
place, but not greedy for same bundle in another place ... which I'm
guessing is "not good" (at least, in most cases). Plus, many places where
optional requirements are still greedy (by default).
When I last posted to cross-project about this issue, the Tycho project
reported back:
"Tycho uses 3.8-based publisher and generates non-greedy optional
dependencies since version 0.13."
So, I am wondering about Buckminster. Once I start to test and document, is
there any advice I could give to projects that use Buckminster based
builds? Such be sure to use a version higher than such and such? Thought
I"d check "in advance" what my advice should be, if any. I'll likely send
the note/bugs next week and hope for Juno M6 we can be relatively "clean".
Your advice and help is kindly appreciated.
Thanks,
|
|
|
Re: [buckminster-dev] Buckminster builds and non-greedy optional dependencies? [message #811823 is a reply to message #811782] |
Fri, 02 March 2012 16:45  |
Eclipse User |
|
|
|
Hi David,
The 3.8/4.2 version of Buckminster (due by Juno M6) will also use the new publisher.
Regards,
Thomas Hallgren
On 03/02/2012 09:28 PM, David M Williams wrote:
>
> As you know, p2 publisher in Eclipse 3.8 (and 4.2), since Juno M1 now
> publishes runtime optional dependencies with "greedy=false".
>
> I plan to do some tests and checks against our "common repo" to see who
> might not be doing that, yet, and open bugs, or send notes to cross-project
> lists with details and advice. From quick inspection, I already see some
> cases of the metadata saying "opposite" things: greedy for a bundle in one
> place, but not greedy for same bundle in another place ... which I'm
> guessing is "not good" (at least, in most cases). Plus, many places where
> optional requirements are still greedy (by default).
>
> When I last posted to cross-project about this issue, the Tycho project
> reported back:
>
> "Tycho uses 3.8-based publisher and generates non-greedy optional
> dependencies since version 0.13."
>
> So, I am wondering about Buckminster. Once I start to test and document, is
> there any advice I could give to projects that use Buckminster based
> builds? Such be sure to use a version higher than such and such? Thought
> I"d check "in advance" what my advice should be, if any. I'll likely send
> the note/bugs next week and hope for Juno M6 we can be relatively "clean".
>
> Your advice and help is kindly appreciated.
>
> Thanks,
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03449 seconds