Markus,I agree about dropping Carbon builds for EPP packages. It was discussed in the "We need Cocoa 64-bit packages" bug (starting in https://bugs.eclipse.org/bugs/show_bug.cgi?id=281501#c17 ). Ian's objection was that dropping Carbon in Galileo provided no transition for products that are dependent on Carbon; I think it's worthy of bringing up again now that Galileo has had Cocoa64 packages for a while.
Anyone else have any thoughts or opinions?
Eric
On Dec 18, 2009, at 9:38 AM, Markus Knauer wrote: Yes, my opinion is that we just remove the carbon-ppc packages and leave all others as they are. I always thought about dropping EPP build support for this platform in Helios, maybe this is a coincidence?
Regards,
Markus
2009/12/17 David M Williams <david_williams@xxxxxxxxxx>
Thanks for the report, Christian. I have opened bug 298107 to capture this issue.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=298107
It would be interesting to know if this is JEE package only, or
other packages for carbon.ppc, or ... other mac OS packages?!
(Sorry, I can't test myself).
I have tested Java EE and _javascript_ package on Windows x86 and Linux x86 .... and I'll approve those.
Markus, I assume we could promote all the packages except for carbon ppc? (That is, we don't have
to leave out all of Java EE because of one platform, right?)
Hi,
I'm not a package maintainer but nevertheless went ahead and downloaded 20091217-0920_eclipse-jee-helios-M4-macosx.carbon.ppc.tar.
There is something wrong with this: the config.ini does not contain the simpleconfigurator and instead lists all bundles.
Also the package does not start:
!SESSION 2009-12-17 17:37:50.389 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_17
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/cdupuis/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws carbon -arch x86 -product org.eclipse.epp.package.jee.product -keyring /Users/cdupuis/.eclipse_keyring -showlocation
!ENTRY org.eclipse.osgi 4 0 2009-12-17 17:37:52.365
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:367)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:611)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:566)
at org.eclipse.equinox.launcher.Main.run(Main.java:1363)
Christian
On 17 Dec 2009, at 16:34, Markus Knauer wrote:
> Hi package maintainers,
>
> there is a build available for Helios M4 with all the packages except the modeling one which has some unresolved dependencies because there are some features missing in the upstream Helios p2 repository.
>
> See http://www.eclipse.org/epp/download.php - build 20091217-0920
>
> Please do some sanity testing on this build and report if there are serious errors as soon as possible or if everything is fine. If it is a no-go for your package then I have only one alternative: Remove it from the list of download packages.
>
> The Helios schedule is quite tight... actually, it means that there is only a very short time slice between the Helios repository build and the "final" EPP package build, i.e. the repo should be available Wednesdays, the EPP packages on Thursday to give them enough time to be copied to the Eclipse mirrors and to make them available on Friday. That means that with the next milestone M5 we need more testing during the release week, otherwise we do not have many possibilities to rebuild the packages.
>
> For now (M4):
> Today/Thursday - EPP packages available for testing and copied to the download area
> Tomorrow/Friday - packages available (or not...)
>
> In the future (M5...):
> Monday-Wednesday - continuous package builds available for testing
> Thursday - final package build, final testing, and *final approval*
> Friday - release of the packages
>
> Regards,
> Markus
>
> <ATT00001.c>
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Markus Knauer
EclipseSource
### phone: +49 721 664 733 0 (GMT +2)
### fax: +49 721 664 733 29
### web: www.eclipsesource.com
Innoopract Informationssysteme GmbH
Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
|
