From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Monday, July 01, 2013 11:37 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
> 1. Riena has contributed a custom pre-release build of a Nebula component to the Kepler repository,
> unfortunately this wasn’t caught before the release, but severity of the problem means that the
> resolution cannot wait until Kepler SR1. The Planning Council should take this up.
> I recommend removing Riena from Kepler repository as the safest recovery action.
I fail to see how this is THAT bad of a problem and believe it can be fixed in SR1. Obviously, I must be missing the point of your concern.
Please open a cross-project bug explaining why this is a "rebuild" causing problem, giving concrete examples of how it impacts adopters or users,
for which there is no work-around.
Thanks,
From: "Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>
To: "'Cross project issues'" <cross-project-issues-dev@xxxxxxxxxxx>,
Date: 07/01/2013 01:47 PM
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
It’s not quite time to sideline this to bugzilla. Two major issues have been identified that need attention beyond the two involved projects.
1. Riena has contributed a custom pre-release build of a Nebula component to the Kepler repository, unfortunately this wasn’t caught before the release, but severity of the problem means that the resolution cannot wait until Kepler SR1. The Planning Council should take this up. I recommend removing Riena from Kepler repository as the safest recovery action.
2. Nebula apparently has not produced a 1.0 release despite a successful 1.0 release and graduation review almost a year ago (2012-09-12). The dashboard lists the 1.0 release on 2012-09-21. Could someone from Nebula address what happened? This is hardly the proper way for a project deserving of the mature label to behave.
- Konstantin
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Campo, Christian
Sent: Monday, July 01, 2013 1:31 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=411977 to track the discussion…. and to take it off the cross project mailing list.
christian
Von: Doug Schaefer <dschaefer@xxxxxxx>
Antworten an: Cross issues <cross-project-issues-dev@xxxxxxxxxxx>
Datum: Samstag, 29. Juni 2013 16:46
An: Cross issues <cross-project-issues-dev@xxxxxxxxxxx>, Cross issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Cross issues <cross-project-issues-dev@xxxxxxxxxxx>
Betreff: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
It would be awesome to see a release of Nebula, BTW. As we try to modernize the UI for Eclipse we're finding some nice things there.
D
From: Tom Schindl
Sent: Saturday, June 29, 2013 3:36 AM
To: Cross project issues
Reply To: Cross project issues
Cc: Cross project issues
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site |
We have not yet done any release at nebula! We have split the project, into an incubator and to-be-released components but did not yet finish it!
Tom
Von meinem iPhone gesendet
Am 28.06.2013 um 23:53 schrieb "Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>:
An official release (as defined by EDP) of an incubating project can be contributed, such as a 0.7 of something, but not a pre-release build.
Note that this distinction doesn’t apply to Nebula Grid, since Nebula has graduated from incubation status and made a 1.0 release back in 2012, so the only question is whether the bundles actually correspond to Nebula’s 1.0 release.
- Konstantin
From:cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Campo, Christian
Sent: Friday, June 28, 2013 2:19 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
to my knowledge a project can also contribute components that are still in incubator and havnt done a release yet. I am sure we asked that in the past. (EMO)
We also distributed Nebula CompositeTable in the past for a number of years and now we include the Nebula Grid.
So I disagree with "there should not be any pre-release bundle in the release train repo".
christian
Von: Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx>
Antworten an: Cross issues <cross-project-issues-dev@xxxxxxxxxxx>
Datum: Freitag, 28. Juni 2013 22:58
An: Cross issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: 'Nebula Dev' <nebula-dev@xxxxxxxxxxx>
Betreff: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
Does the version of nebular.widgets.grid in Kepler correspond to a Nebula release (not a pre-release build)?
If it does corresponds to a release, there is nothing wrong here. A project can contribute its dependencies to the release train aggregation even if those dependencies aren’t part of the release train.
If it doesn’t correspond to a release, then there is a serious problem as there shouldn’t be any pre-release bundles in Kepler.
I notice that Nebula is using 1.0.0.HEAD versioning for the bundle and it seems that the version doesn’t change from build to build. This is very wrong and may make answering the above question rather difficult. Nebula should work to fix the build ASAP.
Thanks,
- Konstantin
From:cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Campo, Christian
Sent: Friday, June 28, 2013 1:43 PM
To: Cross project issues
Cc: Nebula Dev; Cross project issues
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
Hi,
Yes riena uses the nebula gid widget and because of that we distribute it in our p2 repo.
Whats wrong with that ?
Gruesse
Christian
Am 28.06.2013 um 15:25 schrieb "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>:
Hi Tom,
I can confirm it’s riena:
$> ssh build.eclipse.org
$> cd /home/data/httpd/download.eclipse.org/releases/kepler/201306260900
$> unzip -p content.jar | grep -B 50 'require.*nebula.widgets.grid' | egrep 'unit|nebula.widgets.grid'
<unit id='org.eclipse.riena.ui.ridgets.swt.optional' version='5.0.0.v20130605_5_0_0_0'>
<required namespace='osgi.bundle' name='org.eclipse.nebula.widgets.grid' range='1.0.0'/>
</unit>
<unit id='org.eclipse.riena.tests' version='5.0.0.v20130605_5_0_0_0'>
<required namespace='osgi.bundle' name='org.eclipse.nebula.widgets.grid' range='0.0.0'/>
<required namespace='org.eclipse.equinox.p2.iu' name='org.junit' range='[4.10.0.v20120426-0900,4.10.0.v20120426-0900]'/>
<required namespace='org.eclipse.equinox.p2.iu' name='org.eclipse.nebula.widgets.grid' range='[1.0.0.HEAD,1.0.0.HEAD]'/>
</unit>
<unit id='org.eclipse.riena.example.client.optional' version='5.0.0.v20130605_5_0_0_0'>
<required namespace='osgi.bundle' name='org.eclipse.nebula.widgets.grid' range='1.0.0'/>
I don’t know from what repository riena (or the aggregator) pulls in the odd version.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Schindl
Sent: Friday, June 28, 2013 3:08 PM
To: Nebula Dev
Cc: Cross project issues
Subject: Re: [cross-project-issues-dev] [nebula-dev] Nebula Grid is available from Kepler update site
Wild guess is that one of the release train projects uses it - IIRC riena used to use it.
Tom
On 28.06.13 13:51, Wim Jongman wrote:
> Hi,
>
> Apparently the Nebula Grid widget is available from the Kepler Update
> site. This should not be the case.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=411867
>
> Regards,
>
> Wim
>
>
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<ATT00001.c>
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
