Re: [cross-project-issues-dev] Status and outlook for Juno SR2 RC3 (CDO late because of Hudson problems)

Am 06.02.2013 08:11, schrieb Matthias Sohn: I restarted slave1, Thank you! it seems now your build fails due to another reason: https://hudson.eclipse.org/hudson/job/emf-cdo-maintenance/512/console Yeah, that was the other problem I mentioned. Wiping the wokspace and kicking a build worked a

Re: [cross-project-issues-dev] Status and outlook for Juno SR2 RC3 (CDO late because of Hudson problems)

2013/2/6 Eike Stepper > Hi, > > I've not been able to build CDO for SR2 RC3, yet, because of Hudson or > Buckminster problems. > > hudson-slave1 seems to reject external p2 repositories for our > dependencies: https://hudson.eclipse.org/**hudson/job/emf-cdo-** > maintenance/509/console

Re: [cross-project-issues-dev] Status and outlook for Juno SR2 RC3 (CDO late because of Hudson problems)

Hi, I've not been able to build CDO for SR2 RC3, yet, because of Hudson or Buckminster problems. hudson-slave1 seems to reject external p2 repositories for our dependencies: https://hudson.eclipse.org/hudson/job/emf-cdo-maintenance/509/console After wiping out the job workspace the build han

[cross-project-issues-dev] Status and outlook for Juno SR2 RC3

We would be in good shape, except I accidentally removed ../releases/maintenance (too much automation that depend on tiny buttons on web interfaces :) Apologies. I'll have it updated again by around midnight (Eastern time). I also noticed Scout had been disabled previously due to a RAP problem,

Re: [cross-project-issues-dev] Status and outlook for Juno SR1 RC3 +0

The m2m-atl issue should be fixed now, sorry for the inconvenience. I fixed the URL and re-enabled the atl contribution. I will now re-enable jwt and modisco for the next aggregation build. Regards, William Le 08/09/2012 03:49, David M Williams a écrit : I contributed the Eclipse Project cont

[cross-project-issues-dev] Status and outlook for Juno SR1 RC3 +0

I contributed the Eclipse Project contribution for RC3, and in doing so, had to do the usual disablement of rap runtime which due to dependencies required disablement of scout A little different that usual, it seemed there is a missing repo (wrong url?) for m2m-atl so disabled that, which

Re: [cross-project-issues-dev] Status and outlook for Juno SR1 RC1

Hi David, just to inform you that Mylyn Intent (mylyn-docs-intent.b3aggrcon) will not contribute to Kepler M1 because we still rely on EMF Compare 1 . We're planning to use EMF Compare 2 soon, and will join the Kepler release once this will be done. Best regards, Alex Le 22/08/2012 06:42, Da

[cross-project-issues-dev] Status and outlook for Juno SR1 RC1

As far as I can tell, there are two disabled contributions or features for SR1 RC1. emf-query2.b3aggrcon - org.eclipse.simrel.build soa-bpel.b3aggrcon - org.eclipse.simrel.build Now, emf-query2 I know was not in Juno SR0, but I recall some mention "maybe it'd rejoin in SR1". If this is the pl

Re: [cross-project-issues-dev] Status and Outlook for Juno!

arou Fukuda, Ph.D. > IBM Research - Tokyo > Tel: +81-3-5144-2852 > E-mail: kenta...@jp.ibm.com > > > > From: David M Williams > To: Cross project issues > Date: 2012/06/14 06:41 > Subject:Re: [cross-project-issues-dev] Status and Outlook for > Juno!

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Cross project issues Date: 2012/06/14 06:41 Subject: Re: [cross-project-issues-dev] Status and Outlook for Juno! Sent by:cross-project-issues-dev-boun...@eclipse.org Ah ... estimate high so you can deliver ahead of schedule, eh? :) I stopped the build that was in progress

Re: [cross-project-issues-dev] Status and Outlook for Juno!

roblem, let me know, and I'll restart the build again ... if its before 6:30 AM or so. Otherwise, will let current one finish.] Thanks, From: Holger Staudacher To: Cross project issues , Date: 06/13/2012 05:31 PM Subject: Re: [cross-project-issues-dev] Status and Outloo

Re: [cross-project-issues-dev] Status and Outlook for Juno!

ss project issues , > Date:06/13/2012 04:45 PM > Subject: Re: [cross-project-issues-dev] Status and Outlook for Juno! > Sent by:cross-project-issues-dev-boun...@eclipse.org > > > > Or in an hour and a half. I just landed at the airport. Give me some ti

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Date: 06/13/2012 04:45 PM Subject:Re: [cross-project-issues-dev] Status and Outlook for Juno! Sent by:cross-project-issues-dev-boun...@eclipse.org Or in an hour and a half. I just landed at the airport. Give me some time until I find a sufficient network connection (eclip

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Or in an hour and a half. I just landed at the airport. Give me some time until I find a sufficient network connection (eclipse p2 repositories need speed) ;) Sorry for the delay. Cheers Holger On Jun 13, 2012, at 10:10 PM, Ralf Sternberg wrote: > The old org.eclipse.rap bundles come from RT

Re: [cross-project-issues-dev] Status and Outlook for Juno!

The old org.eclipse.rap bundles come from RTP. Holger will update the RTP contribution in about an hour. Regards, Ralf On Wed, Jun 13, 2012 at 4:30 PM, Dennis Hübner wrote: > > Am 13.06.2012 um 16:13 schrieb Ralf Sternberg: > > For the duplicate org.eclipse.rap.* bundles, 1.5.0.20120612-1458 our

Re: [cross-project-issues-dev] Status and Outlook for Juno!

> Wayne Beaton > Sent by: cross-project-issues-dev-boun...@eclipse.org > I took a quick look at a couple of the Virgo features and the Gemini > Web feature, and they seem to be okay with regard to licenses. The > feature.properties file is included, it has the "license" key (the > build file is

Re: [cross-project-issues-dev] Status and Outlook for Juno!

found one to open bugs, etc. From: Wayne Beaton To: cross-project-issues-dev@eclipse.org, Date: 06/13/2012 01:14 PM Subject: Re: [cross-project-issues-dev] Status and Outlook for Juno! Sent by:cross-project-issues-dev-boun...@eclipse.org Thanks for the summary, Jo

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Thanks for the summary, John. On 06/13/2012 09:45 AM, John Arthorne wrote: > 2) 10 features with no license (in particular their license is the > string "%license"). 1 from Virgo, 9 from Gemini. The most common cause > of this is missing key in feature.properties file, or the > feature.properties

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Konstantin Komissarchik wrote on 06/13/2012 10:14:52 AM: > Re: [cross-project-issues-dev] Status and Outlook for Juno! > > > It looks like this dependency is coming from RT packaging, not Saphire: > > That makes more sense. All Sapphire dependencies are written very > b

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Am 13.06.2012 um 16:13 schrieb Ralf Sternberg: > For the duplicate org.eclipse.rap.* bundles, 1.5.0.20120612-1458 our > RC4 contribution, 20120605-1606 is RC3. I guess someone depending on > the rap runtime has not picked up the RC4 yet, could that be EMF? We include any rap bundles or features,

Re: [cross-project-issues-dev] Status and Outlook for Juno!

so: Thanks, - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Paul Webster Sent: Wednesday, June 13, 2012 7:02 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Status and Outlook for J

Re: [cross-project-issues-dev] Status and Outlook for Juno!

For the duplicate org.eclipse.rap.* bundles, 1.5.0.20120612-1458 our RC4 contribution, 20120605-1606 is RC3. I guess someone depending on the rap runtime has not picked up the RC4 yet, could that be EMF? The duplicate org.eclipse.jetty.xml bundles come from the rap tools. For some reason, they con

Re: [cross-project-issues-dev] Status and Outlook for Juno!

On Wed, Jun 13, 2012 at 9:45 AM, John Arthorne wrote: > org.eclipse.core.commands > 3.6.1.v20120521-2332 > It looks like this dependency is coming from RT packaging, not Saphire: org.eclipse.rtp.package.feature.group - RT Package - Eclipse RTP - 1.0.0.v20120606-1022 Maybe compiling ag

Re: [cross-project-issues-dev] Status and Outlook for Juno!

Hey all, Just updated the Virgo contribution. The mentioned above reports should be fine now. Waiting on the new reports... Thanks, Bobby On Wed, Jun 13, 2012 at 4:45 PM, John Arthorne wrote: > David Williams wrote on 06/12/2012 05:15:26 PM: > > > > I appreciate everyone keeping the "build gree

Re: [cross-project-issues-dev] Status and Outlook for Juno!

David Williams wrote on 06/12/2012 05:15:26 PM: > > I appreciate everyone keeping the "build green" and making progress > on the "sim rel reports" [1], though there are a few serious issues > left there. > > [1] http://build.eclipse.org/juno/simrel/reporeports/ I looked through these, and at

[cross-project-issues-dev] Status and Outlook for Juno!

24 hours left! I appreciate everyone keeping the "build green" and making progress on the "sim rel reports" [1], though there are a few serious issues left there. Just wanted to remind everyone that after RC4 (which ends tomorrow, Wednesday, at 5 PM, unless someone asks for a few extra hours)

Re: [cross-project-issues-dev] Status and outlook for Juno RC1: How much trouble are we in?

Hi David, all, I am sorry, I made a change in the agregator, but it seems my new updates sites do not have the right MD5. And I don't understand, since I did not change my Maven-signing-plugin configuration. I am doing one last try, and then I was about to email you about this (or about to res

[cross-project-issues-dev] Status and outlook for Juno RC1: How much trouble are we in?

Here it is, nearly 5 PM on +3 day, and we haven't had a green build all day!? I've been assuming people were tending to the issues and fixing things up ... but ... without some quick communication here, I'm going to start disabling projects in order to get a good build. Please let us know if som

Re: [cross-project-issues-dev] Status and outlook for Juno M5

t; > enabled="false"/> > > versionRange="7.1.0.201110312222" enabled="false"> > > Thanks, > > > > > From: David M Williams/Raleigh/IBM@IBMUS > To: Cross project issues , > Date: 02/01/2012 09:22 PM > Subjec

Re: [cross-project-issues-dev] Status and outlook for Juno M5

ues , Date: 02/01/2012 09:22 PM Subject: [cross-project-issues-dev] Status and outlook for Juno M5 Sent by:cross-project-issues-dev-boun...@eclipse.org Still having windowbuilder problems (in Juno and Indigo) waiting to hear from Mark. Hopefully fixable in next few hours? Konstan

[cross-project-issues-dev] Status and outlook for Juno M5

Still having windowbuilder problems (in Juno and Indigo) waiting to hear from Mark. Hopefully fixable in next few hours? Konstantin, it is automatic if you change your b3aggrcon file (which you did) and in fact your contribution built successful in build 241. https://hudson.eclipse.org/hudson/vi

Re: [cross-project-issues-dev] Status and outlook for Juno M3, nearing end of +1 day

EEF M3 contribution commited, should be picked up for next build. cheers, Le 07/11/2011 22:33, David M Williams a écrit : Things are looking pretty good ... which means I was able to coax out a green build, hacking in a few "quick fixes" and disable a few contributions. I've opened bugs where

Re: [cross-project-issues-dev] Status and outlook for Juno M3, nearing end of +1 day

The riena build is nearly finished. I upload an reenable it tomorrow morning. christian Am 07.11.2011 um 22:33 schrieb David M Williams: Things are looking pretty good ... which means I was able to coax out a green build, hacking in a few "quick fixes" and disable a few contributions. I'v

[cross-project-issues-dev] Status and outlook for Juno M3, nearing end of +1 day

Things are looking pretty good ... which means I was able to coax out a green build, hacking in a few "quick fixes" and disable a few contributions. I've opened bugs where I made a "quick fix" and will remind everyone that the following projects still have disabled features or repositories. Som