Re: [cross-project-issues-dev] Eclipse IDE 2024-06 Project Participation Page

[Markus Knauer via cross-project-issues-dev]

Hi Wayne,

for Eclipse RAP it will be version 3.29.

Thanks and regards
Markus

On Thu, 23 May 2024 at 11:08, DEVILLE Pauline via cross-project-issues-dev <
cross-project-issues-dev@eclipse.org> wrote:

> Hello Wayne and all,
>
>
>
> Papyrus will also participate to 2024-06 and will contribute a 6.7.0
> version :
> https://projects.eclipse.org/projects/modeling.mdt.papyrus/releases/6.7.0
>
>
>
> Best regards,
>
> Pauline DEVILLE
>
>
>
> *De :* cross-project-issues-dev <
> cross-project-issues-dev-boun...@eclipse.org> *De la part de* Wayne
> Beaton via cross-project-issues-dev
> *Envoyé :* mercredi 22 mai 2024 23:56
> *À :* Cross project issues 
> *Cc :* Wayne Beaton 
> *Objet :* [cross-project-issues-dev] Eclipse IDE 2024-06 Project
> Participation Page
>
>
>
> Greetings folks!
>
>
>
> I've assembled the release information for participating projects here
> .
>
>
>
> Note that the list of projects reflects our long time practice of only
> including projects whose teams are actively participating in the
> simultaneous release. If you look hard enough, you'll notice that projects
> that have been "sponsored in" by participating projects are absent from the
> list. This is per the requirements. I expect that these requirements will
> change in some future release.
>
>
>
> A lot of the releases are quite old, and based on the activity in the
> simrel.build 
> repository,  at least a few projects need to create some release records,
> and some may need to engage in a progress review (I've done my usual thing
> of making by best guess based on the release records in the system).
>
>
>
> If your project is contributing a different release than what you see
> here, please ensure that you've created a release record
> , and
> let me know. If your project has not engaged in a progress (or release)
> review  in
> more than one year, please engage with the EMO ASAP to schedule a review.
>
>
>
> Be sure to set the New and Noteworthy URL in your release record: it is
> through this relationship that we build the aggregate N
>
>
>
> Please make sure that you've made your best effort to engage in the IP Due
> Diligence Process for all third party content before you engage with the
> EMO for review. Bear in mind that you should be engaging in the IP Due
> Diligence Process
>  on an ongoing
> basis and that all releases (regardless of whether or not they correspond
> with a progress or release review) must only contain content that has been
> vetted through the due diligence process. With the Eclipse Dash License
> Tool  and the ability to use it
> to automatically create review requests, it should be *easier than ever*
> before to engage (the README has extensive information on how to engage,
> and does include some pointers for using it with Eclipse Tycho
> -based builds).
> Connect with the EMO if you need assistance.
>
>
>
> Here are some things that I've observed:
>
>
>
> Eclipse Client Platform has been removed.
>
>
>
> The aggrcon files for the following projects are disabled; if any of these
> projects are dropping from the release, please let me know:
>
>- Eclipse Xpand
>- Eclipse BPMN2 Modeler Project
>- Eclipse RCPTT
>
> Let me know what I've missed.
>
>
>
> Thanks,
>
>
>
> Wayne
>
> --
>
> *Wayne Beaton*
>
> *Director of Open Source Projects | **Eclipse Foundation*
>
>
>
> My working day may not be your working day! Please don’t feel obliged to
> read or reply to this e-mail outside of your normal working hours.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (UTC +1)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Staging for SimRel 2023-06 M1 is Complete

[Markus Knauer]

Good Morning everyone,

I didn't notice that earlier, sorry for that.

Yes, we (RAP) didn't contribute an M1 build yet, mostly because it is not
yet ready with the many required Java, Maven, Tycho version changes, and
some of our test cases are still failing.
Therefore I created change 201201
 in
Gerrit that temporarily disables our contribution together with the
dependent single EMF-RAP feature for M1. If a respin is okay I would
proceed and merge that change.

Thanks
Markus



On Thu, 13 Apr 2023 at 08:45, Ed Merks  wrote:

> FYI,
>
> As I was about to send out the note below, but I thought, let me have look
> at the reported duplicates:
>
>
> https://download.eclipse.org/staging/2023-06/buildInfo/archive/download.eclipse.org/staging/2023-06/
>
> Oh my goodness, up to 55!  Worse still, there are two versions of Jetty
> and even two versions of some of the Platform's bundles:
>
> Why is that?
>
> RAP needs the older version because it has not contributed a new build for
> M1.  Nor can I find a more recent build than the 3.24 release here:
>
> https://download.eclipse.org/rt/rap/
>
> I'm not sure the resulting repository is really consumable for EPP.
> Certainly the RAP package is unlikely to work...
>
> So I suspect a respin will be needed...
>
> __
>
> The staging repository content of
>   https://download.eclipse.org/staging/2023-06/
>
> has been promoted to the following repository for 2023-06 M1:
>
>   https://download.eclipse.org/releases/2023-06 /202304141000/
>
> This is ready for consumption by EPP.
>
> Baring a respin, it will become visible in the composite as scheduled
> Friday April, 14th, 2023:
>
>   https://download.eclipse.org/releases/2023-06
>
> Regards,
> Ed
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Databinding api deletion - ACTION REQUIRED by some projects

[Markus Knauer]

In case someone is only reading this mail thread... (sorry for
cross-posting and the noise):

The required implementation is now (with RC2) available in RAP.
See issue #91 No jface.databinding.swt.typed package?
 for the details.

Thanks and regards
Markus

On Sun, 27 Nov 2022 at 18:32, Jonah Graham  wrote:

> Thanks Zoltán for looking into it. Glad to hear that there is no need for
> a new version of VIATRA for 2022-12.
>
> Jonah
>
> On Sun, Nov 27, 2022 at 6:54 AM Zoltán Ujhelyi <
> zoltan.ujhe...@incquerylabs.com> wrote:
>
>> Hi,
>>
>> thanks Jonah for taking the time to check all projects.
>>
>> For VIATRA I have checked the usage, and found that it is a dead code
>> that should be removed, but do not cause issues (and I have manually
>> checked that the related wizard works in 2022-12).
>>
>> In bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=581130 we will
>> remove it from the codebase but we won’t provide any new binaries for
>> SimRel.
>>
>> Best regards,
>> Zoltan
>>
>> On 2022. Nov 27., at 3:20, Jonah Graham  wrote:
>>
>> Hi folks,
>>
>> Eclipse Platform removed some of the previously deprecated databinding
>> APIs in the upcoming release. See
>> https://github.com/eclipse-platform/eclipse.platform.ui/pull/323 for
>> specifics.
>>
>> After seeing email
>> 
>> from Lorenzo, and knowing that CDT only just removed
>>  references to the deleted
>> classes in the last couple of months I was wondering if SimRel contained
>> any other references to the now deleted classes as this will cause runtime
>> exceptions.
>>
>> The following projects seem to have such references:
>>
>> bpmn2.modeler
>> dltk
>> emf.compare
>> emf.parsley
>> rap
>> rcptt
>> viatra
>> xwt
>>
>> See attached files for the specific classes that reference the removed
>> API. I did the analysis by disassembling all the class files in all of
>> SimRel and searching for the removed classes.
>>
>> Jonah
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> --
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (UTC +1)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] RAP and the new jface.databinding.swt.typed.WidgetProperties

[Markus Knauer]

Hi everyone,

just to close the loop...

The required implementation is now (with RC2) available in RAP.
See issue #91 No jface.databinding.swt.typed package?
 for the details.

Thanks and regards
Markus

On Sat, 26 Nov 2022 at 12:17, Ivan Furnadjiev 
wrote:

> Hi,
>
> RAP has a forked "org.eclipse.rap.jface.databinding", which was not
> updated to the latest platform code.
> See issue 91 
> for more details.
>
> Best regards,
> Ivan
>
> On Sat, Nov 26, 2022 at 1:12 PM Jens Lideström  wrote:
>
>> Hm!
>>
>> This package is located in the same bundle as the old and deprecated
>> class org.eclipse.jface.databinding.swt.WidgetProperties.
>>
>> The new package should be provided in every release for maybe the last 3
>> years, since 2019-06, Platform version 4.12, bundle version 1.9.0. And
>> certainly in all releases where the old version is deprecated.
>>
>> It surely must exist in RAP also!
>>
>> Are you sure you're not using a really old target platform when you are
>> compiling?
>>
>> Does your target platform include bundle org.eclipse.jface.databinding
>> version 1.9.0 or later?
>>
>> /Jens
>>
>>
>>
>> On 2022-11-25 20:18, Lorenzo Bettini wrote:
>> > Hi
>> >
>> > I seem to understand that the old deprecated databinding classes have
>> been removed in 2022-12, and so I switched to
>> org.eclipse.jface.databinding.swt.typed.WidgetProperties.
>> >
>> > However, RAP does not provide this package, does it?
>> > Or is it going to provide it before the finale 2022-12 release?
>> >
>> > thanks in advance
>> >  Lorenzo
>> >
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (UTC +1)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2022-09 Participation

[Markus Knauer]

...and RAP (Remote Application Platform) will deliver a 3.22.0
.
The release record is now available.

Thanks
Markus

On Wed, 31 Aug 2022 at 06:29, Dietrich, Christian <
christian.dietr...@itemis.de> wrote:

>
> Xtext version is 2.28
> Wayne Beaton  schrieb am Mi. 31.
> Aug. 2022 um 05:27:
>
>> Greetings folks!
>>
>> I've assembled my first pass at the Eclipse IDE 2022-09 participation
>> page .
>>
>> Please have a look to ensure that I've captured the release version of
>> your project correctly. If you're contributing a new release, please be
>> sure to create the release record.
>>
>> You may notice that Maven Integration for Web Tools Platform is dropped
>> from the project list. That project was terminated and its resources were
>> merged into Maven Integration.
>>
>> Some anomalies that I've noticed:
>>
>>- The Eclipse Platform release record has not been created yet;
>>- Eclipse ACTF's aggrcon is disabled;
>>- Eclipse PDT's aggrcon is disabled; and
>>- Eclipse DLTK's aggrcon is disabled.
>>
>> Can a committer from Eclipse Platform please create the release record?
>>
>> Regarding the disabled contributions... Can a representative from the
>> corresponding project committers please let us know if you are engaged
>> working on getting these contributions back into an enabled state?
>>
>> If your project is contributing a new major or minor release to 2022-09
>> and you haven't engaged in a release or progress review in the year leading
>> up to your release date, please engage with the EMO ASAP.
>>
>> Remember that, regardless of whether or not a review is required, any
>> intellectual property included in any release must be fully vetted. If you
>> have not already done so, I recommend that you check out the Eclipse Dash
>> License Tool to identify any gaps in the vetting of your third-party
>> dependencies; look especially at the Automatic IP Team Review Requests
>> 
>> feature.
>>
>> Thanks,
>>
>> Wayne
>> --
>>
>> Wayne Beaton
>>
>> Director of Open Source Projects | Eclipse Foundation
>>
>>
>> My working day may not be your working day! Please don’t feel obliged to
>> read or reply to this e-mail outside of your normal working hours.
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> --
> Christian Dietrich (Diplom-Informatiker (BA))
> Softwareentwickler / -Architekt
> Committer and Co-Lead for Eclipse Xtext
>
> Tel.: +49 (0) 711 / 34 21 91-0
> Fax.: +49 (0) 711 / 34 21 91-29
> Mobil: +49 (0) 151 / 173969 17
> Mail: christian.dietr...@itemis.de
> XING: https://www.xing.com/profile/Christian_Dietrich8
> Web: http://www.itemis.de
> Skype: christiandietrich1982
>
> itemis AG
> Niederlassung Süd
> Industriestraße 6
> 70565 Stuttgart
>
> Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle,
> Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef Schuermann
> Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald
> Goertz, Eric Swehla
> Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen
> (Germany)
> Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [epp-dev] EPP 2022-09 M1

[Markus Knauer]

+1 for RCP/RAP package (on Linux x86)

My first tests (startup, creation of a sample RAP plugin project,
downloading target platform, etc.) were successful, although I found some
expected problems in the RAP Tooling that we need to fix for M2, e.g. the
list of plugins that we are automatically adding to a launch configuration
is wrong because of changes in the OSGi bundle dependencies.

Thanks
Markus

On Fri, 15 Jul 2022 at 09:56, Ed Merks  wrote:

> Jonah,
>
> I fix the problem in the aggregator (a *.pack.gz is no longer processable
> by the latest p2 but the aggregator was treating it as the canonical
> artifact instead of the *.jar as it should), built a  new version of
> staging using the fixed aggregator, and promoted staging to:
>
>   https://download.eclipse.org/releases/2022-09/202207151001
>
> Note the 20220715100*1* versus 20220715100*0*.
>
> I also changed the script that composes the release composite such that it
> only contains the (one) most recent child, so the broken 202207151000 will 
> *not
> *be in the composite when it's made visible later today as scheduled.
>
> While testing the installer, I made the mistake of creating an
> installation that uses Java 11 and of course the tm4e bundles don't start
> in that case.  So I changed all the product definitions to require Java 17:
>
>   https://git.eclipse.org/r/c/epp/org.eclipse.epp.packages/+/194724
>
> The train also contains some really old content so that these certificate
> prompts come up for such very old certificates:
>
> When installing everything, I see wiring problems that appear to be caused
> by multiple versions of com.google.inject (two versions on the train) and
> com.google.gson (three versions  on the train).  In particular these
> failures:
>
> I'll need to investigate these further.
>
> But if you see your project above, it's better to use the latest version
> to avoid this possible installation configuration with multiple versions:
>
> We're doing poorly on duplicates with this now:
>
> And this in 2022-06:
>
> And as we see above, this can and does lead to wiring problems in some
> cases...
>
> Regards,
> Ed
>
>
> On 15.07.2022 02:52, Jonah Graham wrote:
>
> Hi everyone,
>
> Our next milestone build is available for testing: EPP 2022-09 M1
>
> *While the EPP is ready for testing, please see the email I sent to
> cross-project-issues-dev
> 
> about my concern with the SimRel repo contents. There may be more
> consequences than what I have highlighted in that email that we are not
> familiar with yet.*
>
> I have been following the steps on
> https://hackmd.io/@jonahgraham/eclipse-epp-release-process - you can see
> the checkmarks as to what is done.
>
> Download link:
> https://download.eclipse.org/technology/epp/downloads/release/2022-09/M1/_mirrors.php
>
> EPP was built with the p2 repositories at:
>
> https://download.eclipse.org/releases/2022-09/202207151000/ and
> https://download.eclipse.org/technology/epp/packages/2022-09/202207141200/
>
> Please test and send your +1 to this mailing list. +1s are optional as the
> package will be published anyway.
>
> Last +1 received for each package and platform (apologies if I missed one
> of your +1 emails, just let me know and I will update Last Recorded +1)
>
> Packages:
> committers - 2022-06 RC2
> cpp - 2022-06 RC2
> dsl - 2022-06 RC2
> embedcpp - 2022-06 RC2
> java - 2022-06 RC2
> jee - 2022-06 RC2
> modeling - 2022-06 M3
> parallel - 2022-03 RC2
>
> *php - 2020-12 RC2 (tested by Ed in 2022-03 RC2) *rcp - 2022-06 RC2
> scout - 2022-06 RC1
>
> Platforms:
> Linux x86_64 - 2022-06 RC2
> Linux aarch64 - 2022-06 RC2
> Windows - 2022-06 RC2
> macOS x86_64 - 2022-06 RC2
> macOS aarch64 - 2022-06 RC2
>
> Thank you for testing!
>
> Regards,
> Jonah
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
> ___
> epp-dev mailing listepp-...@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/epp-dev
>
> ___
> epp-dev mailing list
> epp-...@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/epp-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ACTION REQUIRED from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the status on removing slf4j 2.0.0 alpha

[Markus Knauer]

Our RAP update was successful, I tested it against the Platform rebuild,
and submitted it to the SimRel p2 repository.

Thanks
Markus

On Sat, 12 Jun 2021 at 06:01, Nitin Dahyabhai  wrote:

> It's possible that our own update didn't work its way through as I
> thought. Rebuilding.
>
> On Sat, Jun 12, 2021 at 12:00 AM Nitin Dahyabhai 
> wrote:
>
>> We use https://download.eclipse.org/eclipse/updates/4.20-I-builds/ ; it
>> would have shown up there, yes?
>>
>> On Fri, Jun 11, 2021 at 11:16 PM Jonah Graham 
>> wrote:
>>
>>> Hi Nitin
>>>
>>> There is something amiss about the contribution,
>>> https://download.eclipse.org/webtools/downloads/drops/R3.22.0/S-3.22.0.RC3-20210612014426/repository
>>> has a mixture of snapshot and non snapshot jetty bundles. The snapshot ones
>>> look like the ones that platform produced for the test build yesterday.
>>>
>>> Did webtools rc3 use platform RC2 final repo as input?
>>>
>>> Thanks,
>>> Jonah
>>>
>>> On Fri., Jun. 11, 2021, 22:29 Nitin Dahyabhai, 
>>> wrote:
>>>
 WTP's RC3 (there was a small code change that had to be made to use the
 new SLF4J API bundle name) is now contributed, and our Jetty 10.0.5 site
 should be the only one anyone else refers to in their build if they're
 using it--it will not be contributed. We are pulling in the SLF4J API
 bundle into our main site, which is contributed via the aggrcon file.

 On Fri, Jun 11, 2021 at 8:37 PM Jonah Graham 
 wrote:

> Thanks Kit and Nitin,
>
> At the moment the aggregator is broken because the temporary repo that
> simrel pointed to for webtools to test Jetty 10.0.5 snapshot is not
> available anymore. This will be resolved once webtools update their
> contribution. Let me know if there is anything I can do to help.
>
> Thanks folks.
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
>
> On Fri, 11 Jun 2021 at 19:19, Nitin Dahyabhai 
> wrote:
>
>> WTP's Jetty site is ready, the rest of WTP needs a gerrit merged and
>> then some time to build.
>>
>> --
>> Regards,
>> Nitin Dahyabhai
>> Eclipse WTP PMC
>> --
>>
> Regards,
 Nitin Dahyabhai
 Eclipse WTP PMC

>>>
>>
>> --
>> Regards,
>> Nitin Dahyabhai
>> Eclipse WTP PMC
>>
>
>
> --
> Regards,
> Nitin Dahyabhai
> Eclipse WTP PMC
>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ACTION REQUIRED from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the status on removing slf4j 2.0.0 alpha

[Markus Knauer]

;>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 9 Jun 2021 at 16:56, Ondrej Dockal 
>>>>>>> wrote:
>>>>>>>
>>>>>>> Jonah, thanks for taking care of this. If we will revert it after
>>>>>>> RedDeer is pushed, I think it is safe to give it a try. Also, If Jetty
>>>>>>> should be built somewhere with a fix it might provide a space for 
>>>>>>> updating
>>>>>>> all deps in all project, though, in quite late time.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jun 9, 2021 at 10:45 PM Jonah Graham 
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Ondre/Nitin,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/181738
>>>>>>> decouples the reddeer contribution from webtools which means if you 
>>>>>>> think
>>>>>>> it is ok you can merge that so reddeer can be merged.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Jonah
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ~~~
>>>>>>> Jonah Graham
>>>>>>> Kichwa Coders
>>>>>>> www.kichwacoders.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 9 Jun 2021 at 16:25, Jonah Graham 
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Ondrej,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> AFAICT the problem is that WTP is also pulling in org.slf4j 2.0 from
>>>>>>> reddeer.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 15:53:01 [0]Missing requirement: Jetty :: JNDI Naming 10.0.4
>>>>>>> (org.eclipse.jetty.jndi 10.0.4) requires 'java.package; org.slf4j
>>>>>>> [2.0.0,3.0.0)' but it could not be found
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> So because you are (correctly) removing slf4j 2.0, it is
>>>>>>> unintentionally breaking WTP.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Nitin is working on fixing up the WTP contribution. I don't think
>>>>>>> there is actually anything wrong with reddeer's contribution, we just 
>>>>>>> need
>>>>>>> a resolution of WTP first.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I will push a patch that verifies the above in a moment.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jonah
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ~~~
>>>>>>> Jonah Graham
>>>>>>> Kichwa Coders
>>>>>>> www.kichwacoders.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, 9 Jun 2021 at 16:15, Ondrej Dockal 
>>>>>>> wrote:
>>>>>>>
>>>>>>> Unfortunately, I am still not able to pass aggregator validation,
>>>>>>> this time it is jetty complaining about missing org.slf4j [2.0.0,3.0.0) 
>>>>>>> as
>>>>>>> can be seen in [1]. I am not really sure about what I can do about it
>>>>>>> from my side. There is a reopened bugzilla [2] and PR on jetty project 
>>>>>

Re: [cross-project-issues-dev] ACTION REQUIRED from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the status on removing slf4j 2.0.0 alpha

[Markus Knauer]

Just to double-check: My understanding is that we are using Jetty 10.0.5-
*snapshot* for "early" testing in order to get some confidence that
everything will work with the final Jetty 10.0.5 build. But our plan is to
deliver the final Jetty 10.0.5 build, i.e. not the snapshot. Is that
assumption correct?

Thanks
Markus

On Thu, 10 Jun 2021 at 21:54, Jonah Graham  wrote:

> The simrel aggregator is reenabled (thanks Fred!), let's test the snapshot
> there to give maximum confidence that what we have works.
>
> BTW to other projects not involved in this respin activity, please
> continue to hold off changing simrel until after the release.
>
> Thanks,
> Jonah
>
> On Thu., Jun. 10, 2021, 15:15 Jonah Graham, 
> wrote:
>
>> Hi Nitin,
>>
>> You can/should revert the change at the same time you provide a WTP build
>> with Jetty 10.0.5 (snapshot or not).
>>
>> I can run the test locally, or we can all contribute our snapshot version
>> to simrel and test there.
>>
>> @Frederic Gurr  has disabled the
>> build, until it is reenabled we'll have to test locally and I am happy to
>> do that.
>>
>> Thanks,
>> Jonah
>>
>>
>> On Thu., Jun. 10, 2021, 14:56 Nitin Dahyabhai, 
>> wrote:
>>
>>> I'm doing a build against the 10.0.5 snapshot. The
>>> corresponding WTP jetty site has been updated to not have the SLF4J API
>>> bundle in it. Yesterday we added the 10.0.4 site to the webtools.aggrcon to
>>> provide the slf4j 2.0.0 alpha1 and unblock others; should I remove that
>>> from the aggrcon file now so that we're not contributing that and 10.0.4
>>> any more, or wait to do it until after your test, Jonah?
>>>
>>> On Thu, Jun 10, 2021 at 1:52 PM Markus Knauer 
>>> wrote:
>>>
>>>> We (RAP) are consuming the Jetty bundles from WTP (
>>>> https://download.eclipse.org/webtools/jetty/...), and of course, other
>>>> bundles from Platform.
>>>> Therefore I'd like to wait until we can get the updated bundles from
>>>> there. If the update appears in the next hours, I can trigger new RAP
>>>> builds.
>>>>
>>>> Thanks
>>>> Markus
>>>>
>>>>
>>>> On Thu, 10 Jun 2021 at 18:49, Jonah Graham 
>>>> wrote:
>>>>
>>>>> Hi folks,
>>>>>
>>>>> Sravan has provided me with a link to what should represent Platform's
>>>>> contribution based on the jetty snapshot.
>>>>>
>>>>> I don't think we need to wait for a respin of the snapshot for the
>>>>> source bundle issue that Sravan identified.
>>>>>
>>>>> If other projects (RAP / Webtools/ Reddeer) can do the same, or
>>>>> provide me with build instructions I can smoke test the integration of
>>>>> everything in SimRel/EPP and make sure it all looks good and try to report
>>>>> back to Jetty so they can make their release.
>>>>>
>>>>> Thanks
>>>>> Jonah
>>>>> ~~~
>>>>> Jonah Graham
>>>>> Kichwa Coders
>>>>> www.kichwacoders.com
>>>>>
>>>>>
>>>>> On Thu, 10 Jun 2021 at 12:26, Sravan K Lakkimsetti <
>>>>> sravankum...@in.ibm.com> wrote:
>>>>>
>>>>>> Triggered a platform build with latest 10.0.5-SNAPSHOT. But there is
>>>>>> issue in the source bundles as they contain temporary files
>>>>>> https://github.com/eclipse/jetty.project/issues/6354#issuecomment-858764165
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Sravan
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* Jonah Graham 
>>>>>> *Sent:* 10 June 2021 21:36
>>>>>> *To:* Cross project issues 
>>>>>> *Subject:* [EXTERNAL] Re: [cross-project-issues-dev] ACTION REQUIRED
>>>>>> from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the
>>>>>> status on removing slf4j 2.0.0 alpha
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi folks,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> The snapshot is ready
>>>>>> https://github.com/eclipse/jetty.project/issues/6354#issuecomment-858733158
>>>

Re: [cross-project-issues-dev] ACTION REQUIRED from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the status on removing slf4j 2.0.0 alpha

[Markus Knauer]

DI Naming 10.0.4
>> (org.eclipse.jetty.jndi 10.0.4) requires 'java.package; org.slf4j
>> [2.0.0,3.0.0)' but it could not be found
>>
>>
>>
>> So because you are (correctly) removing slf4j 2.0, it is unintentionally
>> breaking WTP.
>>
>>
>>
>> Nitin is working on fixing up the WTP contribution. I don't think there
>> is actually anything wrong with reddeer's contribution, we just need a
>> resolution of WTP first.
>>
>>
>>
>> I will push a patch that verifies the above in a moment.
>>
>>
>>
>> Thanks,
>>
>> Jonah
>>
>>
>>
>>
>>
>>
>>
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>>
>>
>>
>>
>> On Wed, 9 Jun 2021 at 16:15, Ondrej Dockal  wrote:
>>
>> Unfortunately, I am still not able to pass aggregator validation, this
>> time it is jetty complaining about missing org.slf4j [2.0.0,3.0.0) as can
>> be seen in [1]. I am not really sure about what I can do about it from my
>> side. There is a reopened bugzilla [2] and PR on jetty project to handle
>> this bundle dep. range for org.slf4j, but who knows when it will be fixed.
>>
>> I am trying in a meantime to omit any bundles from my plugins in release,
>> not sure if that can help.
>>
>> [1]:
>> https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/2274/console
>>
>> [2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=573454
>>
>>
>>
>> On Wed, Jun 9, 2021 at 6:47 PM Jonah Graham 
>> wrote:
>>
>> Ondrej,
>>
>>
>>
>> I think your analysis is correct. RAP tools publishes jetty to its p2
>> site, but does not include the slf4j so just happened to pick it up from
>> Platform until they removed it, now it picks it up from Reddeer.
>>
>>
>>
>> Markus,
>>
>>
>>
>> Not sure what the issues with removing slf4j 2.0.0 alpha is. Do you mean
>> that RAP references it in too many places? If you mean too many projects,
>> then you might be right, but I hope not. Hopefully with rap, wtp, and
>> reddeer making their update we can get rid of it from the 2021-06 release
>> entirely.
>>
>>
>>
>> Nitin,
>>
>>
>>
>> I think the RC2 contribution of WTP only validated because Reddeer is
>> still publishing slf4j 2.0.
>>
>>
>>
>> Jonah
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>>
>>
>>
>>
>> On Wed, 9 Jun 2021 at 10:55, Ondrej Dockal  wrote:
>>
>> Hi Folks,
>>
>> Gerrit aggregator validation job [1] is failing for me due to RAP
>> requiring jetty 10.0.3 and that transitively requires slf4j in 2.0.0 +, I
>> guess I have to wait for you to update jetty deps to make it work, right?
>>
>>
>>
>> [1]:
>> https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/2247/
>>
>>
>>
>> On Wed, Jun 9, 2021 at 4:50 PM Markus Knauer 
>> wrote:
>>
>> Switching to Jetty 10.0.4 seems to be doable for RAP, especially because
>> the Webtools team was so kind to give us access to their p2 repository for
>> building. I will try that now.
>>
>>
>>
>> slf4j 2.0.0 is a different issue. It was required until today, and is now
>> referenced in too many places. I am not sure if it will be possible to
>> remove it in a quick and safe manner in a last build towards RC2.
>>
>>
>>
>> Thanks
>>
>> Markus
>>
>>
>>
>> On Wed, 9 Jun 2021 at 15:32, Jonah Graham  wrote:
>>
>> Hi folks,
>>
>>
>>
>> Eclipse Platform have successfully updated their contribution* (Thanks
>> Sravan, Thomas, Jetty team and anyone else who got this done that I don't
>> know about!) *to SimRel to their RC2a build and that means that Eclipse
>> Platform now no longer contributes the alpha 2.0.0 version.
>>
>>
>>
>> However other projects still are contributing the bundle to simrel
>> because they are republishing parts or all of Platform RC2 or earlier or
>> jetty 10 from other sources.
>>
>>
>>
>> Can both *reddeer *and *rap *projects look at their contribution to
>> ensure that they are not contributing slf4j 2.0.0 alpha to the simrel
>> please.
>>
>>
>>
>> As Platform have updated to Jetty 10.0.4, I also see that *rap* has
>> Jetty 10.0.3 contributed to simrel and *webtools* has 10.0.2 contributed
>> to webtools. *All three versions* are in the simrel output repo!
>>
>>
>>
>> Thank you,
>>
>> Jonah
>>
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders
>> www.kichwacoders.com
>>
>>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ACTION REQUIRED from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the status on removing slf4j 2.0.0 alpha

[Markus Knauer]

Jonah, your investigation and explanation sounds plausible, and matches
what I found out.

We've been working on an upgrade of both RAP Runtime and RAP Tools to Jetty
10.0.4 in the last hours. This hopefully matches what other projects are
going to contribute.
And in addition to that we've been reworking all (transitive) dependencies
to SLF4J, ensuring that we are delivering the 1.7 version from our p2
repositories.

All is committed and pushed to SimRel now.

Thanks
Markus

On Wed, 9 Jun 2021 at 18:47, Jonah Graham  wrote:

> Ondrej,
>
> I think your analysis is correct. RAP tools publishes jetty to its p2
> site, but does not include the slf4j so just happened to pick it up from
> Platform until they removed it, now it picks it up from Reddeer.
>
> Markus,
>
> Not sure what the issues with removing slf4j 2.0.0 alpha is. Do you mean
> that RAP references it in too many places? If you mean too many projects,
> then you might be right, but I hope not. Hopefully with rap, wtp, and
> reddeer making their update we can get rid of it from the 2021-06 release
> entirely.
>
> Nitin,
>
> I think the RC2 contribution of WTP only validated because Reddeer is
> still publishing slf4j 2.0.
>
> Jonah
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
>
> On Wed, 9 Jun 2021 at 10:55, Ondrej Dockal  wrote:
>
>> Hi Folks,
>>
>> Gerrit aggregator validation job [1] is failing for me due to RAP
>> requiring jetty 10.0.3 and that transitively requires slf4j in 2.0.0 +, I
>> guess I have to wait for you to update jetty deps to make it work, right?
>>
>> [1]:
>> https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/2247/
>>
>> On Wed, Jun 9, 2021 at 4:50 PM Markus Knauer 
>> wrote:
>>
>>> Switching to Jetty 10.0.4 seems to be doable for RAP, especially because
>>> the Webtools team was so kind to give us access to their p2 repository for
>>> building. I will try that now.
>>>
>>> slf4j 2.0.0 is a different issue. It was required until today, and is
>>> now referenced in too many places. I am not sure if it will be possible to
>>> remove it in a quick and safe manner in a last build towards RC2.
>>>
>>> Thanks
>>> Markus
>>>
>>> On Wed, 9 Jun 2021 at 15:32, Jonah Graham 
>>> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> Eclipse Platform have successfully updated their contribution* (Thanks
>>>> Sravan, Thomas, Jetty team and anyone else who got this done that I don't
>>>> know about!) *to SimRel to their RC2a build and that means that
>>>> Eclipse Platform now no longer contributes the alpha 2.0.0 version.
>>>>
>>>> However other projects still are contributing the bundle to simrel
>>>> because they are republishing parts or all of Platform RC2 or earlier or
>>>> jetty 10 from other sources.
>>>>
>>>> Can both *reddeer *and *rap *projects look at their contribution to
>>>> ensure that they are not contributing slf4j 2.0.0 alpha to the simrel
>>>> please.
>>>>
>>>> As Platform have updated to Jetty 10.0.4, I also see that *rap* has
>>>> Jetty 10.0.3 contributed to simrel and *webtools* has 10.0.2
>>>> contributed to webtools. *All three versions* are in the simrel output
>>>> repo!
>>>>
>>>> Thank you,
>>>> Jonah
>>>>
>>>> ~~~
>>>> Jonah Graham
>>>> Kichwa Coders
>>>> www.kichwacoders.com
>>>> ___
>>>> cross-project-issues-dev mailing list
>>>> cross-project-issues-dev@eclipse.org
>>>> To unsubscribe from this list, visit
>>>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>>
>>>
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To unsubscribe from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] ACTION REQUIRED from RAP / REDDEER / WEBTOOLS - respin of Eclipse Platform RC2a and the status on removing slf4j 2.0.0 alpha

[Markus Knauer]

Switching to Jetty 10.0.4 seems to be doable for RAP, especially because
the Webtools team was so kind to give us access to their p2 repository for
building. I will try that now.

slf4j 2.0.0 is a different issue. It was required until today, and is now
referenced in too many places. I am not sure if it will be possible to
remove it in a quick and safe manner in a last build towards RC2.

Thanks
Markus

On Wed, 9 Jun 2021 at 15:32, Jonah Graham  wrote:

> Hi folks,
>
> Eclipse Platform have successfully updated their contribution* (Thanks
> Sravan, Thomas, Jetty team and anyone else who got this done that I don't
> know about!) *to SimRel to their RC2a build and that means that Eclipse
> Platform now no longer contributes the alpha 2.0.0 version.
>
> However other projects still are contributing the bundle to simrel because
> they are republishing parts or all of Platform RC2 or earlier or jetty 10
> from other sources.
>
> Can both *reddeer *and *rap *projects look at their contribution to
> ensure that they are not contributing slf4j 2.0.0 alpha to the simrel
> please.
>
> As Platform have updated to Jetty 10.0.4, I also see that *rap* has Jetty
> 10.0.3 contributed to simrel and *webtools* has 10.0.2 contributed to
> webtools. *All three versions* are in the simrel output repo!
>
> Thank you,
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] RAP Tools disabled because of conflicts with Eclipse Platform 4.20 M1 contribution

[Markus Knauer]

I started yesterday to look into this, unfortunately it'll take some time...

We used to consume Jetty from their 9.x p2 repositories, but with 10.x this
is not possible any more.

Eclipse Platform Team, how are you consuming the Jetty bundles now?
That'll help us solve it on our side in the same way.

Thanks
Markus

On Fri, 9 Apr 2021 at 18:14, Kit Lo  wrote:

> During Eclipse Platform 4.20 M1 contribution, we noticed conflicts with
> RAP Tools and new version of Jetty.
>
> Requesting RAP Tools development team to take a look and re-enable RAP
> Tools contribution when the problem is resolved.
>
> Regards,
> Kit Lo
> Eclipse Babel Project Lead
> IBM Eclipse SDK (IES) Technical Lead and Release Manager
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] 2020-06 Release

[Markus Knauer]

Hi Wayne,

it's the same for RAP... it should be 3.13.
The release record is now available at
https://projects.eclipse.org/projects/rt.rap/releases/3.13.0

Thanks and regards,
Markus


On Tue, 26 May 2020 at 02:28, Jeff Johnston  wrote:

> Hi Wayne,
>
> Linux Tools should be 7.7.0 for 2020-06.  I had thought I had created the
> release record, but I was mistaken.  Anyway, it is created now.
>
> -- Jeff J.
>
> On Mon, May 25, 2020 at 2:44 PM Wayne Beaton <
> wayne.bea...@eclipse-foundation.org> wrote:
>
>> I've updated the records based on feedback.
>>
>> If you have not done so, please review the list and let me know if
>> something isn't right.
>>
>> https://projects.eclipse.org/releases/2020-06
>>
>> Wayne
>>
>> On Wed, May 20, 2020 at 11:59 AM Wayne Beaton <
>> wayne.bea...@eclipse-foundation.org> wrote:
>>
>>> Hey folks!
>>>
>>> I've created the record for the 2020-06 Simultaneous Release
>>> . As usual, I've used
>>> the information that I have available to make my best guess at which
>>> version you're releasing. If I've got something wrong, please first make
>>> sure that you've created a release record with the right date and then let
>>> me know to update the corresponding entry on the release page.
>>>
>>> I noticed that several of the contributions are more than one year old
>>> (some of them significantly more). I don't believe that it's necessarily
>>> wrong to contribute stable content, but would like to make sure that
>>> somebody is periodically testing configurations that include these
>>> contributions to mitigate the risk that we ship broken content.
>>>
>>> Eclipse Tools for Cloud Foundry (2018)
>>> Eclipse BIRT (2017)
>>> Eclipse Mylyn (2018)
>>> Eclipse WindowBuilder (early 2019)
>>> Eclipse Xpand (2016)
>>> Eclipse Remote Systems Explorer (2018)
>>> Eclipse EMFStore (2017)
>>> Eclipse BPMN2 Model (2018)
>>> Eclipse BPEL Designer (2018)
>>> Eclipse ACTF (2017)
>>>
>>> Wayne
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Wayne Beaton
>>>
>>> Director of Open Source Projects | Eclipse Foundation, Inc.
>>>
>>> Join us at our virtual event: EclipseCon 2020
>>>  - October 20-22
>>>
>>
>>
>> --
>>
>> Wayne Beaton
>>
>> Director of Open Source Projects | Eclipse Foundation, Inc.
>>
>> Join us at our virtual event: EclipseCon 2020
>>  - October 20-22
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (UTC +1)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [eclipse.org-committers] Use Milestones/RCs To Test and Run

[Markus Knauer]

RC2 == R if everyone sends a +1. That's the reason why they are never
published, but they are available for final testing - see Dani's mail or
the announcement on epp-dev.

Thanks,
Markus


On Sun, 15 Dec 2019, 20:06 Matthias Sohn,  wrote:

> I can't find the RC2 packages, are they already available ?
> Can't find them here
> https://www.eclipse.org/downloads/packages/release/2019-12/rc2
>
> -Matthias
>
> On Fri, Dec 13, 2019 at 4:11 PM Daniel Megert 
> wrote:
>
>> The Platform cannot envision all the ways it is used. We do what we can
>> to test. So, as long as you test your stuff against all the milestones and
>> then don't file bugs after RC2 - fine.
>>
>> Dani
>>
>>
>>
>> From:Greg Watson 
>> To:Daniel Megert 
>> Cc:Eclipse Cross Project Issues <
>> cross-project-issues-dev@eclipse.org>, eclipse.org-committ...@eclipse.org
>> Date:13.12.2019 15:11
>> Subject:[EXTERNAL] Re: [cross-project-issues-dev]
>> [eclipse.org-committers] UseMilestones/RCs To Test and Run
>> Sent by:cross-project-issues-dev-boun...@eclipse.org
>> --
>>
>>
>>
>> Projects have enough on their plates testing their own code, let alone
>> testing the platform. This seems to be a deficiency in the regression
>> testing of the platform, and should be handled by the platform team IMHO.
>>
>> Greg
>>
>> On Dec 13, 2019, at 5:23 AM, Daniel Megert <*daniel_meg...@ch.ibm.com*
>> > wrote:
>>
>> It would be great if everyone could at least test or even better, run on
>> the latest milestone/RC. Platform got a stop ship bug for 4.13 and one for
>> 4.14 reported after RC2. The 4.13 bug was introduced in M3 and the 4.14 bug
>> in M1. So, there would have been enough room to find the bugs earlier.
>>
>> Of course the Platform team does exactly that but everyone has its own
>> patterns how to work and hence, unfortunately did not detect those bugs.
>>
>> Thanks to everyone who helps with testing!
>> Dani
>> ___
>> *eclipse.org* -committers mailing list
>> *eclipse.org-committ...@eclipse.org* 
>> https://www.eclipse.org/mailman/listinfo/eclipse.org-committers
>>
>> IMPORTANT: Membership in this list is generated by processes internal to
>> the Eclipse Foundation.  To be permanently removed from this list, you must
>> contact e...@eclipse.org to request removal.
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Participation Page

[Markus Knauer]

Good point...

We (RAP) are going to publish 3.11 (and not 3.10):
  https://projects.eclipse.org/projects/rt.rap/releases/3.11.0

Thanks,
Markus



On Fri, 13 Dec 2019 at 16:28, Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Please have another look at the page to make sure that we have this right.
>
> https://projects.eclipse.org/releases/2019-12
>
> FWIW, getting this right is important for a number of our processes,
> including the "new and noteworthy" page and a number of statistics that I
> report to the board.
>
> Wayne
>
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation, Inc.
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel 2019-12 Milestone 3 (M3) is available

[Markus Knauer]

Indeed, that update was missing. I've fixed it right now.

Thanks,
Markus

On Mon, 2 Dec 2019 at 08:32, Ed Merks  wrote:

> Fred,
>
> I wondered why the repository analyzer is not finding EPP's M3. It
> appears that's because the
> http://download.eclipse.org/technology/epp/packages/2019-12/ composite
> has not been updated to include it:
>
> 
> 
>  type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
>
> version='1.0.0'>
>
>  
>  
>  
>
>
>  
>  
>
> 
>
> Something has slipped through the cracks...
>
> Regards,
> Ed
>
>
> On 29.11.2019 16:00, Frederic Gurr wrote:
> > Hi,
> >
> > The 2019-12 M3 update repository is now available from:
> >
> > => http://download.eclipse.org/releases/2019-12/
> >
> > The EPP Packages are available here:
> >
> > => https://www.eclipse.org/downloads/packages/release/2019-12/m3
> >
> > Thanks everyone for participating. Keep on testing!
> >
> >
> > Regards,
> >
> > Fred
> >
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] The Eclipse IDE 2019-09 release is available now!

[Markus Knauer]

>
> Beers on me at EclipseCon!


I knew there are countless reasons to attend EclipseCon, but this one is an
additional motivation... I'll try to find some time after a one year
non-attendance.

Thanks,
Markus

On Wed, 18 Sep 2019 at 17:28, Denis Roy 
wrote:

> That bears repeating. Last minute regression, fix, respin and still
> deliver on time?
>
> Some folks know what they are doing. Props for the professionalism.
>
> Beers on me at EclipseCon!
>
>
>
> On 2019-09-18 10:47 a.m., Mickael Istria wrote:
>
> Thanks to everyone, especially to those involved in the last minute respin
> of the Platform and downstream rebuilds, and that's actually a long list!
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] End of an Era: shell access.

[Markus Knauer]

Dear Webmasters,

back from vacation I find this conversation about shell access again. After
the one earlier this year I believed that you will rethink your decision,
and my and other concerns were heard, especially because the discussion
went quiet so quickly.

I have to say that I am not in any way prepared for the shell access
removal, and that I won't have any time and energy to spend on the
preparation in the next weeks because of too many more important duties on
my list. But without shell access I won't be able to release any of the
packages in the future, and short term I cannot help anyone to setup a
Jenkins job that would copy and rename the packages into the correct
location, and prepare the other configuration files for the download page.

I'm asking you to either postpone this access removal until the end of the
year, or rethink the whole removal, but it needs more time for preparation
and communication with the teams.

Regards,
Markus




On Tue, 27 Aug 2019 at 18:46, Ed Merks  wrote:

> Matt,
>
> So in the end, a restricted shell is essentially so crippled as to be
> effectively useless, and there exists no actual concrete "definition" of
> what, if anything, useful might in reality be accomplished with a
> restricted shell.
>
> I should point out that this is quite different from the impression that
> was presented earlier in this process, so I'm disappointed in how this has
> been presented and handled.  It feels to me like a process of decree where
> there is no recourse:
>
>   "We've come to claim your property to build a new highway; we're very
> sorry that you'll have to move out before the end of October, but it is for
> the greater good."
>
> Regards,
> Ed
>
>
> On 27.08.2019 16:44, Matthew Ward wrote:
>
> Hi Ed,
>
>   The restricted shell was originally created with the goal of providing
> committers a way to interact with the downloads/archive filesystems for
> releng activities, and version control systems without providing a general
> purpose shell.  So naturally the command set available leans in that
> direction(mv,cp,mkdir,git etc).
>
> We are certainly willing to discuss adding extra commands either
> temporarily or permanently, but I want to make it clear that the goal is
> not to reproduce bash.
>
> -Matt.
>
>
>
>
> On Mon, Aug 26, 2019 at 9:58 AM Ed Merks  wrote:
>
>> What will we be able to do in restricted shell?  Using vi is a very basic
>> activity.  I suppose there must be some good reason why that's restricted?
>> Earlier I was under the impression that such simple things would continue
>> to work, but now I have to wonder.  But then it was mentioned that things
>> we discover needed could become unrestricted...
>>
>> On 26.08.2019 15:35, Matthew Ward wrote:
>>
>> Hi David,
>>
>>   Thanks for the questions.
>>
>> Users with the restricted shell will have the same home directories that
>> they do currently, which will remain the place for authorized keys.   You
>> won't be able to edit(vi/emacs/ed) files directly within the restricted
>> shell, so you will need to upload them via scp/rsync.  If you want a more
>> 'interactive' type of access I'd suggest looking into using libfuse, and
>> specifically the sshfs file system.
>>
>> The restricted shell allows rsync, so there should be zero impact.  If
>> you'd like to test in advance, drop me a line and I'll set you up.
>>
>> -Matt.
>>
>> On Sat, Aug 24, 2019 at 3:23 PM David Williams 
>> wrote:
>>
>>> On 8/23/19 14:24, Matthew Ward wrote:
>>>
>>> Hi Everyone,
>>>
>>>   I just wanted to follow up with a reminder that on August 28th we will
>>> be moving committers that have an actual shell on Eclipse.org to our
>>> restricted shell.
>>>
>>> I'd like to thank both Donat and Etienne on the Buildship RelEng team
>>> who volunteered to test this change, and helped me confirm that this change
>>> should be minimally disruptive.
>>>
>>> If you have any questions, please let me know.
>>>
>>> -Matt.
>>>
>>>
>>> Thanks for the reminder.
>>>
>>> Will those of use that still want to use 'scp' and similar still have a
>>> 'home directory' (on "build"?) and is that still the place for
>>> .ssh/authorized_keys2? Or, does all that change with "restricted shell"?
>>>
>>> If a change, can you point me to instructions on how to set that up? I
>>> would assume some form of "ssh-copy-id hostname" but thought best not to
>>> assume and ask explicitly.
>>>
>>> In case you are wondering, the use case, for using scp and similar is to
>>> download a number of builds to my local machine (without going through web
>>> interfaces).
>>> Now that I think of it, I currently use rsync via ssh, such as
>>>
>>>  rsync -a -e ssh ${committer_id}@build.eclipse.org:${dlpath}
>>> "${output_dir}"
>>>
>>> Will that still work with a restricted shell? Or, will I need to convert
>>> to "scp"?
>>>
>>> Thanks,
>>>
>>>
>>> ___
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@eclipse.org
>>> To 

Re: [cross-project-issues-dev] The end of an era: shell access.

[Markus Knauer]

Hi Matt,

I share Ed's opinion: Many of my tasks that are currently easy to
accomplish with the flexibility of a shell will become nearly impossible
without, and because these tasks require some flexibility I cannot simply
replace them with jobs running on a CI instance. And e.g. there's really no
benefit of running a rsync in a Jenkins job (with a lot of try and error
involved) compared to do the same work in an efficient manner from the
shell.

Thanks,
Markus

On Thu, 4 Jul 2019 at 22:54, Ed Merks  wrote:

> Mat,
>
> Count me as someone who will be VERY, VERY, VERY UNHAPPY ABOUT
> RESTRICTIONS!
>
> Sorry for shouting, but it's hard for me to imagine how I can maintain the
> services that I provide without the access I currently have.  Just as an
> example, I could not have developed this without such access:
>
>   https://download.eclipse.org/oomph/archive/eclipse/index.html
>
> I assume there must be extremely good reasons for this change of policy,
> no doubt related to ultra-secure security.  I'm sure those reasons must be
> excellent and that you, or someone, will be able to articulate them.
> Please do so for the benefit of the community at large, given that you feel
> the need to announce this to the community at large, rather than to the
> "limited set of committers".
>
> Perhaps a Bugzilla for such a discussion thread would be appropriate to
> reduce noise levels on the mailing list.
>
> Regards,
> Ed
>
>
> On 04.07.2019 21:49, Eclipse Webmaster wrote:
>
> Hi Everyone,
>
>   As some of you may know we have traditionally provided a limited set of
> committers with shell access to build.eclipse.org, and all other
> committers having restricted shells.
>
> For the last couple of years[1][2] we've been working to reduce that
> number as far as possible, and the time has come to finish the process.
>
> Effective August 28th 2019 we will be transitioning all committers that
> still have a regular shell to our restricted shell.  You will still be able
> to use SFTP and SCP to interact with the downloads and archive areas(but we
> suggest a job on your Eclipse CI instance!)
>
> If you have any questions or concerns please feel free to contact
> Webmaster.
>
> -Matt.
>
> [1] https://www.eclipse.org/lists/cross-project-issues-dev/msg06625.html
> [2] https://www.eclipse.org/lists/eclipse.org-committers/msg01075.html
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Request for respin of 2019-06

[Markus Knauer]

The .../epp/packages/2019-06 repo is now in its expected, normal state.

Thanks,
Markus

On Tue, 18 Jun 2019 at 18:29, Markus Knauer 
wrote:

> I'm concerned, too, about the bug 548397
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=548397> you were
> mentioning in your mail.
>
> Regarding the p2 repo: That is on my list and a routine task. The p2
> repository itself is small, and usually no issue to be mirrored.
>
> Thanks,
> Markus
>
>
> On Tue, 18 Jun 2019 at 18:24, Ed Merks  wrote:
>
>> At the moment, the missing signatures of Windows executables in any of
>> the p2 repositories is starting to look like a pretty serious problem.
>> E.g., this file does not contain a signed eclipse.exe
>>
>>
>> https://download.eclipse.org/technology/epp/packages/2019-06/R/binary/epp.package.committers.executable.win32.win32.x86_64_4.12.0.20190614-1200
>>
>> I think that stems from the fact the platform repo has not signed its
>> eclipse.exe:
>>
>>   https://bugs.eclipse.org/bugs/show_bug.cgi?id=548397
>> As a result, none of the installations create by the installer will have
>> a signed executable (nor will any update of any existing installation
>> update to produce a signed executable).
>>
>> I'm also a very concerned that the
>> https://download.eclipse.org/technology/epp/packages/2019-06 repo does
>> not look to be in the normal state that it's typically in right before
>> being published on the release day.  I.e., there to not exist the expected
>> binary, features and plugins folders with content that have been mirrored
>> ahead of time; perhaps that will be prepared in the next few hours...
>>
>> In the end, all this does not look promising for a high-quality release
>> tomorrow.
>>
>>
>> On 18.06.2019 17:46, Matthias Wienand wrote:
>>
>> Hello, everybody,
>>
>> I'm sorry for the late communication during quiet week.
>>
>> I wanted to get involved in the corresponding discussion about the
>> Respin: I would be happy about a Respin, that would allow me to update the
>> GEF contribution for the release, which fixes a little annoyance in the
>> user interface.
>>
>> https://git.eclipse.org/r/144374
>>
>> Best regards,
>> Matthias
>> --
>>
>> Matthias Wienand
>> B.Sc. Softwaretechnik
>> Software Engineer
>>
>> Telefon: +49 231 9860 202
>> Telefax: +49 231 9860 211
>> Mobil:   +49 152 26802283
>>
>>
>> matthias.wien...@itemis.de
>> http://www.xing.com/profile/Matthias_Wienand2
>> http://www.itemis.de
>>
>>
>> itemis AG
>>
>> Am Brambusch 15-24
>> 44536 Lünen
>>
>> Rechtlicher Hinweis:
>> Amtsgericht Dortmund, HRB 20621
>> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Abdelghani El-Kacimi
>> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer
>> Fiorentino
>>
>>
>> ___
>> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe from 
>> this list, 
>> visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Request for respin of 2019-06

[Markus Knauer]

I'm concerned, too, about the bug 548397
 you were mentioning
in your mail.

Regarding the p2 repo: That is on my list and a routine task. The p2
repository itself is small, and usually no issue to be mirrored.

Thanks,
Markus


On Tue, 18 Jun 2019 at 18:24, Ed Merks  wrote:

> At the moment, the missing signatures of Windows executables in any of the
> p2 repositories is starting to look like a pretty serious problem.  E.g.,
> this file does not contain a signed eclipse.exe
>
>
> https://download.eclipse.org/technology/epp/packages/2019-06/R/binary/epp.package.committers.executable.win32.win32.x86_64_4.12.0.20190614-1200
>
> I think that stems from the fact the platform repo has not signed its
> eclipse.exe:
>
>   https://bugs.eclipse.org/bugs/show_bug.cgi?id=548397
> As a result, none of the installations create by the installer will have a
> signed executable (nor will any update of any existing installation update
> to produce a signed executable).
>
> I'm also a very concerned that the
> https://download.eclipse.org/technology/epp/packages/2019-06 repo does
> not look to be in the normal state that it's typically in right before
> being published on the release day.  I.e., there to not exist the expected
> binary, features and plugins folders with content that have been mirrored
> ahead of time; perhaps that will be prepared in the next few hours...
>
> In the end, all this does not look promising for a high-quality release
> tomorrow.
>
>
> On 18.06.2019 17:46, Matthias Wienand wrote:
>
> Hello, everybody,
>
> I'm sorry for the late communication during quiet week.
>
> I wanted to get involved in the corresponding discussion about the Respin:
> I would be happy about a Respin, that would allow me to update the GEF
> contribution for the release, which fixes a little annoyance in the user
> interface.
>
> https://git.eclipse.org/r/144374
>
> Best regards,
> Matthias
> --
>
> Matthias Wienand
> B.Sc. Softwaretechnik
> Software Engineer
>
> Telefon: +49 231 9860 202
> Telefax: +49 231 9860 211
> Mobil:   +49 152 26802283
>
>
> matthias.wien...@itemis.de
> http://www.xing.com/profile/Matthias_Wienand2
> http://www.itemis.de
>
>
> itemis AG
>
> Am Brambusch 15-24
> 44536 Lünen
>
> Rechtlicher Hinweis:
> Amtsgericht Dortmund, HRB 20621
> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Abdelghani El-Kacimi
> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer
> Fiorentino
>
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel 2019-06 Release Candidate 2 (RC2) staging repo is complete

[Markus Knauer]

Hmm, big surprise...
I just realized, too, like so many other people that there is no RC3. That
should have been communicated better.

The current EPP builds are really "RC2" builds and not a "R" (GA) build.
That still needs to be done, and will take some more time.

Regards,
Markus


On Thu, 13 Jun 2019 at 18:24, Greg Watson  wrote:

> I can live without it :-)
>
> I agree with Doug though, it should probably be better documented when the
> last contribution can be made. Since the iterations come so frequently now,
> it’s hard to keep up with where we are in a cycle.
>
> Regards,
> Greg
>
> On Jun 13, 2019, at 12:10 PM, Doug Schaefer 
> wrote:
>
> If that's the rule, it should really be captured here:
>
> https://wiki.eclipse.org/SimRel/2019-06/Simultaneous_Release_Plan
>
> Also interesting that the GA date keeps getting earlier. We're in mid-June
> territory now...
>
> Doug.
>
> 
> From: cross-project-issues-dev-boun...@eclipse.org [
> cross-project-issues-dev-boun...@eclipse.org] on behalf of Frederic Gurr [
> frederic.g...@eclipse-foundation.org]
> Sent: Thursday, June 13, 2019 12:04 PM
> To: cross-project-issues-dev@eclipse.org
> Subject: Re: [cross-project-issues-dev] SimRel 2019-06 Release Candidate 2
> (RC2) staging repo is complete
>
> Hi,
>
> The quiet period officially starts tomorrow, but the EPP build is always
> on a Thursday. Unfortunately, last minute contributions have started to
> bleed into Thursday for a while now, even though they should be done by
> Wednesday EOB.
>
> Are you okay with leaving out that change?
>
> Regards,
>
> Fred
>
> On 13.06.19 17:58, Greg Watson wrote:
>
> No, not critical, but I thought tomorrow was the start of the RC2 quiet
> period?
>
> Greg
>
> On Jun 13, 2019, at 11:45 AM, Frederic Gurr <
> frederic.g...@eclipse-foundation.org> wrote:
>
> Hi,
>
> Is this a critical fix?
>
> Regards,
>
> Fred
>
> On 13.06.19 16:24, Greg Watson wrote:
>
> I have an update that only went into the build today because a previous
> Gerrit changeset was never validated. Is it possible to run the aggregation
> again today? Sorry for the last minute issue.
>
> Thanks,
> Greg
>
> On Jun 13, 2019, at 9:43 AM, Frederic Gurr <
> frederic.g...@eclipse-foundation.org> wrote:
>
> Hi,
>
> Since the SimRel aggregator build is quiet, I declare the staging repo
> for 2019-06 RC2 to be complete.
>
> As usual, it can be found here:
>
> =>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__download.eclipse.org_staging_2019-2D06_=DwICAg=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE=NrrbvTHWa2Nbp_kAN0Hl1o3lM1WAwSes64uBjxjNhMc=Kxo5hO9B2vR-RsF79RhPB4XXe9-ohDFoJvX3O40qggU=yyVFt7Kg-duKjZ89Yo9TCo-e3CcfHTVh4J9mMbNFX0M=
>
> Please note, we will enter quiet days for 2019-06. If no blocking
> issues are found, RC2 will become the official 2019-06 release on
> Wednesday, June 19th.
>
> Thanks for all your contributions and happy _quiet_ days!
>
> Regards,
>
> Fred
>
>
>
> --
> Frederic Gurr
> Release Engineer | Eclipse Foundation Europe GmbH
>
> Annastr. 46, D-64673 Zwingenberg
> Handelsregister: Darmstadt HRB 92821
> Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev=DwICAg=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE=NrrbvTHWa2Nbp_kAN0Hl1o3lM1WAwSes64uBjxjNhMc=Kxo5hO9B2vR-RsF79RhPB4XXe9-ohDFoJvX3O40qggU=Ys6M874QOeeDzWafEyaZs0kC6STit_ELSN-vnRBUS1g=
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev=DwICAg=yzoHOc_ZK-sxl-kfGNSEvlJYanssXN3q-lhj0sp26wE=NrrbvTHWa2Nbp_kAN0Hl1o3lM1WAwSes64uBjxjNhMc=Kxo5hO9B2vR-RsF79RhPB4XXe9-ohDFoJvX3O40qggU=Ys6M874QOeeDzWafEyaZs0kC6STit_ELSN-vnRBUS1g=
>
>
> --
> Frederic Gurr
> Release Engineer | Eclipse Foundation Europe GmbH
>
> Annastr. 46, D-64673 Zwingenberg
> Handelsregister: Darmstadt HRB 92821
> Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
>
> 

Re: [cross-project-issues-dev] Initialization for 2019-06

[Markus Knauer]

I added the one for EPP 2019-06. Please check.

Thanks,
Markus

On Thu, 21 Mar 2019 at 12:48, Ed Merks  wrote:

> I'm very happy to see that http://download.eclipse.org/releases/2019-06
> already exists.
>
> But of course I'm going to complain and ask for more! :-P
>
> The contents current look like this:
>
> 
> 
>  type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
>
> version='1.0.0'>
>
>  
>  
>  
>
>
>  
>
> 
>
> Note that the EPP repo is absent and that's because
> https://download.eclipse.org/technology/epp/packages/2019-06 doesn't yet
> exist.  But more important note that there is now no EPP repo specified
> anywhere, so this isn't really going to be workable in this state...
>
> What would be really great would be if
> https://download.eclipse.org/technology/epp/packages/2019-06 also
> already existed; it would be a composite that references exactly one
> child via ../2019-03.
>
> Then http://download.eclipse.org/releases/2019-06 would be changed to
> this:
>
> 
> 
>  type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
>
> version='1.0.0'>
>
>  
>  
>  
>
>
>   location='http://download.eclipse.org/technology/epp/packages/2019-09' />
>  
>
> 
>
> In this state, the two repos would serve up the exactly same contents as
> 2019-03 via composition, until that point in time when the first
> milestone is produced for 2019-06 when they would reference the new
> 2019-06 repos instead.
>
> This would really help me maintain the Oomph setups better (and to
> prepare the first EMF builds targeting 2019-06).
>
> Of course I'm more than willing to do all the work to prepare these if I
> my account emerks has the necessary permissions on build.eclipse.org.
>
> BTW, special thanks to whomever changed
> http://download.eclipse.org/releases/latest to look like this:
>
> 
> 
>  type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
>
> version='1'>
>
>  
>  
>  
>
>
>  
>
> 
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (UTC +1)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] URGENT!! Re: The Eclipse IDE 2019-03 release is available now!

[Markus Knauer]

lipse.org/releases/luna/201406250900/content.jar*
> <http://download.eclipse.org/releases/luna/201406250900/content.jar>.
>at
> org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:431)
>at
> org.eclipse.equinox.internal.p2.repository.CacheManager.createCache(CacheManager.java:262)
>at
> org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile(SimpleMetadataRepositoryFactory.java:69)
>at
> org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:89)
>at
> org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:63)
>at
> org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:770)
>at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>at java.lang.reflect.Method.invoke(Method.java:498)
>at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:117)
>at
> org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:409)
>at
> org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:201)
>at
> org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:476)
>at
> org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110)
>at
> org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105)
>at
> org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:168)
>... 19 more
> Caused by: java.net.SocketTimeoutException: Read timed out
>at java.net.SocketInputStream.socketRead0(Native Method)
>at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
>at java.net.SocketInputStream.read(SocketInputStream.java:171)
>at java.net.SocketInputStream.read(SocketInputStream.java:141)
>at
> org.apache.http.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:201)
>at
> org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:176)
>at
> org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135)
>at java.io.FilterInputStream.read(FilterInputStream.java:133)
>at java.io.FilterInputStream.read(FilterInputStream.java:107)
>at
> org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178)
>at
> org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74)
>... 1 more
> On 21.03.2019 07:11, Christian Dietrich wrote:
> Hi,
>
> i am getting this from oomph now
>
> Fetching content.xml.xz from
> *http://download.eclipse.org/releases/2019-03/201903201000/*
> <http://download.eclipse.org/releases/2019-03/201903201000/>
> ERROR: org.eclipse.equinox.p2.metadata.repository code=1002 Unable to
> read repository at *http://download.eclipse.org/releases/2019-03*
> <http://download.eclipse.org/releases/2019-03>.
> ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 Unable to read
> repository at
> *http://download.eclipse.org/releases/2019-03/201903201000/content.xml.xz*
> <http://download.eclipse.org/releases/2019-03/201903201000/content.xml.xz>
> .
> java.net.SocketTimeoutException: Read timed out
>
> Any idea?
>
> Thanks
> Christian
>
> Am 20.03.19 um 15:59 schrieb Frederic Gurr:
>
> Thanks Markus!
>
> On 20.03.19 15:49, Markus Knauer wrote:
>
> Timezones...
>
> I was about to update the repo anyway before reading these messages.
> It's done now...
>
> Regards,
> Markus
>
> On Wed, 20 Mar 2019 at 15:42, Ed Merks <*ed.me...@gmail.com*
> 
> *<mailto:ed.me...@gmail.com>* > wrote:
>
>   Yes, I was about to send an urgent note as well.  Someone forgot to
>   change *http://download.eclipse.org/technology/epp/packages/2019-03/*
> <http://download.eclipse.org/technology/epp/packages/2019-03/>
>   to be an aggregate!!
>
>   I see artifacts.jar.R, and content.jar.R (and the .xml.xz.R versions
>   of them) so I believe those need to be renamed to replace the
>   composite*.jar things *as soon as possible*. Because right now this
>   doesn't even point at RC2 because it's hidden from the composite so
>   one one can install anything 

Re: [cross-project-issues-dev] URGENT!! Re: The Eclipse IDE 2019-03 release is available now!

[Markus Knauer]

Timezones...

I was about to update the repo anyway before reading these messages.
It's done now...

Regards,
Markus

On Wed, 20 Mar 2019 at 15:42, Ed Merks  wrote:

> Yes, I was about to send an urgent note as well.  Someone forgot to change
> http://download.eclipse.org/technology/epp/packages/2019-03/ to be an
> aggregate!!
>
> I see artifacts.jar.R, and content.jar.R (and the .xml.xz.R versions of
> them) so I believe those need to be renamed to replace the composite*.jar
> things *as soon as possible*. Because right now this doesn't even point
> at RC2 because it's hidden from the composite so one one can install
> anything right now!!
>
> On 20.03.2019 15:29, Patrick Tasse wrote:
>
> Hi Frederic,
>
> If I try "Check for Updates" I get the following error:
>
> Cannot complete the install because one or more required items could not
> be found.
>   Software being installed: Eclipse IDE for Eclipse Committers
> 4.11.0.20190307-1428 (epp.package.committers 4.11.0.20190307-1428)
>   Missing requirement: Eclipse IDE for Eclipse Committers
> 4.11.0.20190307-1428 (epp.package.committers 4.11.0.20190307-1428) requires
> 'org.eclipse.equinox.p2.iu; org.eclipse.help.feature.group
> [2.2.500.v20190301-0040,2.2.500.v20190301-0040]' but it could not be found
>
> My "Available Software Sites" are
> http://download.eclipse.org/releases/2019-03 and
> http://download.eclipse.org/eclipse/updates/4.11 .
>
> Patrick
>
> On Wed, Mar 20, 2019 at 10:01 AM Frederic Gurr <
> frederic.g...@eclipse-foundation.org> wrote:
>
>> The main repository is at
>>
>>   http://download.eclipse.org/releases/2019-03/
>>
>> (http://download.eclipse.org/releases/latest also points to it)
>>
>> The EPP (all-in-one) packages are available at
>>
>>   https://www.eclipse.org/downloads/eclipse-packages/
>>
>> The landing page can be found here:
>>
>>   https://www.eclipse.org/eclipseide/2019-03/
>>
>> Thanks to all users, bug reporters, contributors, committers, releng
>> engineers and everyone else involved with making this release possible!
>>
>> Regards,
>>
>> Fred
>>
>> --
>> Frederic Gurr
>> Release Engineer | Eclipse Foundation Europe GmbH
>>
>> Annastr. 44, D-64673 Zwingenberg
>> Handelsregister: Darmstadt HRB 92821
>> Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [epp-dev] Fwd: EPP Packages 2019-03 M3

[Markus Knauer]

Maybe it is cached in one of the webservers, proxies, etc.?

On the file system it is correct:

download.eclipse.org/technology/epp/packages/2019-03> zcat
compositeContent.jar



  



  
  



  



Regards,
Markus


On Fri, 8 Mar 2019 at 13:54, Christian Dietrich <
christian.dietr...@itemis.de> wrote:

> Hi,
>
>
> i dont see M3 here right now
>
>
> https://download.eclipse.org/technology/epp/packages/2019-03/compositeContent.jar
>
> https://download.eclipse.org/technology/epp/packages/2019-03/compositeArtifacts.jar
> Am 08.03.19 um 13:52 schrieb Markus Knauer:
>
> Hi Christian,
>
> yes, the reference to M3 *was* missing, but has been added in the
> meantime, and
> yes, RC1 should be available later today.
>
> Thanks,
> Markus
>
> On Fri, 8 Mar 2019 at 13:33, Christian Dietrich <
> christian.dietr...@itemis.de> wrote:
>
>>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: EPP Packages 2019-03 M3
>> Datum: Fri, 8 Mar 2019 13:16:47 +0100
>> Von: Christian Dietrich 
>> 
>> An: Cross project issues 
>> 
>>
>> Hello all,
>>
>> https://download.eclipse.org/technology/epp/packages/2019-03/ does not
>> contain M3
>> will there be a RC1/Release.
>>
>> I am currently stucked with an OOmphed Eclipse Committers IDE with no
>> package explorer
>> and no ability to update Platform/JDT cause there is no M3
>>
>> Thanks
>> Christian
>>
>> ___
>> epp-dev mailing list
>> epp-...@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://www.eclipse.org/mailman/listinfo/epp-dev
>
>
>
> ___
> epp-dev mailing listepp-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visithttps://www.eclipse.org/mailman/listinfo/epp-dev
>
> ___
> epp-dev mailing list
> epp-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/epp-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Fwd: EPP 2018-12 Repo Doesn't Appear Prepared for Tomorrow's Release

[Markus Knauer]

Hi Ed,

the repository should be ready, except the artifacts and p2.index files
which are "invisible" by the appended .R

And, yes, the last RC is not published intentionally.

Thanks,
Markus

On Tue, 18 Dec 2018 at 14:42, Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:

> Hi,
>
> That's intentional. RC2 packages are the final (GA) packages which are
> not visible on the download page until release day.
>
> Regards,
>
> Fred
>
> On 18.12.18 14:26, Christian Dietrich wrote:
> > hi,
> >
> > i have noticed that rc2 is not available at
> > https://www.eclipse.org/downloads/packages/release/2018-12/
> >
> > Am 18.12.18 um 14:07 schrieb Ed Merks:
> >> Hi,
> >>
> >> I'm growing concerned that I don't yet see the EPP repo for 2018-12 in a
> >> state where it is prepared for tomorrow's release.
> >>
> >> In particular 2018-12 looks like this at the moment:
> >>
> >> Normally, at the time of the release, the repo looks like this:
> >>
> >> I.e., the repo changes from being a composite to being a
> >> simple/aggregate.   That can of course happen tomorrow (changing the
> >> p2.index and making the artifacts/content files visible) but at some
> >> point very soon (today) the binary, features, and plugins folders should
> >> be populated so that mirrors have a chance to mirror those folders
> >> before users start using the repo tomorrow. Otherwise, users installing
> >> with the installer will install RC1 (if the repo doesn't change at all
> >> before tomorrow) or they will need to download directly from
> >> download.eclipse.org for lack of mirrors, possibly bring the server to
> >> its knees.
> >>
> >> Has something been overlooked?
> >>
> >> Regards,
> >> Ed
> >>
> >>
> >>
> >> ___
> >> cross-project-issues-dev mailing list
> >> cross-project-issues-dev@eclipse.org
> >> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> >> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>
> >
>
> --
> Frederic Gurr
> Release Engineer | Eclipse Foundation Europe GmbH
>
> Annastr. 46, D-64673 Zwingenberg
> Handelsregister: Darmstadt HRB 92821
> Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] EPP 2018-12 Repo Doesn't Appear Prepared for Tomorrow's Release

[Markus Knauer]

Hi Ed,

no need to worry about that. I was just waiting for the outcome of the
respin discussion, and this morning I was enjoying the "stable" Internet
connection in our trains.

It should be there within the next one to two hours.

Thanks,
Markus

On Tue, 18 Dec 2018, 14:07 Ed Merks  Hi,
>
> I'm growing concerned that I don't yet see the EPP repo for 2018-12 in a
> state where it is prepared for tomorrow's release.
>
> In particular 2018-12 looks like this at the moment:
>
> Normally, at the time of the release, the repo looks like this:
>
> I.e., the repo changes from being a composite to being a
> simple/aggregate.   That can of course happen tomorrow (changing the
> p2.index and making the artifacts/content files visible) but at some point
> very soon (today) the binary, features, and plugins folders should be
> populated so that mirrors have a chance to mirror those folders before
> users start using the repo tomorrow.  Otherwise, users installing with the
> installer will install RC1 (if the repo doesn't change at all before
> tomorrow) or they will need to download directly from download.eclipse.org
> for lack of mirrors, possibly bring the server to its knees.
>
> Has something been overlooked?
>
> Regards,
> Ed
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Eclipse RAP 3.6.0 participation in 2018-09 release

[Markus Knauer]

Hi everyone,

Eclipse RAP will participate with the usual +2 offset in the 2018-09
release.
Planned version is 3.6.0 [1].

Thanks and regards,
Markus


[1] https://projects.eclipse.org/projects/rt.rap/releases/3.6.0
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [epp-dev] Photon aggregation jobsare stuck

[Markus Knauer]

Thank you for solving this and keeping us informed about the many steps and
attempts that were necessary to fix the problem! I know what it means to
fight against such kind of problems that late in a release cycle late in
the night!

After checking the last package build, I've been asking the package
maintainers for testing and for voting now. I hope to get enough +1 votes
in order to ask webmasters to make them available on Monday on the
developers area on the download page.

The EPP p2 repository itself has been prepared. Independent of the votes, I
would take the freedom to activate this earlier (i.e. before Monday) if
necessary.

Thanks,
Markus




On 19 May 2018 at 03:13, Mikaël Barbero <
mikael.barb...@eclipse-foundation.org> wrote:

> Photon M7 is back on track.
>
> Staging repo is complete without any incorrect checksum (see
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=534867 for details).
>
> EPP is currently building.
>
> To give a bit of time to EPP, official repo of Photon M7 is scheduled to
> be promoted tomorrow at 10:00am EDT, exactly 24h late. I'll re-activate the
> simrel build jobs shortly after.
>
> Thanks to Alex and Nick for their precious help.
>
> Cheers,
>
> --
> *Mikaël Barbero - *Eclipse Foundation
> IT Services - Release Engineering
>  (+33) 642 028 039
>  mikael.barb...@eclipse-foundation.org
>  @mikbarbero
>
>
> ___
> epp-dev mailing list
> epp-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/epp-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Photon aggregation jobs are stuck

[Markus Knauer]

No problem for EPP... we've had other issues that are "fixed" now and will
need another EPP package build anyway.

(The best case would be if we could fix the RAP Tools contribution problem
with the rebuild, too. I'll see what I can do in the next minutes)

Thanks,
Markus


On 17 May 2018 at 16:18, Mikaël Barbero <
mikael.barb...@eclipse-foundation.org> wrote:

> I'm willing to give it a try, but EPP would need to rebuild as well after
> that.
>
> EPP, is it ok with you?
>
> Cheers,
>
> --
> *Mikaël Barbero - *Eclipse Foundation
> IT Services - Release Engineering
>  (+33) 642 028 039
>  mikael.barb...@eclipse-foundation.org
>  @mikbarbero
>
> Le 17 mai 2018 à 15:35, Nick Boldt  a écrit :
>
> There appears to be a problem with the simrel photon staging site. When I
> attempt to use p2.mirror to make a copy of the site, I get this error:
>
>
> *09:00:15 [p2.mirror] Messages while mirroring artifact descriptors.*
>
> *09:00:15* [p2.mirror] Problems downloading artifact: 
> osgi.bundle,org.eclipse.compare,3.7.200.v20180418-1233.*09:00:15* [p2.mirror] 
> SHA-256 hash is not as expected. Expected: 
> 6bf838a9064adb86f20a1ced5fc953014ce72f68f6b9eb71ecd28d711e42cdc7 and found 
> 3ea05da118160a8aa1be2c98c43d8868495a95bca1a5d6a3980fbdc653773f02.
>
>
> Here's the command I'm running:
>
> *09:00:15* Command-line arguments:  -consoleLog -data 
> /mnt/hudson_workspace/workspace/jbosstoolstargetplatformrequirements-mirror-matrix/a4e6db81/tmp
>  -application org.eclipse.ant.core.antRunner -f build.xml 
> -Dversion=201805161906-Photon.0.M7 
> -DURL=http://download.eclipse.org/staging/photon
>
>
> And here's the script:
>
> http://download.jboss.org/jbosstools/updates/requirements/photon/build.xml
> http://download.jboss.org/jbosstools/updates/
> requirements/generic/build.xml
>
> I can work around this with -DignoreErrors=true, but that seems
> potentially a bad idea.
>
> Should the staging site be rebuilt to fix this SHA/metadata problem?
>
>
>
> Nick
>
> On Thu, May 17, 2018 at 7:10 AM, Daniel Megert 
> wrote:
>
>> The change was in the wrong Gerrit change but is still valid. This was
>> announced on May 10: https://dev.eclipse.org/mhonar
>> c/lists/cross-project-issues-dev/msg15529.htmland Markus said, he will
>> take care of this, see ttps://dev.eclipse.org/mhonarc
>> /lists/cross-project-issues-dev/msg15530.html
>> 
>>
>> Dani
>>
>>
>>
>> From:Mickael Istria 
>> To:Cross project issues 
>> Date:17.05.2018 12:46
>> Subject:Re: [cross-project-issues-dev] Photon aggregation jobs
>> are stuck
>> Sent by:cross-project-issues-dev-boun...@eclipse.org
>> --
>>
>>
>>
>>
>>
>> On Thu, May 17, 2018 at 12:39 PM, Arthur van Dorp <
>> *arthur.vand...@bsi-software.com* >
>> wrote:
>> Sorry. I’m looking at the latest EPP-Build:
>> *https://ci.eclipse.org/packaging/job/photon.epp-tycho-build/*
>> I’m not
>> sure, what code will be pulled there after the SimRel part is done.
>>
>>
>> Please bring this to the epp-dev mailing-list. The contribution of RAP
>> tools was disabled by
>> *http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/rap-tools.aggrcon?id=d298c990d67b7ee4cd2e1232a41f1bee636507fa*
>> (which
>> seems not related and erroneous to me). If this was not intentional, then
>> it would IMO be better to respin SimRel than to add workload on RAP which
>> didn't do anything wrong here.
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
> Nick Boldt
> Principal Software Engineer, RHCSA
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> 
> TRIED. TESTED. TRUSTED. 
> @ @redhatnews   Red Hat
> 
> 
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
> ___
> cross-project-issues-dev mailing list
> 

Re: [cross-project-issues-dev] Heads Up: Simrel issues with Jetty 9.4.10 for Photon M7

[Markus Knauer]

Thanks, Sravan,

we (RAP) are already working on this, but for the time being some of our
test cases are still failing, probably because of the API changes.
We'll re-enable the RAP contributions once they are migrated to the new
Jetty version.

Thanks,
Markus



On 10 May 2018 at 11:59, Sravan K Lakkimsetti 
wrote:

> Hi,
>
>
>
> Platform is adopting Jetty 9.4.10 in M7. In this regard when I tried to
> contribute to simrel. The simrel build is failing in RAP tools (it is
> looking for Jetty 9.4.8 version). Please reenable RAP tools after adjusting
> Jetty version used by RAP tools
>
>
>
> Thanks and Regards,
>
> Sravan
>
>
>
> Sravan Kumar Lakkimsetti
>
> IBM India Pvt Ltd,
>
> Embassy Golf Links Business Park, D Block,
>
> Off Indiranagar-Kormangla Inner Ring Road,
>
> Bangalore - 560071, India
>
> Phone: 91-80-41776858
>
>
>
> *From:* Aleksandar Kurtakov [mailto:akurt...@redhat.com]
> *Sent:* Wednesday, May 09, 2018 1:58 PM
> *To:* issues, Cross 
> *Subject:* [cross-project-issues-dev] Heads up: API changes in Jetty
> 9.4.10 for Photon M7
>
>
>
> Eclipse Platform moves to Jetty version 9.4.10 which contains the
> following changes:
> org.eclipse.jetty.http(9.4.10)
> ADDEDorg.eclipse.jetty.http.HttpCompliance#CUSTOM0
> ADDEDorg.eclipse.jetty.http.HttpCompliance#CUSTOM1
> ADDEDorg.eclipse.jetty.http.HttpCompliance#CUSTOM2
> ADDEDorg.eclipse.jetty.http.HttpCompliance#CUSTOM3
> ADDEDorg.eclipse.jetty.http.HttpCompliance#RFC2616_LEGACY
> ADDEDorg.eclipse.jetty.http.HttpCompliance#RFC7230_LEGACY
> ADDEDorg.eclipse.jetty.http.HttpCompliance#VIOLATIONS_ATTR
> ADDEDorg.eclipse.jetty.http.HttpCompliance#HttpCompliance
> requiredCompliance(HttpComplianceSection)
> ADDEDorg.eclipse.jetty.http.HttpCompliance#EnumSet
> sections()
> ADDEDorg.eclipse.jetty.http.HttpComplianceSection
> ADDEDorg.eclipse.jetty.http.HttpMethod#INSENSITIVE_CACHE
> ADDEDorg.eclipse.jetty.http.HttpParser#String
> caseInsensitiveHeader(String, String)
> REMOVEDorg.eclipse.jetty.http.HttpParser#boolean 
> complianceViolation(HttpCompliance,
> String)
> ADDEDorg.eclipse.jetty.http.HttpParser#boolean 
> complianceViolation(HttpComplianceSection,
> String)
> ADDEDorg.eclipse.jetty.http.HttpParser#void 
> handleViolation(HttpComplianceSection,
> String)
> REMOVEDorg.eclipse.jetty.http.HttpParser#String legacyString(String,
> String)
> ADDEDorg.eclipse.jetty.http.HttpParser$FieldState#WS_AFTER_NAME
> ADDEDorg.eclipse.jetty.http.MimeTypes$Type#MULTIPART_FORM_DATA
> ADDEDorg.eclipse.jetty.http.MultiPartFormInputStream
> ADDEDorg.eclipse.jetty.http.MultiPartParser
>
> org.eclipse.jetty.io
> 
> (9.4.10)
> REMOVEDorg.eclipse.jetty.io.AbstractConnection#boolean onReadTimeout()
> ADDEDorg.eclipse.jetty.io.AbstractConnection#boolean
> onReadTimeout(Throwable)
> ADDEDorg.eclipse.jetty.io.CyclicTimeout
> ADDEDorg.eclipse.jetty.io.ManagedSelector.SelectorUpdate
> REMOVEDorg.eclipse.jetty.io.ManagedSelector#void submit(Runnable)
> ADDEDorg.eclipse.jetty.io.ManagedSelector#void submit(ManagedSelector.
> SelectorUpdate)
> ADDEDorg.eclipse.jetty.io.WriteFlusher.Listener
> REMOVEDorg.eclipse.jetty.io.WriteFlusher#boolean isInProgress()
>
> org.eclipse.jetty.server(9.4.10)
> ADDEDorg.eclipse.jetty.server.AbstractNCSARequestLog#String
> getAuthentication(Request)
> REMOVED
> org.eclipse.jetty.server.CachedContentFactory$CachedHttpContent#boolean
> isMiss()
> REMOVEDorg.eclipse.jetty.server.HttpChannel#void onBadMessage(int,
> String)
> ADDEDorg.eclipse.jetty.server.HttpChannel#void onBadMessage(
> BadMessageException)
> REMOVEDorg.eclipse.jetty.server.HttpChannelOverHttp#void
> badMessage(int, String)
> REMOVEDorg.eclipse.jetty.server.HttpChannelOverHttp#void
> onComplianceViolation(HttpCompliance, HttpCompliance, String)
> ADDEDorg.eclipse.jetty.server.HttpChannelState$Action#NOOP
> ADDEDorg.eclipse.jetty.server.HttpConfiguration#long
> getMinResponseDataRate()
> ADDED
> org.eclipse.jetty.server.HttpConfiguration#MultiPartFormDataCompliance
> getMultipartFormDataCompliance()
> ADDEDorg.eclipse.jetty.server.HttpConfiguration#void
> setMinResponseDataRate(long)
> ADDEDorg.eclipse.jetty.server.HttpConfiguration#void
> setMultiPartFormDataCompliance(MultiPartFormDataCompliance)
> ADDEDorg.eclipse.jetty.server.HttpOutput#void onFlushed(long)
> ADDEDorg.eclipse.jetty.server.MultiPartFormDataCompliance
> ADDEDorg.eclipse.jetty.server.MultiParts
> ADDEDorg.eclipse.jetty.server.Request#__MULTIPARTS
> REMOVEDorg.eclipse.jetty.server.Request#__MULTIPART_CONTEXT
> REMOVED

Re: [cross-project-issues-dev] [epp-dev] Photon M6 is available now

[Markus Knauer]

That was a minor error and has been corrected now.

Thanks,
Markus

On 16 March 2018 at 22:50, Mickael Istria  wrote:

> Hi,
>
> EPP site that's composited in SimRel repo ( http://download.eclipse.org/
> technology/epp/packages/photon/ ) seems to miss reference to the M6
> release so the "Check for updates" doesn't work going from M5 to M6.
> Is this expected?
>
> Cheers
>
> ___
> epp-dev mailing list
> epp-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/epp-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Photon EPP Repo Inconsistent

[Markus Knauer]

Thanks for mentioning it... it is fixed now with the following children in
the EPP Photon repo:

  



  

Regards,
Markus

On 12 February 2018 at 09:30, Ed Merks  wrote:

> I noticed that the EPP Photon composite repo is inconsistent right now. I
> noticed this because this familiar problem is cropping up every time I try
> to do completion in JDT:
>
> java.lang.NoSuchMethodError: org.eclipse.jface.internal.tex
> t.html.HTMLPrinter.insertPageProlog(Ljava/lang/StringBuilder
> ;ILorg/eclipse/swt/graphics/RGB;Lorg/eclipse/swt/graphics/
> RGB;Ljava/lang/String;)V
> at org.eclipse.jdt.internal.ui.text.java.AbstractJavaCompletion
> Proposal.getAdditionalProposalInfo(AbstractJavaCompletionProposal.
> java:610)
> at org.eclipse.jface.text.contentassist.AdditionalInfoControlle
> r$Timer$2$1.run(AdditionalInfoController.java:113)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
>
> The file /home/data/httpd/download.eclipse.org/technology/epp/package
> s/photon/compositeContent.jar does not contain a reference to
> /home/data/httpd/download.eclipse.org/technology/epp/packages/photon/M5/
> so when you try to install Photon M5 from the release train composite you
> actually end up with Photon M4 which seems to cause some inconsistent of
> JDT and JFace Text.
>
> Note that I see the following in /home/data/httpd/download.ecli
> pse.org/releases/photon/:
>
> 
> 
> 
>   
> 
> 
> 
>   
>   
>  
> 
> 
> 
>   
> 
>
> So while it might point at M5 via 201802021000, it points at an EPP
> composite that does not include M5 packages so you'll definitely end up
> with M4 packages and whatever those requirements decide to pull in, which
> seems to be a mixture of M4 and M5.
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Eclipse RAP participation in Photon

[Markus Knauer]

For the time being we plan to contribute Eclipse RAP 3.5.0 [1] to the
Photon release next year.
Our typical offset is +2


[1] https://projects.eclipse.org/projects/rt.rap/releases/3.5.0

Thanks and regards,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Problem with webtools repo for Oxygen.2

[Markus Knauer]

Thanks for taking care of it... I was investigating the same error because
I wasn't able to contribute RAP.

Can someone check that it isn't possible to push directly to the Git
repository without getting a build verification by Gerrit, and that this
setting is active for branches other than master?

Thanks,
Markus


On 15 November 2017 at 18:14, Jeff Johnston  wrote:

> In doing the latest Linux Tools update for Oxygen_update, I ran into an
> issue with a webtools repo which does not exist.  Using the date as a clue,
> I changed it from 3.9.0 to 3.9.2 and checked in a fix.  If this is wrong,
> webtools-folks, please change it.  Without the change, it would not
> validate the aggregation for me.
>
> How is it that people are getting fixes in with bugs when gerrit is
> enabled?  Is there a bug in the gerrit validation testing or is it being
> circumvented?
>
> -- Jeff J.
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] When will Oxygen.1 bits be in place?

[Markus Knauer]

Packages are available at their final location:

  /home/data/httpd/
download.eclipse.org/technology/epp/downloads/release/oxygen/1/

Thanks,
Markus



On 25 September 2017 at 19:54, Denis Roy 
wrote:

> Greetings,
>
> Looking at [1] it would appear Oxygen.1 is happening on Wednesday, the
> 27th of September.  Where are the EPP packages and the Oomph installer
> bits located? I can see them in:
>
>
> droy@dev1:/home/data/httpd/download.eclipse.org/technology/
> epp/downloads/release/oxygen> ls -l
> total 116
> drwxrwsr-x 2 mknauer technology.packaging 16384 Sep  4 02:00 1.RC2
> drwxrwsr-x 2 mknauer technology.packaging 20480 Sep  8 11:10 1.RC3
> drwxrwsr-x 2 mknauer technology.packaging 20480 Sep 18 07:04 1.RC4
> drwxrwsr-x 2 mknauer technology.packaging 20480 Jun 25 06:00 R
> drwxrwsr-x 2 mknauer technology.packaging 20480 Jun  9 01:48 RC3
> -rw-rw-r-- 1 mknauer technology.packaging 0 Jun 25 06:00 TIMESTAMP
>
> droy@dev1:/home/data/httpd/download.eclipse.org/technology/
> epp/downloads/release/oxygen> ls -l ../../../../../oomph/epp/oxygen/
>
> total 4
>
> -rw-rw-r-- 1 estepper tools.oomph 350 Aug 19  2016 config.ini
>
> drwxrwsr-x 2 estepper tools.oomph 245 Sep 21  2016 M1
>
> drwxrwsr-x 2 estepper tools.oomph 245 Nov  2  2016 M3
>
> drwxrwsr-x 2 estepper tools.oomph 245 Dec 14  2016 M4
>
> drwxrwsr-x 2 estepper tools.oomph 245 Feb  1  2017 M5
>
> drwxrwsr-x 2 estepper tools.oomph 245 Mar 15  2017 M6
>
> drwxrwsr-x 2 estepper tools.oomph 245 May 17 01:17 M7
>
> drwxrwsr-x 2 estepper tools.oomph 245 Jun 14 02:43 R
>
> drwxrwsr-x 2 estepper tools.oomph 245 May 31 06:07 RC2
>
>
> Thanks for your help.
>
>
> Denis
>
>
> [1] https://wiki.eclipse.org/Oxygen/Simultaneous_Release_Plan#Oxygen.1
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Photon M2 is available now

[Markus Knauer]

Hi Ed,

that's done now, the composite p2 repository has been created.

Thanks for the reminder,
Markus



On 22 September 2017 at 17:17, Ed Merks  wrote:

> I need the contents of /home/data/httpd/download.
> eclipse.org/technology/epp/packages/photon to be updated to contain
> references to the contents of /home/data/httpd/download.
> eclipse.org/technology/epp/packages/photon/M2.  The later properly
> contains the artifacts.jar and content.jar, but the former isn't a
> composite that provides access to M2.  I need this to generate the product
> catalog.  I hope that's made available very soon.
>
> On 22.09.2017 17:02, Christopher Guindon wrote:
>
> Hi,
>
> I am currently waiting for +1 from the EPP package maintainers before
> posting the Photon M2 packages on our website.
>
> We currently have two +1 (java & committers) but we need a minimum of five
> +1 before we can update the download page.
>
> I hope to make them available before the end of the day!
>
> -Christopher
>
>
> On Fri, Sep 22, 2017 at 10:19 AM, Frederic Gurr  foundation.org> wrote:
>
>> Hi,
>>
>> The Photon M2 repository is now "visible".
>>
>> => http://download.eclipse.org/releases/photon/
>>
>> The M2 EPP packages will be available soon from a tab under
>>
>> => https://www.eclipse.org/downloads/index-developer.php
>>
>>
>> Thanks for all contributions.
>>
>>
>> Regards,
>>
>> Fred
>>
>>
>> --
>> Frederic Gurr
>>
>> Release Engineer
>> Eclipse Foundation
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
> Christopher Guindon
> Lead Web Developer
> Eclipse Foundation
> Twitter: @chrisguindon
>
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [platform-releng-dev] [epp-dev] Issue with the macOS bundle signing, dmg packaging and signing

[Markus Knauer]

Same here... I enabled signing and building DMG files today, and now I'm
running our Oxygen.1 build (still running...).
The first .dmg files are already available!

Many thanks!

Regards,
Markus



On 14 September 2017 at 18:03, Daniel Megert 
wrote:

> Hi Mikaël (and all other involved parties)
>
> I was one of those pushing hard on this and also ranting. Kudos that you
> guys were able to solve the problem. We were able to have several
> successful builds in a row.
>
> Thanks a lot - really appreciated!
> Dani
>
>
>
> From:Mikaël Barbero 
> To:Eclipse Packaging Project 
> Cc:Mike Milinkovich , Webmaster <
> webmas...@eclipse.org>, platform-releng-dev-boun...@eclipse.org, Cross
> project issues , "Eclipse platform
> release engineering list." 
> Date:14.09.2017 10:47
> Subject:Re: [platform-releng-dev] [epp-dev] Issue with the macOS
> bundle signing, dmg packaging and signing
>
> Sent by:platform-releng-dev-boun...@eclipse.org
> --
>
>
>
> Hi,
>
> I'm glad to announced that the macOS services (.app signing, .dmg
> packaging and .dmg signing) have been restored on a new machine hosted
> within the Foundation VLAN.
>
> If you've disabled their usages, you can now re-enable them as it was
> before. The authentication layer I was talking about in my initial mail
> will be released later to possibly let us use resources outside of the
> Foundation VLAN. We will keep you posted.
>
> Thanks for your patience while we were resolving this issue.
>
> Cheers,
> Mikael
>
> --
> *Mikaël Barbero - *Eclipse Foundation
> IT Services - Release Engineering
>  (+33) 642 028 039
>  *mikael.barb...@eclipse-foundation.org*
> 
>  @mikbarbero
>
> Le 11 sept. 2017 à 19:56, Denis Roy <*denis@eclipse-foundation.org*
> > a écrit :
>
> Hi Dani,
>
> Just a clarification -- the current (broken) Mac services are hosted on
> our hardware. We are working on two fronts --
>
> 1. Provision a temporary new Mac to re-establish the current service
>
> 2. Provision managed/hosted Mac services to avoid these problems in the
> future, as our in-house hardware is not redundant, and does not scale.
>
> In the immediate terms, you can disable the signing parts in your build
> scripts for basically no cost, as signing is likely not needed on I-builds,
> nor to validate test results.
>
> Mikael has offered to manually sign your the last release candidates so
> that release deadlines can be met.
>
> I apologize for the inconveniences this causes, and thank you for your
> continued patience while we resolve this issue and make it better.
>
> Denis
>
>
> On 11/09/17 08:14 AM, Daniel Megert wrote:
> Can you explain why this critical/blocking hardware is hosted outside the
> Eclipse Foundation, creating more/new issues and delays? Our automated
> builds don't play well with filing bugs (for signing and DMG creation) and
> wait for resolution ;-). Ah, and BTW, our latest Photon M2 candidate build
> just failed again:
> *http://download.eclipse.org/eclipse/downloads/drops4/I20170911-0405/*
> 
>
> Dani
>
>
>
> From:Mikaël Barbero **
> 
> To:"Eclipse platform release engineering list."
> ** ,
> Eclipse Packaging Project ** 
> Cc:Webmaster ** ,
> Cross project issues **
> 
> Date:07.09.2017 14:07
> Subject:[platform-releng-dev] Issue with the macOS bundle
> signing,dmg packaging and signing
> Sent by:*platform-releng-dev-boun...@eclipse.org*
> 
> --
>
>
>
> (cross-posting to platform-releng, epp-dev and cross-projects)
>
> Hi,
>
> Recently, we've been facing a lot of issues with the services we provide
> for macOS: UI testing, macOS .app bundles signing and DMG files creation
> and signing. It has been a combination of hardware, software and network
> failures and these issues have already impacted some projects, delaying
> their milestones/releases and consuming a lot of time from their teams.
>
> Since the beginning of the week, we've setup a new machine to run UI tests
> from the Hudson shared instance (*https://hudson.eclipse.org/shared/*
> ). This machine is not hosted on our
> infra, and thus not everything that was possible can be done on the new
> machine (most notably, it's not possible 

Re: [cross-project-issues-dev] Oxygen RC2 staging repository is completed

[Markus Knauer]

Thanks for using and testing the package.
We've had too many infrastructure problems this week and builds were
failing due to pack200 problems. The only way to contribute to RC2 was to
disable all this.

We are aware of that, but so far I didn't have the time to investigate.
Although it seems similar to Tom's problem, we are quite sure that we use
the correct JVM version for pack200.

Thanks,
Markus


On 2 Jun 2017 17:34, "Wayne Beaton" 
wrote:

> I just pulled updates and got a warning that a RAP bundle isn't signed.
>
> Warning: You are installing software that contains unsigned content. The
> authenticity or validity of this software cannot be established. Do you
> want to continue with the installation?
>   /home/apps/eclipse-rcp-oxygen-M6-linux-gtk-x86_64/eclipse/
> features/org.eclipse.rap.tools.feature_3.2.0.20170531-0554
>
> Wayne
>
> On Wed, May 31, 2017 at 6:41 PM, Frederic Gurr  foundation.org> wrote:
>
>> Hi,
>>
>> it's past 6pm EDT and the last build is done.
>> Therefore I call the staging repository for Oxygen RC2 complete.
>> => http://download.eclipse.org/staging/oxygen/
>> 
>>
>> SimRel aggregation builds are disabled until Friday after the release at
>> 10am EDT.
>>
>> Thanks once again for all contributions and remember to test, test and
>> test. ;)
>>
>> Regards,
>>
>> Fred
>>
>> --
>> Frederic Gurr
>>
>> Release Engineer
>> Eclipse Foundation
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> --
> Wayne Beaton
> Director of Open Source Projects
> The Eclipse Foundation
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Jetty version in Oxygen

[Markus Knauer]

We are using (and contributing) some of the Jetty bundles in Eclipse RAP.

As I wrote on your PMC mailing list, I'd be willing to give it a try, and
if it works move to the new version next week. But as it looks today,
there's not even a p2 repository available, which prevents easy consumption
on our side.

What are the other projects planning?

Thanks,
Markus

On 2 June 2017 at 15:07, Aleksandar Kurtakov  wrote:

> There is new staged release for Jetty 9.4.6 [1]. In platform Jetty is
> still at version 9.4.5 and the question of updating the version for
> RC4 pops up. On one side it's a bit late in the cycle (although same
> thing happened last year [2]) and we can not try the staged version
> imediately due to [3], on the other the possibility for multiple
> versions being shipped is a stability risk (as seen with httpclient
> and guava).
> So is any project planning to contribute Jetty 9.4.6 to Oxygen?
>
> [1] https://dev.eclipse.org/mhonarc/lists/jetty-dev/msg03018.html
> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=495069
> [3] https://github.com/eclipse/jetty.project/issues/1587
>
> --
> Alexander Kurtakov
> Red Hat Eclipse Team
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] missing Jetty dependencies of projects other than RAP

[Markus Knauer]

Hi all,

I was trying to contribute our RAP M7 build to the Simultaneous Release
when I found out that our contribution leads to some missing dependencies
to Jetty bundles from other projects. It looks like some projects were
relying that RAP contributes a specific version of those bundles, but we
don't... we always try to align our Jetty bundle versions to the ones that
Eclipse Platform uses.

Short version: We are using (and contributing) Jetty 9.4.5.v20170502 now,
which breaks other projects that define a dependency to other versions
without contributing these bundles. In order to get green build I had to
disable temporarily the full dependency chain:

  - webtools.aggrcon
  - jwt.aggrcon
  - soa-bpel.aggrcon
  - m2e-wtp.aggrcon
  - scout.aggrcon

It is documented in the following bug - please remember to enable your
contribution again after fixing the issues!

  *Bug 516750*  - Missing
Jetty dependencies after adding RAP 3.2M7 to Oxygen build
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=516750

Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Severe regression in PDT Neon.3 RC4 - chance for a respin?

[Markus Knauer]

Any status updates and progress on this issue?

Thanks,
Markus

On 13 March 2017 at 19:57, Kaloyan Raev  wrote:

> Thank you, Fred!
>
> PDT 4.3 RC5 is released [1]
> I prepared the Gerrit patch for the Neon SimRel repo [2]. You still need
> to merge it.
>
> [1] http://download.eclipse.org/tools/pdt/updates/4.3-rc5
> [2] https://git.eclipse.org/r/#/c/92967/
>
> Kaloyan Raev | Zend Studio Team Lead
> Rogue Wave Software, Inc.
> Accelerating Great Code
> *M* +359 887 648 663
> www.roguewave.com / kaloyan.r...@roguewave.com
>
> On 03/13/2017 08:21 PM, Frederic Gurr wrote:
>
> Hi Kaloyan,
>
> If this has not be done already, please revert the patch in PDT, release
> a RC5 milestone and provide the new URL(s).
>
> I will respin the Neon staging P2 repo tomorrow morning.
>
> Regards,
>
> Fred
>
> On 10.03.2017 10:24, Kaloyan Raev wrote:
>
> Hi,
>
> While testing the PHP EPP Neon.3 RC4 we found a severe regression [1].
> While it does not affect the Simultaneous Release as a whole, it is
> something that would affect most of the PHP users.
>
> I know the simplest and risk free solution is PDT to have a maintenance
> release on the date of the Neon.3 release train. But, as the affected
> workflow is one that would be executed early after starting the IDE,
> most probably, the affected users would not notice that there is a
> maintenance update they need to apply. The effect of freezing the IDE
> would result in a very negative experience with the Eclipse IDE.
>
> For the above reasons, I'd like to ask what are our chances for
> respinning the Neon staging p2 repo?
>
> Technically speaking, we need to revert one patch in PDT and release a
> RC5 milestone. Then the Neon staging p2 repo needs to be respun and then
> the EPP packages.
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=513432
>
> --
> Kaloyan Raev| Zend Studio Team Lead
> Rogue Wave Software, Inc.
> Accelerating Great Code
> *M* +359 887 648 663www.roguewave.com  
>  / kaloyan.r...@roguewave.com
>
>
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Neon.3 RC4 status?

[Markus Knauer]

Is Neon.3 RC4 ready and available from the staging repository? Or do we
have reports from projects requiring more time?

Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Neon.3 RC3 staging repo is complete

[Markus Knauer]

I hope there weren't any changes in the last 20 hours... the EPP package
build run yesterday at about 4pm UTC.


Regards,
Markus

On 3 March 2017 at 12:26, Frederic Gurr  wrote:

> Obviously I was late with this email. I somehow got my weekdays mixed up
> (it still feels like a Thursday). My apologies!
>
> On 03.03.2017 11:43, Frederic Gurr wrote:
> > Staging is complete and ready for EPP packages to be created.
> >
> > http://download.eclipse.org/staging/neon/
> >
> > The "Neon jobs" have been disabled temporarily and will be re-enabled
> > on Friday, after the EPP packages are done.
> >
> > Thanks everyone for participating.
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Something wrong with bugzilla?

[Markus Knauer]

bugzilla.eclipse.org seems to use a wildcard certificate issued for CN = *.
eclipse.org, very likely the same that is used for other services and URLs,
too.

It has been renewed 17/01/17 and is valid until 02/03/2020 with the
fingerprints below. My personal guess is that *some* front end servers
serving bugzilla are using the relatively new certificate, while others are
still using a now expired certificate (which would explain why only some
people are having problems).

Just a blind guess...

Regards,
Markus



SHA256
32:74:4F:FB:2A:B4:FE:66:5A:A8:5A:16:5E:B7:0A:BB:07:34:2A:E5:0E:72:0C:9B:3C:F4:CE:EB:0F:77:C6:28
SHA1 9D:51:60:10:5E:72:48:57:77:8B:1A:1A:B8:35:0C:0D:2E:A4:C6:F5



On 6 February 2017 at 13:27, Gunnar Wagenknecht 
wrote:

> Hi Lars,
>
> That's a sign that there is a replication issue or lag. But I cannot
> access Bugzilla at all currently due to an expired SSL certificate.
> Previously Chrome allowed me to ignore that but not this time it seems.
>
> --
> Gunnar Wagenknecht
> gun...@wagenknecht.org, http://guw.io/
>
>
>
>
>
>
> On 6 Feb 2017, at 11:58, Lars Vogel  wrote:
>
> Hi,
>
> my Bugzilla Search Queries do not return my latest updates. First I
> assume bad network did swallow my updates but I just opened a bug for
> JDT and I'm not able to find it again via the search.
>
> Is this a know issue?
>
> Best regards, Lars
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] hipp9 overloaded

[Markus Knauer]

I see similar problems on hipp8. Its reported load is between 1 and 2 at
the moment, sometimes less, i.e. not very high, but the EPP package builds
are extremely slow, much slower than usual. A few months ago in October
these builds used to take 1:20h [1], now we are close to 6 hours [2] which
is 4 times slower for the same build. In both cases, builds were running on
a day during Simultaneous Release week which rules out this as a reason for
the increased duration.

Maybe its worth to look at this host, too, as the increased build time
doesn't seem to be caused by a high load of the CPU.

And I highly appreciate your efforts to distribute CPU resources in a
better way!

Much thanks,
Markus

[1] https://hudson.eclipse.org/packaging/job/neon.epp-tycho-build/448/
[2] https://hudson.eclipse.org/packaging/job/oxygen.epp-tycho-build/183/



On 2 February 2017 at 01:22, Frederic Gurr 
wrote:

> Hi,
>
> Unfortunately hipp9 has been experiencing a near-constant high load
> during work hours. Due to a few projects hogging resources other
> projects are severely constrained and have problems running their builds
> in a timely manner.
>
> To fix this, I have taken the following near term steps:
>
> - Papyrus HIPP
>   - disabled execution of concurrent builds for "Papyrus-Gerrit-Oxygen"
>   - limited the number of executors to 2
>
> - EMF Compare HIPP
>   - limited the number of executors to 2
>
> I will also move the EMF Compare HIPP to a different hipp machine
> tomorrow at 9am EST. Downtime will be less than one hour.
>
> We will also investigate how CPU usage can be limited to ensure a fair
> distribution of resources.
>
> Regards,
>
> Fred
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] SimRel download stats

[Markus Knauer]

It looks like the JDT feature isn't prepared for p2 download stats. Most
projects are using features (and not plugins) of the stats, but AFAIK it is
really up to the projects to prepare their p2 repositories beforehand. If
you download the artifacts.jar file from

  http://download.eclipse.org/releases/neon/201609281000/artifacts.jar

you'll see the base URL that is used by p2 for the statistic HEAD requests:

  

Then you could grep and search for 'download.stats' properties in the
artifact.xml file which will give you a list of IUs that are prepared for
p2 stats.
(Of course, you can do the same for the EPP packages with the file at
http://download.eclipse.org/technology/epp/packages/neon/artifacts.jar).

Does that answer your question?

Regards,
Markus


On 6 October 2016 at 13:14, Mickael Istria  wrote:

> Hi all,
>
> I'm trying to sort out some download stats about the different plugins in
> SimRel.
>
> I tried for example to look for http://download.eclipse.org/
> releases/neon/201606221000/features/org.eclipse.jdt_3.12.
> 0.v20160606-1100.jar on https://dev.eclipse.org/committers/committertools/
> stats.php but got no result (whereas I'm pretty sure that at least one
> person did a p2 install of JDT one day). Are download stats available for
> SimRel? If so, what's the trick to see them?
>
> Thanks in advance
> --
> Mickael Istria
> Eclipse developer for Red Hat Developers 
> My blog  - My Tweets
> 
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] MPC participation in Oxygen

[Markus Knauer]

Well, all EPP packages depend on the MPC on Oomph and on... :(
But these projects could be disabled easily without too much negative
side-effects, whereas other projects cannot be disabled.

Regards,
Markus

On 10 August 2016 at 22:43, Carsten Reckord  wrote:

> Unfortunately, MPC will stay disabled for Oxygen M1, because we depend on
> USS (Eclipse User Storage), currently a part of Oomph, which is not yet
> enabled.
>
> I don't believe anyone in the release train depends on MPC, so I hope this
> doesn't cause any problems.
>
> Carsten
>
> > -Original Message-
> > From: cross-project-issues-dev-boun...@eclipse.org [mailto:
> cross-project-
> > issues-dev-boun...@eclipse.org] On Behalf Of Carsten Reckord
> > Sent: Wednesday, August 10, 2016 6:35 PM
> > To: Cross project issues 
> > Subject: [cross-project-issues-dev] MPC participation in Oxygen
> >
> > Hi all,
> >
> > MPC will participate in Oxygen with MPC 1.6.0 [1] at its usual +3 offset.
> >
> > Thanks,
> > Carsten
> >
> > [1]
> > https://projects.eclipse.org/projects/technology.packaging.
> mpc/releases/1.
> > 6.0
> >
> > ___
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > To change your delivery options, retrieve your password, or unsubscribe
> > from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] RAP will participate in Oxygen

[Markus Knauer]

Hi everyone,

the RAP team will participate in Oxygen with RAP 3.2 and deliver with our
usual offset of +2.
The release record is pending as long as projects.eclipse.org is down...

Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Bugzilla + Gerrit + ? down

[Markus Knauer]

I haven't tried Gerrit, but I see sporadic problems with the wiki now.

All requests take a very long time, sometimes they are successful, but most
of the time I'm getting a message like "A database query error has
occurred. This may indicate a bug in the software."

Judging from https://dev.eclipse.org/committers/help/status.php I would say
that everything runs smooth, but the wiki doesn't. Are the DB problems back?

Regards,

Markus




On 17 June 2016 at 11:52, Laurent Redor  wrote:

> These restarts change nothing. Is anyone seeing the same problem?
>
> In the gerrit-trigger plugin page, I can see in the warning message that
> the number of items in the "Gerrit-trigger send commands queue" increases.
>
> Le 17/06/2016 à 10:10, Matthias Sohn a écrit :
>
> if you are Hudson admin you can try to restart the gerrit-trigger plugin
> here
> https://hudson.eclipse.org/sirius/gerrit-trigger/
>
> otherwise try if restarting Hudson helps, you can trigger a restart Hudson
> HIPP control here
> https://dev.eclipse.org/site_login/myaccount.php
>
> -Matthias
>
>
> On Fri, Jun 17, 2016 at 9:42 AM, Laurent Redor 
> wrote:
>
>> Hi,
>>
>> The sites are now accessible. Since this problem, it seems that the
>> gerrit jobs launched from Hudson (HIPP instance) do not give feedback on
>> the corresponding gerrit.
>> Example: Gerrit https://git.eclipse.org/r/#/c/75413 has 3 patch sets but
>> no validation from Hudson. The corresponding jobs are launched ([1], [2],
>> [3], [4], ...) but without validation on Gerrit.
>>
>> Is it a problem related to the yesterday infra problem (something not
>> correctly restarted)?
>>
>> Regards,
>>
>> Laurent
>>
>> [1]
>> https://hudson.eclipse.org/sirius/view/gerrit/job/sirius.gerrit.build-neon/1198/
>> [2]
>> https://hudson.eclipse.org/sirius/view/gerrit/job/sirius.gerrit.build-neon/1208/
>> [3]
>> https://hudson.eclipse.org/sirius/view/gerrit/job/sirius.gerrit.build-neon/1212/
>> [4]
>> https://hudson.eclipse.org/sirius/view/gerrit/job/sirius.gerrit.tests-mars/4158/
>>
>>
>>
>> Le 16/06/2016 à 15:21, Matthew Ward(Bt. Kt. SSA.) a écrit :
>>
>> We've got things going on the master and the slave should be catching up.
>>
>> -Matt.
>>
>> On 06/16/2016 09:04 AM, Matthias Sohn wrote:
>>
>> Gerrit seems to work again
>>
>> ___
>> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe from 
>> this list, 
>> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>> --
>>
>> *Laurent Redor*
>> +33 2 51 13 52 18
>>
>> 
>>
>> 7 Boulevard Ampère - Carquefou - France
>> *obeo.fr*  | *twitter*
>>  | *linkedin*
>> 
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> --
>
> *Laurent Redor*
> +33 2 51 13 52 18
>
> 
>
> 7 Boulevard Ampère - Carquefou - France
> *obeo.fr*  | *twitter*
>  | *linkedin*
> 
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Bugzilla + Gerrit + ? down

[Markus Knauer]

Hi everyone,

I wanted to file a bug that Gerrit is not reachable any more, but then I
found out that I cannot access Bugzilla, too.

Is anyone seeing the same, i.e. errors when accessing Gerrit and Hudson web
interfaces?

Regards,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Simrel validation fails for Jetty

[Markus Knauer]

The Jetty version in the RAP Tools has been updated, and the project is
re-enabled in the SimRel build.

Regards,
Markus


On 8 June 2016 at 09:03, Markus Knauer <mkna...@eclipsesource.com> wrote:

> Thanks, good that we have the SimRel build that detects such problems.
> The RAP Tools problem is found and I will contribute a new version when
> our build is ready.
>
> Thanks,
> Markus
>
>
>
> On 8 June 2016 at 03:07, David M Williams <david_willi...@us.ibm.com>
> wrote:
>
>> I forgot to attach the "patch" as I said I would. When these projects are
>> ready to commit new versions, just remove the enabled="false" attribute.
>>
>> diff --git a/rap-tools.b3aggrcon b/rap-tools.b3aggrcon
>> index da65673..ae5b1cd 100644
>> --- a/rap-tools.b3aggrcon
>> +++ b/rap-tools.b3aggrcon
>> @@ -4 +4 @@
>> -> versionRange="[3.1.0,3.2.0)">
>> +> name="org.eclipse.rap.tools.feature.feature.group"
>> versionRange="[3.1.0,3.2.0)">
>> diff --git a/webtools.b3aggrcon b/webtools.b3aggrcon
>> index 0048050..9ca1c0d 100644
>> --- a/webtools.b3aggrcon
>> +++ b/webtools.b3aggrcon
>> @@ -54 +54 @@
>> -> name="org.eclipse.wst.server_adapters.feature.feature.group">
>> +> name="org.eclipse.wst.server_adapters.feature.feature.group">
>>
>>
>>
>>
>> From:David M Williams/Raleigh/IBM@IBMUS
>> To:Cross project issues <cross-project-issues-dev@eclipse.org>,
>> Date:06/07/2016 09:04 PM
>> Subject:Re: [cross-project-issues-dev] Simrel validation fails
>> for Jetty
>> Sent by:cross-project-issues-dev-boun...@eclipse.org
>> --
>>
>>
>>
>>
>> > In particular we haven't changed anything in CDO between RC3 and
>> > RC4. Does someone know what this can mean and what I
>> > can do to get my contribution through?
>>
>> I do! Its all related to the jetty change Carl mentioned. While the
>> Platform has not been "contributing" Jetty 9.3.5 for a week or two, I
>> suspect someone else was, thus no issues, and now that "other project" has
>> also moved up to 9.3.9.
>>
>> There are actually two issues:
>>
>> Rap Tools, and
>> Web Tools Server adapters.
>>
>> Below is a patch showing what I could disable, and allow the validation
>> to still succeed. I'm sure that functionality will be broken, and EPP
>> package may not even build, until Webtools and RapTools actually submit a
>> fix, but in the mean time, I will submit these "disabled" versions of RAP
>> Tools and Webtools, just so others can validate as best you can.
>>
>> I hope that helps,
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Simrel validation fails for Jetty

[Markus Knauer]

Thanks, good that we have the SimRel build that detects such problems.
The RAP Tools problem is found and I will contribute a new version when our
build is ready.

Thanks,
Markus


On 8 June 2016 at 03:07, David M Williams  wrote:

> I forgot to attach the "patch" as I said I would. When these projects are
> ready to commit new versions, just remove the enabled="false" attribute.
>
> diff --git a/rap-tools.b3aggrcon b/rap-tools.b3aggrcon
> index da65673..ae5b1cd 100644
> --- a/rap-tools.b3aggrcon
> +++ b/rap-tools.b3aggrcon
> @@ -4 +4 @@
> - versionRange="[3.1.0,3.2.0)">
> + name="org.eclipse.rap.tools.feature.feature.group"
> versionRange="[3.1.0,3.2.0)">
> diff --git a/webtools.b3aggrcon b/webtools.b3aggrcon
> index 0048050..9ca1c0d 100644
> --- a/webtools.b3aggrcon
> +++ b/webtools.b3aggrcon
> @@ -54 +54 @@
> - name="org.eclipse.wst.server_adapters.feature.feature.group">
> + name="org.eclipse.wst.server_adapters.feature.feature.group">
>
>
>
>
> From:David M Williams/Raleigh/IBM@IBMUS
> To:Cross project issues ,
> Date:06/07/2016 09:04 PM
> Subject:Re: [cross-project-issues-dev] Simrel validation fails
> for Jetty
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> --
>
>
>
>
> > In particular we haven't changed anything in CDO between RC3 and
> > RC4. Does someone know what this can mean and what I
> > can do to get my contribution through?
>
> I do! Its all related to the jetty change Carl mentioned. While the
> Platform has not been "contributing" Jetty 9.3.5 for a week or two, I
> suspect someone else was, thus no issues, and now that "other project" has
> also moved up to 9.3.9.
>
> There are actually two issues:
>
> Rap Tools, and
> Web Tools Server adapters.
>
> Below is a patch showing what I could disable, and allow the validation to
> still succeed. I'm sure that functionality will be broken, and EPP package
> may not even build, until Webtools and RapTools actually submit a fix, but
> in the mean time, I will submit these "disabled" versions of RAP Tools and
> Webtools, just so others can validate as best you can.
>
> I hope that helps,
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] New UUID in Eclipse Platform

[Markus Knauer]

On 5 June 2016 at 11:43, Ed Willink  wrote:

> What is the process for requesting a respin to have the UUID facility
> removed pending a more acceptable realization?


I've opend bug 495484

  *Bug 495484*  - Remove
unique user tracking id in Neon
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=495484

to officially ask for removal and re-spin of RC4.


On 5 June 2016 at 13:43, Stephan Herrmann 
wrote:

> Technical question: is disabling UUID s.t. which EPP can do?
>

As far as I can see: No.


Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] New UUID in Eclipse Platform

[Markus Knauer]

Ian,

you are right in your assumption that all this won't change my opinion in
any way, in fact, the opposite is true.

The implementation of AERI (the error reporter) and the former EPP Usage
Data Collector are both opt-in implementations. Both have been carefully
designed to be as transparent as possible, no user is forced to send any
data, there is no hidden feature or side-channel, the data is anonymised,
and the mail address that you were referring to in your response is only
optional. AERI has been implemented in an open way as it is appropriate for
an Open Source community, integrated early enough in the release cycle, and
based on feedback by and with review from the community.

This is clearly a major difference to the way the Eclipse Foundation
introduced the implementation of the UUID and its use in Platform, p2, MPC,
and as a last minute change in AERI. (I just want to point out that I am
thankful that the AERI team pushed on making the UUID introduction public,
otherwise some doubts are admissible that it would have been communicated
at all.)

Yes, you are right, I could live with it if it was an opt-in instead of
this hidden opt-out. I called it a 'theoretical' opt-out for a number of
reasons:
- There is no user interface within Eclipse, no preference page it's
just nothing. A void.
- The user isn't told about the existence or about the creation of the UUID.
- The user needs to leave the program ("Eclipse") that he or she is using
to edit an external file.
- And it is an after-the-fact thing. Under normal circumstances the file
can only be edited after its creation by Eclipse. Kind of a short-circuit.
Rethinking, no, that is not even something that can be called opt-out.

The introduction of such IDs is often justified by possible future
improvements, but so far I have not seen any plan what to learn from this
additional information. What is the concrete question that we hope to
answer by introducing the UUID? If most (closed source) organisations are
moving into the data-driven decision direction, this is no reason that the
(open source) Eclipse organisation should move into the same direction. I
think we can do better!

In Europe (I cannot speak for other areas), there are regulations in place
regarding e.g. cookies ('devices') and IMO this per-user UUID is no
different. The European Legislation is very clear about the usage of those
IDs - you may read (24), (25) of [1]. I have serious doubts that the usage
of the UUID which is bound to a single user is in accordance with European
law, and I guess that there is no question that it has to be an opt-in. I
hope that Eclipse Legal has been involved in its development, and that it
did a thorough background check, but so far I haven't seen any indication
that this has been done.

I strongly believe that this UUID is the worst thing that can happen in an
Open Source community like Eclipse, and that the Eclipse Foundation looses
a lot of trust and reputation with this.

Eclipse Neon cannot be released with the current implementations in
Platform, p2, MPC, and AERI in Neon, there are too many open issues that
need to be solved before introducing anything like that.

Markus



[1] http://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32002L0058





On 4 June 2016 at 17:11, Ian Skerrett  wrote:

> Markus
>
>
>
> I think you have captured many of the key concerns so I would like to try
> to respond. I don’t expect to change your opinion but I do believe a
> response is due and hopefully I can express a point of view.
>
>
>
> Btw, I am flying to Europe this afternoon so I apologize in advance if I
> don’t respond quickly to this thread.
>
>
>
>
>
> So late in the release cycle?
>
> >> The initial bug was opened in March and the initial code was available
> in M7. Unfortunately I only made cross-projects aware now.
>
>
> Without any broader involvement of and verification by the Eclipse
> community? Just an announcement after Neon RC3 (or after Platform RC4)?
>
> >> Point taken.
>
>
> Not as an opt-in like in AERI?
>
> >> If I understand correctly AERI collects email addresses. UUID is not
> associated with personable identifiable information.
>
>
> Without any further notice to the user at all?
>
> >> A notice is in the 4.6 N I can also broadcast to wider channels.
>
>
> WITHOUT any working opt-out mechanism? Giving the user the theoretical
> chance to edit a file and set a property to '0' cannot be called a valid
> opt-out option.
>
> >> Not sure why you say this is theoretical. We could look at a UI in the
> preferences but my guess is the real concern is the opt-in vs opt-out.
>
> Let me try to explain the opt-out reasoning. Again, I don’t expect to
> change your opinion.
>
> We have been analyzing the log files for p2, mpc and download servers
> using IP addresses. Unfortunately, it is difficult to equate one IP with
> one developer. Some IP addresses represent many developers, some seem to be
> spamming our 

Re: [cross-project-issues-dev] New UUID in Eclipse Platform

[Markus Knauer]

So late in the release cycle?
Without any broader involvement of and verification by the Eclipse
community? Just an announcement after Neon RC3 (or after Platform RC4)?
Not as an opt-in like in AERI?
Without any further notice to the user at all?
WITHOUT any working opt-out mechanism? Giving the user the theoretical
chance to edit a file and set a property to '0' cannot be called a valid
opt-out option.
And all that from an Open Source organisation?

I believe our users downloading Eclipse deserve more respect. Silently
introducing even more user tracking is nothing that I want to be identified
with.

Markus



On 4 June 2016 at 10:31, Ed Willink  wrote:

> Hi
>
> This hardly seems last minute at all. My
> ${user.home}/.eclipse/eclipse.uuid has a
>
> #Tue May 03 08:41:32 BST 2016
>
> timestamp indicating that it was almost certainly created by M7. Why the
> one month delay in notifying us?
> Why no start up dialog in M7 onwards informing us that we are being
> default opted in?
>
> Regards
>
> Ed Willink
> On 04/06/2016 06:50, Christian Campo wrote:
>
> hi
>
> is that a last minute idea that came up recently or why is it only
> revealed now that is pretty much too late for any change ?
>
> Gruß
>
> Christian
>
> Am 03.06.2016 um 17:13 schrieb Ian Skerrett < 
> ian.skerr...@eclipse.org>:
>
> All,
>
> I wanted to make everyone aware that a UUID has been added to the Eclipse
> Platform [1] and is available in the current Neon RC.  This was done at the
> request of the Eclipse Foundation.
>
>
>
> The UUID is automatically generated and stored in the
> ${user.home}/.eclipse/eclipse.uuid file. The UUID does not contain any
> personally identifiable information. If a user do not want to have this
> property set they are instructed to set eclipse.uuid=0. Information about
> the UUID has been included in the Eclipse Platform N [2].
>
> The UUID will be automatically added to the user-agent of http requests to
> *.eclipse.org servers. For Neon, the projects that make these types of
> requests include p2 [1], MPC [3] and AERI [4]. I would expect other
> projects will add a uuid in the future.
>
>
>
> The immediate questions for many people are 1) why are we doing this, and
> 2) what about the privacy concerns.  Let me attempt to answer both of these
> questions.
>
> Why are we doing this?
>
> The Eclipse Foundation has started an program to better understand our
> user community. We are using a log file analysis service, Splunk, to
> analyze many of our log files to get a better idea of how people are using
> Eclipse. For instance, how many people actively use Eclipse, what version
> of Java is the most popular with the Eclipse user community, what version
> of Eclipse Platform is being used or what operating system is being used?
> In the past, this type of information was typically a ‘best guess’. We
> believe can do better by having the actual data of our user community. The
> UUID will allow us to get a more accurate answer to many of these questions.
>
> What about the privacy concerns?
>
> The UUID is anonymous and does not contain personably identifiable
> information. We only intend to use and analyze the UUID at an aggregate
> level. A user is able to opt-out of sending a UUID by setting
> eclipse.uuid=0. The Eclipse Foundation has a published Privacy Policy [5]
> that details our specific practices.
>
>  Please let me know if you have any questions or concerns. I appreciate
> this might be a sensitive topic but I do believe it is the right thing to
> do for the Eclipse community.
>
> Regards
>
> Ian
>
>
>
>  [1] 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=490112
>
> [2] 
> https://www.eclipse.org/eclipse/news/4.6/platform.php
>
> [2] 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=492916
>
> [3] 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=492917
>
> [4] 
> https://eclipse.org/legal/privacy.php
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> 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] Eclipse RAP RC3 contribution update to Neon RC3

[Markus Knauer]

Hi everyone,

yesterday we contributed our RAP 3.1 RC3 build to Neon as planned (+2 day),
but decided today to fix an issue with our included Jetty version (see bug
495117 [1]) by upgrading to 9.3.9.

This updated contribution has now been pushed to Neon RC3; there are no
other changes in our update.

Just as an overview the p2 repositories...

  Eclipse RAP 3.1 Runtime RC3
  http://download.eclipse.org/rt/rap/3.1/RC3-20160601-1045

  Eclipse RAP 3.1 Tools RC3
  http://download.eclipse.org/rt/rap/tools/3.1/RC3-20160530-1326

Thanks and regards,
Markus



[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=495117
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Neon RC2 is complete

[Markus Knauer]

10 out of 14 Eclipse Neon RC2 packages are now available from

  https://www.eclipse.org/downloads/index-developer.php

We'll enable the remaining ones as soon as a +1 from a package maintainer
arrives.

Thanks,
Markus

On 27 May 2016 at 16:15, David M Williams  wrote:

> We have "turned on" the repositories for Neon RC2 (which is now a
> composite of RC2, RC1, and M7).
>
> The EPP packages will be waiting a bit for some more mirrors to replicate,
> and 5 more package maintainers must give their +1 -- but, they should be
> available later this afternoon, AFAIK.
>
> Thank you, to all you contributors, for this "very close to the end"
> release candidate.
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [epp-dev] [NEON M6] Eclipse Foundation office will be closed on Good Friday

[Markus Knauer]

Sounds like the perfect solution to me, highly appreciated... my personal
opinion is that we should release on Tuesday, i.e. after Easter Monday. I
hope that'll give us enough time to get enough +1 votes for the packages.

Thanks,
Markus


On 23 March 2016 at 20:40, David M Williams 
wrote:

> I have not seen Markus on-line, to check is schedule, but
>
> I suggest we delay until Monday (3/28) - at least, possibly Tuesday, to
> allow time for creation and adequate testing. I think that would be less
> stressful, higher quality, and give us time to fix the signing service (bug
> *489890* ).
>
> I hope that those that can not do it Monday or Tuesday  (due to planned
> vacations, etc.) can find a "back up" person to sign-off on their EPP
> package.
>
> Given this (and the problems with signing), let's say the Sim. Release
> repo will "freeze" on Thursday night, 5 PM (Eastern) instead of tonight.
>
> Let us know if anyone anticipates issues with this change in schedule that
> we have not anticipated.
>
>
>
>
>
> From:Christopher Guindon 
> To:epp-...@eclipse.org,
> Date:03/23/2016 02:11 PM
> Subject:Re: [epp-dev] [NEON M6] Eclipse Foundation office will be
> closed on Good Friday
> Sent by:epp-dev-boun...@eclipse.org
> --
>
>
>
> Correction:
>
> 10:00am not 10:00pm :)
>
> On 2016-03-23 2:09 PM, Christopher Guindon wrote:
> Hi package maintainers,
>
> I noticed today in my calendar that we are releasing Neon M6 on Friday,
> March 25th @ 10:00pm EST.
>
> Unfortunately the Eclipse Foundation office will be closed on Good Friday.
>
> Can we move the release to tomorrow (Thursday, March 24th @ 10:00pm EST)
> or next Monday (Monday, March 28th @ 10:00pm EST)?
>
>
> --
> Christopher Guindon
> Lead Web Developer
> Eclipse Foundation
> Twitter: @chrisguindon
>
> [image: EclipseCon NA 2016] 
>
>
> ___
> epp-dev mailing list
> *epp-...@eclipse.org* 
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> *https://dev.eclipse.org/mailman/listinfo/epp-dev*
> 
>
> --
> Christopher Guindon
> Lead Web Developer
> Eclipse Foundation
> Twitter: @chrisguindon
>
> [image: EclipseCon NA 2016] 
> ___
> epp-dev mailing list
> epp-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/epp-dev
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse asked if I trust the Eclipse signing certificate, if I want to install something

[Markus Knauer]

Did you check the JVM and their trusted certificates? Any changes and/or
updates there?
Are the root certificates that are mentioned in the certificate chain
trusted?

I tried it with my own Mars.1 RCP/RAP package and it worked without showing
me this dialog.

Regards,
Markus


On 17 December 2015 at 11:50, Lars Vogel  wrote:

> Recently Eclipse started to ask me to confirm that I trust the Eclipse
> certificate, if I want to install something.
>
> Example: Using 4.5.1.M20150904-0015 under Ubuntu 15.10 while
> installing Wikitext support from
> http://download.eclipse.org/mylyn/snapshots/weekly
>
> Is this expected? I used to be that the Eclipse IDE would trust
> Eclipse signed content automatically
>
> Best regards, Lars
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Stats on OS being used

[Markus Knauer]

I'd recommend to use a search string such as

  /stats/technology/epp/packages/mars/%feature%

which gives you some numbers about p2 installs of the EPP features, but I'm
unsure how accurate these numbers are because of the heavy caching in Oomph.

Thanks,
Markus



On 18 November 2015 at 22:28, Torkild Ulvøy Resheim 
wrote:

> Just curious; since Mars I’ve been using the Eclipse installer to do a
> dozen or so installations. How are these counted?
>
> Best regards,
> Torkild
> > 18. nov. 2015 kl. 18.39 skrev Marcel Bruch  >:
> >
> > Given Eike’s numbers, Mac users make 7 % of the downloads.
> > In the last 90 days they 'contributed' 15% of all error reports.
> > Not sure what you can take away from these numbers, though… :-)
> >
> >
> > 
> >
> > [1] http://eclip.se/6b
> >
> >
> >> Am 18.11.2015 um 17:24 schrieb Eike Stepper :
> >>
> >> This is what I figured for Mars (incl. milestones):
> >>
> >> win32: 9,000,000
> >> macos: 740,000
> >> linux: 800,000
> >>
> >> Cheers
> >> /Eike
> >>
> >> 
> >> http://www.esc-net.de
> >> http://thegordian.blogspot.com
> >> http://twitter.com/eikestepper
> >>
> >>
> >>
> >> Am 18.11.2015 um 15:56 schrieb Denis Roy:
> >>> I do -- and so do you!
> >>>
> >>> https://dev.eclipse.org/committers/committertools/stats.php
> >>>
> >>> Start with a quary against download.eclipse.org and use file pattern:
> >>>
> >>> /technology/epp/%mars
> >>>
> >>> That should get you going.
> >>>
> >>> Denis
> >>>
> >>>
> >>> On 11/18/2015 09:52 AM, Pascal Rapicault wrote:
>  Since there are discussions on improving SWT for specific platforms, I
>  think it would be interesting to see a rough percentage of the
> downloads
>  per platform.
>  Denis, would you have access to this?
> 
>  Thanks,
> 
>  Pascal
> >>> ___
> >>> cross-project-issues-dev mailing list
> >>> cross-project-issues-dev@eclipse.org
> >>> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>>
> >>
> >>
> >> ___
> >> cross-project-issues-dev mailing list
> >> cross-project-issues-dev@eclipse.org
> >> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> > --
> > Codetrails GmbH
> > The knowledge transfer company
> >
> > Robert-Bosch-Str. 7, 64293 Darmstadt
> > Phone: +49-6151-276-7092
> > Mobile: +49-179-131-7721
> > http://www.codetrails.com/
> >
> > Managing Director: Dr. Marcel Bruch
> > Handelsregister: Darmstadt HRB 91940
> >
> > ___
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)

[Markus Knauer]

*** Automatically check for updates:

That's enabled in all packages, and all of them are looking for updates of
their root feature(s) once every week.

*** Package structure:

All Mars packages (with the exception of the RCP/RAP package) are using a
single root feature that is checked for a higher version. This root feature
is an EPP feature and controlled by the package maintainers. In theory it
could be updated and the respective package would be updated with the new
content. Of course, this works only if the update content is available from
one of the p2 repositories built into the packages (which is the
Simultaneous Release p2 repository).

The RCP/RAP package structure has changed with Mars, as an experiment in
order to get some experience and as a way to "convince" others in the Neon
timeframe to change the package structure of the remaining packages. In
this package *all* content features are installed as root features and
therefore checked for updates.

Personally I think that's the way to go for all packages. The fact that it
is enabled in RCP/RAP gives us a chance to get some experience in order to
roll it out for all packages in the Neon timeframe.

Regards,
Markus


On 23 September 2015 at 21:31, Doug Schaefer  wrote:

> Step 1 - test to see whether it works. Anecdotal evidence says it doesn't.
> Something about how the EPP packages are defined and built. Also projects
> need to make sure the URLs for maintenance p2 sites are correct and enabled
> by default.
>
> The Check for Updates including the auto check feature itself works. We've
> used it for years in our commercial product. Just need to make sure
> everything is set up correctly for the packages.
>
> I'm also not sure (and actually doubt) auto check is turned on in all the
> packages so that when users start them up and/or on regular intervals it
> does a check and prompts the user to install the updates.
>
> This has to be the default behavior without the user having to do
> anything. That way the user could have installed Mars.1 and then when they
> start up they would have been prompted to install the update for Buildship
> any other feature that happened to have updates out by then.
>
> We talked about this at the architecture call. Not sure it got captured in
> the minutes there. But this is the general idea.
>
> Doug.
>
>
> 
> From: cross-project-issues-dev-boun...@eclipse.org [
> cross-project-issues-dev-boun...@eclipse.org] on behalf of Pascal
> Rapicault [pas...@rapicorp.com]
> Sent: Wednesday, September 23, 2015 3:18 PM
> To: cross-project-issues-dev@eclipse.org
> Subject: Re: [cross-project-issues-dev] New components in Mars.1 (was Re:
> Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)
>
> I was about to ask the same :)
>
> On 15-09-23 02:54 PM, Mike Milinkovich wrote:
> > On 23/09/2015 1:49 PM, Doug Schaefer wrote:
> >> if we could ever get Check for Updates working properly, this
> >> wouldn't have been such a big issue.
> >
> > Doug (or anyone)
> >
> > Is there a written proposal anywhere on how "Check for Updates" should
> > be modified?
> >
> > Is there an existing consensus around such a proposal?
> >
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)

[Markus Knauer]

As I wrote in my earlier mail: The RCP/RAP package installs *all* features
as root features, all other packages have only a single root feature
defined by EPP. There's no version restriction involved or enforced.


Regards,
Markus

On 23 September 2015 at 22:24, Max Rydahl Andersen <mande...@redhat.com>
wrote:

> I believe EPP in their features can be less restrictive and allow for
> version ranges in what the root feature will allow.
>
> Maybe that is what the RCP EPP package do ?
>
> If yes,then I can tell that is how we for Developer Studio allow updates
> of certain features (like egit and m2e) to avoid having to release the main
> feature all the time.
>
> /max
>
> Ah, that's it. Perfect. Thanks Markus!
>>
>> IMHO, we should make this mandatory for all packages and have someone
>> just go in and do it.
>>
>> Doug.
>>
>> 
>> From: cross-project-issues-dev-boun...@eclipse.org [
>> cross-project-issues-dev-boun...@eclipse.org] on behalf of Markus Knauer
>> [mkna...@eclipsesource.com]
>> Sent: Wednesday, September 23, 2015 3:44 PM
>> To: Cross project issues
>> Subject: Re: [cross-project-issues-dev] New components in Mars.1 (was Re:
>> Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)
>>
>> *** Automatically check for updates:
>>
>> That's enabled in all packages, and all of them are looking for updates
>> of their root feature(s) once every week.
>>
>> *** Package structure:
>>
>> All Mars packages (with the exception of the RCP/RAP package) are using a
>> single root feature that is checked for a higher version. This root feature
>> is an EPP feature and controlled by the package maintainers. In theory it
>> could be updated and the respective package would be updated with the new
>> content. Of course, this works only if the update content is available from
>> one of the p2 repositories built into the packages (which is the
>> Simultaneous Release p2 repository).
>>
>> The RCP/RAP package structure has changed with Mars, as an experiment in
>> order to get some experience and as a way to "convince" others in the Neon
>> timeframe to change the package structure of the remaining packages. In
>> this package *all* content features are installed as root features and
>> therefore checked for updates.
>>
>> Personally I think that's the way to go for all packages. The fact that
>> it is enabled in RCP/RAP gives us a chance to get some experience in order
>> to roll it out for all packages in the Neon timeframe.
>>
>> Regards,
>> Markus
>>
>>
>> On 23 September 2015 at 21:31, Doug Schaefer <dschae...@qnx.com> dschae...@qnx.com>> wrote:
>> Step 1 - test to see whether it works. Anecdotal evidence says it
>> doesn't. Something about how the EPP packages are defined and built. Also
>> projects need to make sure the URLs for maintenance p2 sites are correct
>> and enabled by default.
>>
>> The Check for Updates including the auto check feature itself works.
>> We've used it for years in our commercial product. Just need to make sure
>> everything is set up correctly for the packages.
>>
>> I'm also not sure (and actually doubt) auto check is turned on in all the
>> packages so that when users start them up and/or on regular intervals it
>> does a check and prompts the user to install the updates.
>>
>> This has to be the default behavior without the user having to do
>> anything. That way the user could have installed Mars.1 and then when they
>> start up they would have been prompted to install the update for Buildship
>> any other feature that happened to have updates out by then.
>>
>> We talked about this at the architecture call. Not sure it got captured
>> in the minutes there. But this is the general idea.
>>
>> Doug.
>>
>>
>> 
>> From: cross-project-issues-dev-boun...@eclipse.org> cross-project-issues-dev-boun...@eclipse.org> [
>> cross-project-issues-dev-boun...@eclipse.org> cross-project-issues-dev-boun...@eclipse.org>] on behalf of Pascal
>> Rapicault [pas...@rapicorp.com<mailto:pas...@rapicorp.com>]
>> Sent: Wednesday, September 23, 2015 3:18 PM
>> To: cross-project-issues-dev@eclipse.org> cross-project-issues-dev@eclipse.org>
>> Subject: Re: [cross-project-issues-dev] New components in Mars.1 (was Re:
>> Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)
>>
>> I was about to ask the same :)
>>
>> On 15-09-23 02:54 PM, Mike Milinkovich wrote:
&g

[cross-project-issues-dev] Mars.1 RC3 available

[Markus Knauer]

Hi everyone,

like last Friday the Mars.1 RC3 EPP packages are available from the
developer tab of the download page at [1]. Not all package maintainers had
the time to test and to vote for the packages yet, so there are some
packages missing but will be made available once we get a +1 vote for them.

Upgrades and updates can be tested with the p2 repositories [2] and [3].
But please keep in mind that the maintenance p2 repository is not stable
and will be updated soon.

These will be the last 'RC' packages that will be made available from the
developer tab; the RC4 next week will stay hidden because it is the final
release (unless there are emergency rebuilds).

Thanks to everyone testing and improving Mars.1!

Regards,
Markus



[1] https://www.eclipse.org/downloads/index-developer.php?release=mars
[2] http://download.eclipse.org/releases/maintenance/
[3] http://download.eclipse.org/technology/epp/packages/mars/SR1-RC3/
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] unable to connect to build.eclipse.org via http

[Markus Knauer]

It has been fixed for *everyone* in the meantime.
Thanks to the webmasters!

Regards,
Markus

On 9 September 2015 at 09:49, Lars Vogel <lars.vo...@vogella.com> wrote:

> Seems fixed, website reports now: It's just you. http://build.eclipse.org
> is up.
>
> On Wed, Sep 9, 2015 at 9:29 AM, Daniel Megert <daniel_meg...@ch.ibm.com>
> wrote:
> > It's not just you, see
> > http://www.downforeveryoneorjustme.com/http://build.eclipse.org/
> >
> > Dani
> >
> >
> >
> > From:Markus Knauer <mkna...@eclipsesource.com>
> > To:Eclipse Cross Project Issues
> > <cross-project-issues-dev@eclipse.org>
> > Date:09.09.2015 09:14
> > Subject:[cross-project-issues-dev] unable to connect to
> > build.eclipse.orgvia http
> > Sent by:cross-project-issues-dev-boun...@eclipse.org
> > 
> >
> >
> >
> > Hi everyone,
> >
> > anyone else having problems to connect to build.eclipse.org via http?
> >
> >   Bug 476936 - Can't connect to build.eclipse.org via http
> >   https://bugs.eclipse.org/bugs/show_bug.cgi?id=476936
> >
> > At the moment this prevents me from building our RAP Mars.1 RC3
> > contribution. If it cannot be fixed within the next two hours I'll try to
> > workaround this issue.
> >
> > Thanks,
> > Markus___
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > To change your delivery options, retrieve your password, or unsubscribe
> from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> > ___
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > To change your delivery options, retrieve your password, or unsubscribe
> from
> > this list, visit
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (032) 221739404, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] unable to connect to build.eclipse.org via http

[Markus Knauer]

Hi everyone,

anyone else having problems to connect to build.eclipse.org via http?

  *Bug 476936*  - Can't
connect to build.eclipse.org via http
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=476936

At the moment this prevents me from building our RAP Mars.1 RC3
contribution. If it cannot be fixed within the next two hours I'll try to
workaround this issue.

Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] unable to connect to build.eclipse.org via http

[Markus Knauer]

Our RC3 is on its way... build is ready, and now I'm just waiting for the
verification before pushing the following Gerrit change
https://git.eclipse.org/r/55520 to the Simultaneous Release repository.

Regards,
Markus


On 9 September 2015 at 09:55, Stephan Leicht Vogt <
stephan.leichtv...@bsi-software.com> wrote:

> Hi Markus
>
> How long till RAP Mars.1 RC3 is ready for us?
>
> Thanks and greetings
> Stephan
>
>
>
> --
>
> Scout Release Engineer, Senior Software Architect
>
> BSI Business Systems Integration AG
>
> Täfernstrasse 16a, CH-5405 Baden
>
> T +41 56 484 19 47
>
> M + 41 78 728 25 05
>
> www.bsi-software.com
>
>
>
> *Neue Adresse ab 1.12.2015:* Täfernweg 1, CH-5405 Baden
>
> On 9 Sep 2015, at 9:52, Markus Knauer wrote:
>
> It has been fixed for *everyone* in the meantime.
> Thanks to the webmasters!
>
> Regards,
> Markus
>
> On 9 September 2015 at 09:49, Lars Vogel lars.vo...@vogella.com wrote:
>
> Seems fixed, website reports now: It's just you. http://build.eclipse.org
> is up.
>
> On Wed, Sep 9, 2015 at 9:29 AM, Daniel Megert <daniel_meg...@ch.ibm.com>
> wrote:
>
> It's not just you, see
> http://www.downforeveryoneorjustme.com/http://build.eclipse.org/
>
> Dani
>
> From: Markus Knauer mkna...@eclipsesource.com
> To: Eclipse Cross Project Issues
> cross-project-issues-dev@eclipse.org
> Date: 09.09.2015 09:14
> Subject: [cross-project-issues-dev] unable to connect to
> build.eclipse.org via http
> Sent by: cross-project-issues-dev-boun...@eclipse.org
> --
>
> Hi everyone,
>
> anyone else having problems to connect to build.eclipse.org via http?
>
> Bug 476936 - Can't connect to build.eclipse.org via http
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=476936
>
> At the moment this prevents me from building our RAP Mars.1 RC3
> contribution. If it cannot be fixed within the next two hours I'll try to
> workaround this issue.
>
> Thanks,
> Markus___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
>
> from
>
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> --
>
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
>
> from
>
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (032) 221739404, Email: lars.vo...@vogella.com, Web:
> http://www.vogella.com
> --
>
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> --
>
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Mars.1 RC2 available

[Markus Knauer]

Hi everyone,

the Mars.1 RC2 EPP packages are available from the developer builds tab on
the download page at  [1]. Packages that didn't receive their +1 vote yet
aren't listed but I'm positive that we can list them soon.

At the same time the p2 repository with the Mars.1 RC2 content is available
at /releases/maintenance [2]. Please keep in mind that this isn't a stable
repository and its content will change immediately when we start to build
for RC3.

Thanks and enjoy your weekends,

Markus


[1] https://www.eclipse.org/downloads/index-developer.php?release=mars
[2] http://download.eclipse.org/releases/maintenance/
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] RAP 3.1.0 in Neon

[Markus Knauer]

Hi everyone,

in the RAP project we plan to contribute RAP 3.1.0 [1] to the Neon release
next year. Offset is +2 as it used to be in the older Simultaneous Releases.

Thanks,
Markus

[1] https://projects.eclipse.org/projects/rt.rap/releases/3.1.0
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Simrel gerrit verification failure

[Markus Knauer]

My guess is that it is caused by commit
4274eeb8a61dfaa77920bb87ca3ec9e89a00a322 from the Subversive team. I think
they changed something without using the b3 tooling which leads to the
following error when I validate the files locally:

The opposite features 'categories' of 'Feature :
org.eclipse.team.svn.revision.graph / [3.0.0,4.0.0) (Subversive Revision
Graph (Optional))' and 'features' of 'Custom Category : Collaboration' do
not refer to each othersimrel.b3aggr/org.eclipse.simrel.build
UnknownAggregator

Now lets see if we can fix this.

Regards,
Markus

On 19 August 2015 at 15:21, Bernd Hufmann bernd.hufm...@ericsson.com
wrote:

 Hello

 I've submitted a change to the Trace Compass b3aggrcon to Gerrit in order
 to include Trace Compass in Neon M1 but the Gerrit verification build
 failed [1]. I'm not sure what's the reason for this. Could someone have a
 look?

 Thanks
 Bernd

 [1] https://git.eclipse.org/r/#/c/54093/
 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Buildship in SR1

[Markus Knauer]

Yep, that's the plan if I may answer this question.

Regards,
Markus

On 24 July 2015 at 18:43, Pascal Rapicault pas...@rapicorp.com wrote:

 Hey,

 IIRC back in April / May, it was decided that Buildship (Gradle
 integration in Eclipse) would be added to Mars SR1.
 Is this still the plan?

 Pascal
 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Bad permissions on download files

[Markus Knauer]

Thanks for noticing... the first ones /rt/rap/* are fixed but I'm still
wondering how that could happen. Probably a wrong umask during script
execution.

Thanks,
Markus

On 15 June 2015 at 22:50, Denis Roy denis@eclipse.org wrote:

 Just a quick reminder to please make sure the world can read files you put
 on download.eclipse.org.  It is not acceptable to hide files by
 blocking permissions, as these cause errors on our mirrors.

 /rt/rap/3.0/R-20150602-0950/addDownloadStats.xsl (in eclipseMirror):
 Permission denied (13)
 /rt/rap/3.0/R-20150602-0950/artifacts.xml.xz (in eclipseMirror):
 Permission denied (13)
 /rt/rap/3.0/R-20150602-0950/p2.index (in eclipseMirror): Permission
 denied (13)
 /rt/rap/3.0/RC4-20150602-0950/addDownloadStats.xsl (in eclipseMirror):
 Permission denied (13)
 /rt/rap/tools/3.0/R-20150609-1348/addDownloadStats.xsl (in
 eclipseMirror): Permission denied (13)
 /rt/rap/tools/3.0/R-20150609-1348/artifacts.xml.xz (in eclipseMirror):
 Permission denied (13)
 /rt/rap/tools/3.0/R-20150609-1348/p2.index (in eclipseMirror):
 Permission denied (13)
 /rt/rap/tools/3.0/RC4-20150609-1348/addDownloadStats.xsl (in
 eclipseMirror): Permission denied (13)
 /sirius/updates/legacy/1.1.0_signingTest/org.eclipse.sirius.legacy.update.zip
 (in eclipseMirror): Permission denied (13)


 Thanks
 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] [epp-dev] [ide-dev] Phasing in Error Reporting for Mars (was: Start collecting requests for Error Reporting v2)

[Markus Knauer]

Hi Marcel,

the good news is... with Luna such a change could not have been rolled out,
with Mars I am very positive that we could do this. Although this is a
possibility I don't like the idea a lot because a lot of work and risk is
involved.

But now back to my thoughts:

- All Mars packages are configured in a way that they are looking for
updates once a week; this makes it possible for the first time to roll out
such a change but even in that case it is kind of a 'pull' by the user who
needs to confirm a dialog here and there... it's not a push mechanism where
we can trigger an update. And it is 'once a week' (starting Tuesdays) which
could be too late?

- A change of the default preferences in packages is possible because all
packages have a plugin_customization.ini of their own.

- As a reminder... from my perspective, but I don't know about all other
projects, we have at least three bandwidth related risk factors in Mars,
one of them is the error reporter, the other two are the aforementioned
check-for-update and of course, the Oomph installer which both rely on p2
and the download server.


Marcel, if you want we can talk about options. If required I'll try to be
available.

Thanks,
Markus (Knauer) ;-)



On 13 June 2015 at 08:58, Marcel Bruch marcel.br...@codetrails.com wrote:

 — Adding epp-dev to this discussion b/c the proposals below affect EPP
 packages —

 The amount of traffic is something no one can estimate yet. I think
 everyone feels a little bit uncomfortable with this situation. So here is a
 proposal I’d like to discuss publicly (although only a small subset of
 people may feel need to discuss this).


 Markus (Knauer),
 in case we’d need to disable error reporting because of too much traffic:
 is it possible for you to simply rebuild the packages with an additional
 preference? This preference would preconfigure the system to “don’t send
 error reports.

 How quickly could we do that - in worst case?


 Denis,
 since JEE is the largest error reports provider, I can imagine to disable
 the error reporter for this package in the beginning. Disabling would mean
 that the user would have to go to the preferences page and enable it
 explicitly by changing a value in some combo box.


 Three options I’d feel comfortable with:

 1. The milquetoast option: Disable error reporting for JEE in the first
 days (via preferences as outlined above). If no outages occur, we can
 rebuild the JEE package and reenable it. We could also do the same for the
 Java package. With that we could slowly phase-in and see whether we can
 handle the traffic.

 2. The daredevil option: Deactivate it in new EPP downloads as soon as we
 see that there is too much traffic. But then the sending clients are
 already out there...

 3. I forgot option three. But I had one before I went to breakfast… Ah,
 here it is: The BOFH option: Use the firewall to block every, say, second
 access to the HTTP HEAD requests to the remote problems database. With
 that, create a controlled phasing in by selectively disabling half of the
 clients (randomly). Instead of blocking every second request, we may
 disable it for some hours of the days. Since this will disable the error
 reporter until restart we may temporarily disable the clients completely on
 the server-side w/o changing any EPP package.

 What do you think?


  It appears to me that you didn't just write code; you've engineered a
 solution.

 Credits for this go to all people involved in various discussions over the
 past milestones and their feature requests. See bug 457115 [1] as one great
 example - but there are many more.



 Denis, BTW:
 can we get more bandwidth for dev.eclipse.org/recommenders? :-)


 Marcel


 [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=457115

  On 12 Jun 2015, at 20:26, Denis Roy denis@eclipse.org wrote:
 
  It appears to me that you didn't just write code; you've engineered a
 solution.
 
  No need for crossed fingers.  I think we're in good shape.  Beer will be
 on me at EclipseCon.
 
  Have a nice weekend.
 
  Denis
 
 
 
  On 12/06/15 02:21 PM, Marcel Bruch wrote:
  Denis,
 
  there are four (4) + one (1) mechanisms in place that will / can limit
 the traffic to dev.eclipse.org/recommenders:
 
  Level 1: A local, persistent, per-workspace history that remembers what
 was send before. If an error is logged that has the same fingerprint as an
 already sent report, it is skipped. This should prevent clients to send the
 same error over and over again.
 
  Level 2: A “known errors database” that get’s downloaded from
 eclipse.org on IDE startup. If an error is logged in the IDE which was
 marked as “ignored” in the known-errors database, it won’t be send. No
 network traffic will happen. The server-side generates this database on
 demand and set’s every problem to ignore that was reported by more than 50
 users.
 
  Level 3: The “emergency” power OFF switch [1]. On startup, we check
 whether a certain system status URL is reachable

Re: [cross-project-issues-dev] WIndowBuilder

[Markus Knauer]

I'd say we are past the deadline, and the aggregation build is disabled
right now.
If this is a stop-ship bug it needs to be discussed with your PMC how we
proceed from here.

Regards,
Markus

On 11 June 2015 at 13:02, Mark R Russell mrruss...@google.com wrote:

 We did find an issue and we have a fix.  I need to get the code signed and
 in the aggregation.  I'll let you know when it is done.

 On Wed, Jun 10, 2015 at 5:04 PM Mark R Russell mrruss...@google.com
 wrote:

 Good news is we are back on the train. I was able to get a machine in
 Google to build the code and get it back in the aggregation build. :-)
 However one of the testers may have found an issue that may require us to
 do a respin.  I'll keep you posted.


 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Gerrit for org.simrel.build keeps asking me to rebase my change

[Markus Knauer]

At the moment there seem to be two competing changes in Gerrit:

[1] https://git.eclipse.org/r/#/c/49960/1
[2] https://git.eclipse.org/r/#/c/49957/4

Both of them have the same parent commit, but only [2] has a change ID that
allows Gerrit to assign updated patch sets to the same change. Maybe this
causes some trouble, too, at least it does not help. I'd suggest to abandon
[1].

Regards,
Markus


On 10 June 2015 at 21:36, Eike Stepper step...@esc-net.de wrote:

 Am 10.06.2015 um 21:30 schrieb Jeff Johnston:

 Hello,

 I'm trying to get the RC4 change in for Linux Tools.  I keep getting a
 successful
 build, then after I review it, it says I have to rebase my change.  I do
 so, it rebuilds
 successfully and then claims I need to rebase it again.  I am only
 changing the
 linuxtools.b3aggrcon file.

 Is anyone else experiencing this issue?

 One night I had the same problem. I worked around it by rebasing and
 setting it to verified +1 myself. Then I could immediately submit it.

 Cheers
 /Eike

 
 http://www.esc-net.de
 http://thegordian.blogspot.com
 http://twitter.com/eikestepper




 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Heads up: Platform will be coming in hot with M6 changes for Mac App layout

[Markus Knauer]

Yes, this certainly affects the EPP packages and I welcome this change!

EPP is using Tycho 0.23.0-SNAPSHOT for quite a while in the Mars builds, so
no change required on that part. We'll see if we need to do something in
other areas, but my current understanding is that it will be more or less
transparent to the build that we are running in EPP. As soon as first
results are available from the Simultaneous Release repository, we'll try,
test, and see if this is true, but I'm very optimistic.

Regards,
Markus



On 11 March 2015 at 08:48, Christian Campo christian.ca...@compeople.de
wrote:

  And that also effects all EPP packages which are also built in the new
 „Mac App layout in their Mac edition ?

   Von: David com david_willi...@us.ibm.com
 Antworten an: Cross issues cross-project-issues-dev@eclipse.org
 Datum: Mittwoch, 11. März 2015 16:15
 An: Cross issues cross-project-issues-dev@eclipse.org
 Cc: General development mailing list of the Eclipse project. 
 eclipse-...@eclipse.org
 Betreff: [cross-project-issues-dev] Heads up: Platform will be coming in
 hot with M6 changes for Mac App layout

  Extended team,

 I wanted to make everyone aware of our latest Platform plans for M6 ...
 especially since it has the potential to effect downstream consumers and
 contributions to Mars Sim. Release.  If anyone sees any blocking aspects
 to this plan, let us know.

 In short, we will aggressively be trying to get changes needed to build
 our Mac Product in a relatively standard Mac App layout. See

 *Bug 431116* https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116 -
 Releases for Mac OS X should be bundled as a proper Mac App and/or
 Library

 We felt it important to make the move by M6, to be sure problems/issues
 can be found, and fixed, by M7 ... otherwise, we face a greater risk making
 changes during RCs, or, worse, not having it well tested by anyone or no
 time to make important fixes.

 Some issues are listed below ... may be others?

 - To do this, we will soon have to move to Tycho 0.23.0-SNAPSHOT.
 -- always risky to do a milestone with a SNAPSHOT, but ... we think
 worth it in this case. (And we'll ask Tycho team to be extra careful :)
 -- so far, we can not quite get our production build to work with it ...
 but, suspect we can soon.
 -- For an experimental build, see
 http://download.eclipse.org/eclipse/downloads/drops4/X20150309-0218/
 --- (This was produced with a locally built patched Tycho, and so far
 haven't quite got the official SNAPSHOT to work consistently ... but
 works sometimes, and issues appear unrelated to the Mac layout)

 - The change is all or nothing ... once we (and Tycho) move to this new
 layout, the old layout will no longer be possible.

 * This should only effect consumers who create their own products ...
 should not effect features or plugins in any way.
 * Should not effect Linux or Windows products in any way.
 * But, anyone who does produce products, for the Mac, will also have to
 use Tycho 0.23.0-SNAPSHOT for Sim. Release.
 * Effect on PDE Builds and Buckminster builds is sort of unknown (by
 us) ... ?

 We have set our own deadline of Sunday March 15 to have everything
 working ... and, if not by then ... *might* have to back peddle, or come
 up with some other plan.

 Just wanted to give a little early warning of this change coming. I think
 for the most part, everyone will welcome the change, but may be some rough
 spots ahead.

 Please comment in *Bug 431116*
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=431116if you see issues,
 or open new bugs, having them 'block' that bug.

 Thanks,


  -
 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@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Update site time outs

[Markus Knauer]

Maybe we should take some time next week to sit in front of a computer and
try to find out more during EclipseCon...

Regards,
Markus

On 6 March 2015 at 16:03, Denis Roy denis@eclipse.org wrote:

  Ed,

 I'm on holidays this week but I can look into it next week. In terms of
 server logs, yeah, there's 22 million entries each day.  Finding patterns
 is a lot of work, especially when it's not clear what I should be looking
 for. I remember asking what an automatic update would look like and I was
 given a list of about 15 files. :)

 There are probably other issues at play:
 - more projects creating Maven-esque repos which cannot leverage our
 mirrors
 - new projects may not be using the mirrors

 Denis


 On 03/06/2015 12:51 AM, Ed Merks wrote:

 Denis,

 I'm not sure I saw a response to Markus' question:

  Is there any pattern visible in the server logs? Some examples I'd be
 interested in...

 - since when does it happen, does it happen since Luna SR2?
  - is it caused by some specific p2 repositories, i.e. the ones in
 /releases/luna? or a project that release recently?
  - is it related to bug 421779 (enable automated updates in Mars)?


 It would be good to know what access pattern caused several days of the
 server being maxed out so we might take steps to avoid it in the future...

 Regards,
 Ed

 On 05/03/2015 1:58 PM, Denis Roy wrote:

 Ed,

 I agree with your assessment below.  I've opened a number of bugs against
 p2 over the years but there appear to be few resources to help address the
 issues (this is not a complaint, just an observation).

 Indeed, p2 is very chatty with download.eclipse.org and I don't think
 it needs to be.

 Denis





 On 05/03/15 02:53 AM, Ed Merks wrote:

 Camille,

 The download server has been maxed out all week with HTTP connections at
 between 9,000 to 12,000 for download1, which I assume is the primary server
 for http:/download.eclipse.org:

 https://dev.eclipse.org/committers/help/status.php

 Things like
 http://download.eclipse.org/releases/luna/201501121000/content.jar were
 taking often more than 4 minutes to download.

 Today it's finally at a more reasonable level at less than 3,000 when I
 used it early in the morning in Europe and I am able to work effectively
 again.

 Some of these problems seem to be to be fundamentally p2 problems.  Eike
 and I looked very closely at the underlying infrastructure as part of the
 Oomph work and even added offline support for Oomph as a layer on top, but
 p2 itself has a habit of downloading content and artifact files (not to
 mention the artifacts themselves when not using bundle pool) over and over
 again.   Also p2 tries many combinations for different potential update
 site configurations many of which yield 404.  In the end, it's very
 annoying to wait for the same things to download again and again and when
 large numbers of users are all doing that at the same time, failing, and
 trying again, it becomes a serious server problem.

 Regards,
 Ed


 On 04/03/2015 4:33 PM, LETAVERNIER Camille wrote:

  Hi,


 We’ve received several notifications [1] from users who encounter a lot of
 “Read time out” when they are trying to install/update some components from
 the simrel (/releases/luna) update site. It seems that it is a general
 issue (not specific to Papyrus). The same thing happens on the mars simrel
 update site (/releases/mars)



 Are there some known server/performances issues? Maybe related to the
 recent SR2 release? Did anyone else run into these issues?



 [1] https://www.eclipse.org/forums/index.php/t/1025771/



 Camille



 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Update site time outs

[Markus Knauer]

Is there any pattern visible in the server logs? Some examples I'd be
interested in...

- since when does it happen, does it happen since Luna SR2?
- is it caused by some specific p2 repositories, i.e. the ones in
/releases/luna? or a project that release recently?
- is it related to bug 421779 (enable automated updates in Mars)?

Regards,
Markus

On 5 March 2015 at 13:58, Denis Roy denis@eclipse.org wrote:

  Ed,

 I agree with your assessment below.  I've opened a number of bugs against
 p2 over the years but there appear to be few resources to help address the
 issues (this is not a complaint, just an observation).

 Indeed, p2 is very chatty with download.eclipse.org and I don't think
 it needs to be.

 Denis






 On 05/03/15 02:53 AM, Ed Merks wrote:

 Camille,

 The download server has been maxed out all week with HTTP connections at
 between 9,000 to 12,000 for download1, which I assume is the primary server
 for http:/download.eclipse.org:

 https://dev.eclipse.org/committers/help/status.php

 Things like
 http://download.eclipse.org/releases/luna/201501121000/content.jar were
 taking often more than 4 minutes to download.

 Today it's finally at a more reasonable level at less than 3,000 when I
 used it early in the morning in Europe and I am able to work effectively
 again.

 Some of these problems seem to be to be fundamentally p2 problems.  Eike
 and I looked very closely at the underlying infrastructure as part of the
 Oomph work and even added offline support for Oomph as a layer on top, but
 p2 itself has a habit of downloading content and artifact files (not to
 mention the artifacts themselves when not using bundle pool) over and over
 again.   Also p2 tries many combinations for different potential update
 site configurations many of which yield 404.  In the end, it's very
 annoying to wait for the same things to download again and again and when
 large numbers of users are all doing that at the same time, failing, and
 trying again, it becomes a serious server problem.

 Regards,
 Ed


 On 04/03/2015 4:33 PM, LETAVERNIER Camille wrote:

  Hi,


 We’ve received several notifications [1] from users who encounter a lot of
 “Read time out” when they are trying to install/update some components from
 the simrel (/releases/luna) update site. It seems that it is a general
 issue (not specific to Papyrus). The same thing happens on the mars simrel
 update site (/releases/mars)



 Are there some known server/performances issues? Maybe related to the
 recent SR2 release? Did anyone else run into these issues?



 [1] https://www.eclipse.org/forums/index.php/t/1025771/



 Camille


 ___
 cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, 
 visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




 ___
 cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, 
 visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Mylyn contribution to Luna SR2

[Markus Knauer]

Hi Sam,

do you have an overview if (and which) other projects depend on this
delivery?
Would they need to take any action (rebuild, testing, etc.)? What's the
risk involved and what's the consequence of not updating to the latest
version?

Personally I think it's not yet too late...

Regards,
Markus

On 18 February 2015 at 08:02, Sam Davis sam.da...@tasktop.com wrote:

 Hi,

 We are currently contributing Mylyn 3.14.1 (already released) to Luna SR2,
 but it happens that we are building a Mylyn 3.14.2 SR on Wednesday morning.
 Would it cause any problems if I update our SR2 contribution to 3.14.2?

 Thanks,
 Sam

 --
 Sam Davis
 Software Engineer, Tasktop Dev
 Committer, Eclipse Mylyn
 http://tasktop.com

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Luna SR2 RC3 staging (maintenance) repository and EPP packages are complete

[Markus Knauer]

Hi Developers,

another week, another release. Luna SR2 RC3 is now available for testing
from the maintenance p2 repository.

The EPP packages are available from the 'Developer Builds' tab on the
download page. Packages are listed as soon as they receive their mandatory
+1 from their package maintainer, most of them are already available:

  https://www.eclipse.org/downloads/index-developer.php?release=luna

Very important are update tests from earlier Luna releases (R, SR1, SR1a).
For those tests you'll need to add the following two p2 repository URLs to
your Eclipse:

  http://download.eclipse.org/releases/maintenance/
  http://download.eclipse.org/technology/epp/packages/luna/SR2-RC3/

/releases/maintenance with the Luna SR2 RC3 content will stay as is for
testing until Monday.

Next week we are going to build RC4 which is the last build for Luna SR2
and will be released after 'Quiet Week' on Friday 27th.

Thanks for testing!

Regards,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Luna SR2 RC2 *and* Mars M5 is complete

[Markus Knauer]

Hi Developers,

after a really, really busy week we've got two new releases ready. Thanks
to everyone who helped to make that happen.


First of all: *Luna*.
Luna SR2 RC2 is available for download as a package from the developer
build tab on the download page:

  https://www.eclipse.org/downloads/index-developer.php?release=luna

Please do not forget to test various updates and upgrades from older Luna
versions. For that reason the maintenance repo will remain constant for a
few days. These tests require the following two additional p2 repositories:

  http://download.eclipse.org/releases/maintenance/
  http://download.eclipse.org/technology/epp/packages/luna/SR2-RC2/



And then there's *Mars*:
The Mars M5 p2 repository is ready at

  http://download.eclipse.org/releases/mars/

and the packages are available from

  https://www.eclipse.org/downloads/index-developer.php?release=mars

(as soon as the package maintainer gave their +1)

I'd like to draw your attention to some important changes in the
packages... please use the bugs to report comments or give feedback:

Bug 457180 https://bugs.eclipse.org/bugs/show_bug.cgi?id=457180 - Add
Automated Error Reporting to all EPP packages
Bug 455645 https://bugs.eclipse.org/bugs/show_bug.cgi?id=455645 - Integrate
Oomph into all EPP packages
Bug 421779 https://bugs.eclipse.org/bugs/show_bug.cgi?id=421779 -
Automatically
find new updates and notify me should be enabled in EPP packages
Bug 332989 https://bugs.eclipse.org/bugs/show_bug.cgi?id=332989 - Allow
parts of a package to upgraded or removed (as a test for the RCP/RAP
package only!)


Thanks to all who have helped produce this milestone and RC, and thanks to
everyone who tests it.

Regards,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Ready for M5?

[Markus Knauer]

scout-rap I think was a recent disable ... perhaps getting ready to
re-submit?

I had to temporarily disable their contribution when I updated our RAP
contributions. That's 'business as usual' and they are informed. I'm sure
they will enable their configuration as soon as their bits are ready.

Regards, Markus
On 3 Feb 2015 19:47, David M Williams david_willi...@us.ibm.com wrote:

 There are still a number of components or features disabled for M5.

 birt.b3aggrcon - org.eclipse.simrel.build
 mat.b3aggrcon - org.eclipse.simrel.build
 mft.b3aggrcon - org.eclipse.simrel.build (2 matches)
 scout-rap.b3aggrcon - org.eclipse.simrel.build

 The BIRT (and MAT) issue is documented in bug *458296*
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=458296 .

 mft has a few disabled features, which I think have been disabled for
 along time. Should they be removed?

 scout-rap I think was a recent disable ... perhaps getting ready to
 re-submit?

 Please post status and outlook, if you are responsible for any of these
 components.

 Thanks,

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Joint NN page for the release train

[Markus Knauer]

Sounds interesting...

Right now we are maintaining a list of NN links for every package, but (a)
these are not very popular... and (b) they are most of the time out of date
because I tend to review these for the release only, i.e. I don't have the
time to update them regularly for every milestone.

Regards,
Markus




On 2 February 2015 at 11:14, Lars Vogel lars.vo...@vogella.com wrote:

 Hi Marcel,

 I think the correct solution would be to extend the purpose of the
 Platform NN to include newsitems from the EPP side.

 Best regards, Lars

 On Mon, Feb 2, 2015 at 11:11 AM, Marcel Bruch marcel.br...@codetrails.com
  wrote:

 Greetings cross-projects,

 I’d like to get your thoughts about a joint NN page for Mars Milestones.

 The platform maintains a NN page [1] for changes on the
 Platform/JDT/PDE. All press releases, blogs and tweets about new milestones
 are pointing to this page and as such it is the most prominent place to
 present new features, what’s new and upcoming in Eclipse.

 However, IMHO there are much more noteworthy things to talk about. For
 instance, the addition of the automated error reporting in all EPP packages
 is such a noteworthy item but it cannot be published on that page because
 it does not belong to the SDK. I guess many projects have interesting NN
 as well. While larger projects with a community/ popular webpage will
 certainly write a blog post about their new features. Smaller ones with no
 prominent website or large community lack such a space. In addition,
 bloggers etc. will certainly not browse all project blogs to find all NNs.

 Thus I wonder whether we should have a joint NN page for the whole
 release train where every participating project could put, say, up to 3
 items per Milestone release with a picture and a short paragraph (as the
 SDK already does).

 What do others think?


 Marcel



 P.S.: FWIW, every EPP package download page *has* a NN link in the side
 menu where EPP packages can add their NN links. However, it’s not used
 much and likely is not very popular (at least I assume that b/c I noticed
 it the very first time today).

 [1] https://www.eclipse.org/eclipse/news/4.5/M5/


 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




 --
 Geschäftsführer

 vogella GmbH

 Haindaalwisch 17a, 22395 Hamburg
 Amtsgericht Hamburg: HRB 127058
 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
 USt-IdNr.: DE284122352
 Fax (032) 221739404, Email: lars.vo...@vogella.com, Web:
 http://www.vogella.com

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson fails to access http://download.eclipse.org/eclipse/updates/4.4-M-builds

[Markus Knauer]

EPP build cannot access Git:

  https://hudson.eclipse.org/packaging/job/mars.epp-tycho-build/130/console

Same problem with RAP HIPP instance:

  https://hudson.eclipse.org/rap/job/rap-head-runtime/569/console

Another issue that I see is that I don't receive any mails from Gerrit any
more.

Thanks,
Markus


On 1 February 2015 at 13:05, Denis Roy denis@eclipse.org wrote:

 Can you point me to a job so I can test this?


 Ed Willink e...@willink.me.uk wrote:

 Hi

 Same for my HIPP.

 [0]Communication with repository at http://download.eclipse.org/releases/luna 
 failed.
 Caused by: [0]java.net.SocketTimeoutException: connect timed out
 [0]Problems loading repositories
 [0.2]Communication with repository at 
 http://download.eclipse.org/releases/luna failed.
 Caused by: [0.2]java.net.SocketTimeoutException: connect timed out

 Any news?

 Regards

 Ed Willink

 On 31/01/2015 18:33, Doug Schaefer wrote:

  No, I think they're all broken. One I was using can't see the git repos.

  Sent from my BlackBerry 10 smartphone on the Rogers network.
*From: *Marcel Bruch
 *Sent: *Saturday, January 31, 2015 1:28 PM
 *To: *Cross project issues
 *Reply To: *Cross project issues
 *Subject: *[cross-project-issues-dev] Hudson fails to access
 http://download.eclipse.org/eclipse/updates/4.4-M-builds

  Our HIPP builds got stuck on accessing the p2 update site from 
 download.eclipse.org. I restarted our jobs two times with the same effect. 
 Running the very same build from my pc, however, does not seem to suffer from 
 an unavailability of download.eclipse.org. Does anyone else see this issue as 
 well? If someone knows a workaround, I’d be happy hear…

 Marcel

 [INFO] Computing target platform for MavenProject: 
 org.eclipse.recommenders:org.eclipse.recommenders.apidocs:2.1.12-SNAPSHOT @ 
 /jobs/genie.technology.recommenders/gerrit.master.luna/workspace/plugins/org.eclipse.recommenders.apidocs/pom.xml

 [INFO] Adding repository 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds

 [WARNING] Failed to access p2 repository 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds, use local cache. 
 Unable to read repository at 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds/compositeContent.xml.

 [WARNING] Failed to access p2 repository 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds/categoriesLuna, use 
 local cache. Unable to read repository at 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds/categoriesLuna/content.xml.

 [WARNING] Failed to access p2 repository 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds/M20140925-0400, use 
 local cache. Unable to read repository at 
 http://download.eclipse.org/eclipse/updates/4.4-M-builds/M20140925-0400/content.xml.




 ___
 cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe from 
 this list, 
 visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



 No virus found in this message.
 Checked by AVG - www.avg.com
 Version: 2015.0.5646 / Virus Database: 4273/9029 - Release Date: 01/31/15



 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Hudson fails to access http://download.eclipse.org/eclipse/updates/4.4-M-builds

[Markus Knauer]

Thanks, Matt, all my builds seem to work again.

Regards,
Markus

On 1 February 2015 at 14:16, Matthew Ward(Bt. Kt. SSA.) 
matt.w...@eclipse.org wrote:

 It looks like our ssh attack protection blocked part of our internal
 network because of some bad longterm stats.  I've cleared the block, and
 the data behind it, and now EPP is building again.

 -Matt.


 On 02/01/2015 07:25 AM, Markus Knauer wrote:

 EPP build cannot access Git:

 https://hudson.eclipse.org/packaging/job/mars.epp-tycho-build/130/console

 Same problem with RAP HIPP instance:

 https://hudson.eclipse.org/rap/job/rap-head-runtime/569/console

 Another issue that I see is that I don't receive any mails from Gerrit
 any more.

 Thanks,
 Markus



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Patch updates, reboot

[Markus Knauer]

On 28 January 2015 at 07:38, Eike Stepper step...@esc-net.de wrote:


 estepper@build:~ ll /home/data/httpd/download.eclipse.org/
 total 0


Very true... NFS mounts seem to be missing.

Regards,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Patch updates, reboot

[Markus Knauer]

Morning Eike,

http://download.eclipse.org/technology/epp/packages/luna/content.jar works
from my computer as does the download URL in your mail. Maybe it is working
now again?

Regards,
Markus


On 28 January 2015 at 06:40, Eike Stepper step...@esc-net.de wrote:

 Hi Denis,

 Maybe you're still working on some issues but just to be sure that you're
 aware: download.eclipse.org seems not available. The following URL just
 shows cant't open file: https://www.eclipse.org/
 downloads/download.php?file=/eclipse/downloads/drops4/S-4.
 5M4-201412102000/eclipse-SDK-4.5M4-win32-x86_64.zipmirror_id=1

 All my cron jobs still fail and the mount point is empty:

 estepper@build:/home/data/httpd/download.eclipse.org ls
 estepper@build:/home/data/httpd/download.eclipse.org

 Good luck and

 Cheers
 /Eike

 
 http://www.esc-net.de
 http://thegordian.blogspot.com
 http://twitter.com/eikestepper



 Am 28.01.2015 um 04:37 schrieb Denis Roy:

 On 27/01/15 10:12 PM, Denis Roy wrote:

 build.eclipse.org is proving to be problematic. At this time, all
 signing services as well as Proxy access to the Internet is not working.


 Good news -- build.eclipse.org is back online, as is signing and proxy
 services.  At this time, everything should be restored.

 Denis


 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Luna SR2 RC1 warm-up is complete

[Markus Knauer]

Hi Developers,

our Luna SR2 RC1 warm-up is complete.

The staging repo will remain constant for a few days if anyone wants to do
some testing. For upgrade tests with EPP packages you'll additionally need
the second repository which includes the package information:

  http://download.eclipse.org/releases/maintenance/
  http://download.eclipse.org/technology/epp/packages/luna/SR2-RC1/

The EPP packages won't be put in the usual developer downloads area,
since this was the warm-up RC, but for anyone who wants to test or check
anything, they are available from the Hudson build:

  https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/238/

With RC2 only two weeks away, it's better to start testing early. RC2 will
be a full release candidate.

Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] RAP 3.x for Mars

[Markus Knauer]

Update to our first planning: After a longer discussion we've decided to go
back to a yearly release cycle for the next RAP release in order to have
enough time to stabilize our API and to make all required changes in the
project.

As a result of this we are going to deliver RAP 3.0 [1] together with Mars
next year. Everything else remains unchanged, i.e. our contributions will
be available with a +2 offset as every year.

[1] https://projects.eclipse.org/projects/rt.rap/releases/3.0.0

Thanks,
Markus



On 30 July 2014 at 19:57, Markus Knauer mkna...@eclipsesource.com wrote:

 Hi all,

 the RAP project will deliver two 3.x releases until Mars in 2015, a
 complete overview of our currently planned releases is available from our
 mailing list [1].

 Up to and including Mars M4, we are going to contribute RAP 3.0 milestone
 builds to Mars: Plan is available at [2].
 From 2015 on we will contribute RAP 3.1 builds to Mars [3]. Content is
 still to be defined, but all the dates are already in the plan document.

 As always... RAP contributions should be available with +2.

 Thanks,
 Markus

 [1] http://dev.eclipse.org/mhonarc/lists/rap-dev/msg01153.html
 [2] https://projects.eclipse.org/projects/rt.rap/releases/3.0.0
 [3] https://projects.eclipse.org/projects/rt.rap/releases/3.1.0




-- 

###
EclipseSource Group
Telefon: +49 721 664733-0 (GMT +2)
Telefax: +49 721 66473329

http://eclipsesource.com


Innoopract Informationssysteme GmbH
Lammstrasse 21, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Where to get last Mars aggregation snapshot ?

[Markus Knauer]

Hi Mickael,

this document in the wiki should describe what you are looking for:
https://wiki.eclipse.org/SimRel/Overview

The 'nightly' aggregation build output of the current Simultaneous Release
is always available from the p2 repository at
http://download.eclipse.org/releases/staging/.

Hope that helps,
Markus

On Thu, Nov 13, 2014 at 1:29 PM, Mickael Istria mist...@redhat.com wrote:

  Hi,

 I've recently contributed an entry for THyM in the aggregator.
 Where can I find the output repository of continuous build in order to
 test this stuff?

 Cheers,
 --
 Mickael Istria
 Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
 My blog http://mickaelistria.wordpress.com - My Tweets
 http://twitter.com/mickaelistria

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Where to get last Mars aggregation snapshot ?

[Markus Knauer]

I didn't want to confuse anyone...

http://download.eclipse.org/releases/staging/ - unfortunately both is 'kind
of' true ;-)

Staging is used for making aggregation build results available whenever
there is a change in the org.eclipse.simrel.build Git repository and the
aggregation build is successful, UNLESS we are in the last phase of the
milestone like now. Between +3 day and the release on Friday the content in
staging isn't updated and the Hudson aggregation jobs are disabled. One
reason for this is to allow to build the EPP packages, another reason is to
allow for better testing of the p2 repository. In other words: At the
moment /releases/staging contains what will be released as M3 tomorrow.

Before the release day the content of staging is being copied to the
release directory (in that case a directory below /releases/mars/...) to
give the Eclipse mirrors some time to sync.

On release day the new content is added to /releases/mars/... and made
available to the public. /releases/mars itself is a composite p2 repository
and contains the last milestone builds.

Usually at the weekend after the release the Hudson aggregation jobs for
/releases/staging are enabled again. From this point on it is possible that
the content of this repository changes.

Maybe this explains better how it works... if not... feel free to ask again.

Regards,
Markus









On Thu, Nov 13, 2014 at 2:54 PM, Mickael Istria mist...@redhat.com wrote:

  On 11/13/2014 02:27 PM, Markus Knauer wrote:

   Hi Mickael,

 Hi,

  this document in the wiki should describe what you are looking for:
 https://wiki.eclipse.org/SimRel/Overview

  The 'nightly' aggregation build output of the current Simultaneous
 Release is always available from the p2 repository at
 http://download.eclipse.org/releases/staging/.
  Hope that helps,

 Kind of ;)
 So I'm a bit confused now. An earlier mail said that releases/staging was
 the M3 build candidate (build candidate == staging in my understanding of
 staging). And now you tell me that staging is actually the latest snapshot
 from CI... That seems strange to me as I would expect the build
 candidate/staging site to be immutable until build is released, whereas I
 would expect the snapshot site to change independently of the staging
 repository status.
 Aren't we missing a step here?
 --
 Mickael Istria
 Eclipse developer at JBoss, by Red Hat http://www.jboss.org/tools
 My blog http://mickaelistria.wordpress.com - My Tweets
 http://twitter.com/mickaelistria

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Still disabled features/repositories for Mars M2?

[Markus Knauer]

Hi Dennis,

I disabled the emf-emf-rap contribution for Mars M1 because EMF wasn't RAP
compatible at that time. I don't know the current state of EMF, but it
would be great if this contribution can be re-enabled for M2:

On Wed, Oct 1, 2014 at 6:17 PM, David M Williams david_willi...@us.ibm.com
wrote:

 emf-emf-rap.b3aggrcon - org.eclipse.simrel.build


Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] HIPP access to download area

[Markus Knauer]

Hi developers,

FYI... if you are running your build jobs on a HIPP instance and you are
publishing the build artifacts in your build job to the download area, you
may be affected by this problem:

  *Bug 444894* https://bugs.eclipse.org/bugs/show_bug.cgi?id=444894 - [HIPP]
Download area unmounted on various HIPP instances
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=444894

I cannot tell if only some HIPP instances are affected, or all of them, but
I'm sure that the webmasters will fix this quickly.

Thanks,
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Luna SR1 RC3 packages available

[Markus Knauer]

Just one last announcement before the weekend: The EPP Luna SR1 RC3
packages have found their way to the developer's tab on the download page:

  https://www.eclipse.org/downloads/index-developer.php?release=luna

Thanks and enjoy your weekends,

Markus


On Thu, Sep 11, 2014 at 2:15 AM, David M Williams david_willi...@us.ibm.com
 wrote:

 I've  disabled the build job until Friday, to avoid confusion as EPP
 finishes up With Luna RC3.

 Thanks all ... one week left! (for contributions ... followed by a quiet
 week buffer).




 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Luna SR2 RC2 repository is complete.

[Markus Knauer]

The Luna SR1 RC2 packages are available from the developer build tab of the
download page:

  https://www.eclipse.org/downloads/index-developer.php?release=luna

The visible name of the Standard package on the web page has been changed
to Eclipse IDE for Eclipse Committers. IDs, filenames, and other
internals of the package have not been changed in Luna SR1. The details of
this change are discussed in [1] and [2].

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=443296
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=441957

Thanks,
Markus


On Thu, Sep 4, 2014 at 2:32 AM, David M Williams david_willi...@us.ibm.com
wrote:

 If no blocking problem found, this repo, at .../releases/maintenance will
 be our Simultaneous Release SR1 RC2 Candidate.

 I almost said Friday at 10 AM, but then remembered this repo is not
 promoted anywhere. But, EPP packages should be ready for public testing
 approximately 10 AM Friday.

 I have disabled the Luna aggregation, until Friday afternoon, but have
 left Mars running, since there's not reason to 'pause' it ... this week.

 Thanks all,

 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] e(fx)clipse participating in Mars release

[Markus Knauer]

While you're at it, maybe it would be interesting to integrate e(fx)clipse
in a package? Maybe the Java package? A bug report at [1] could help
starting a discussion about this ;-)

[1]
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPPcomponent=java-package

Thanks,
Markus

On Wed, Aug 20, 2014 at 10:46 AM, Tom Schindl tom.schi...@bestsolution.at
wrote:

 Hi,

 e(fx)clipse would like to join the Mars release as a +3 component
 because we depend on Xtext who is +2.

 Our current plan is to contribute e(fx)clipse 2.0 because this is the
 first time we are joining (I need to make myself familiar with the
 process) I'm not sure we manage to contribute to M1 in time.

 Tom
 ___
 cross-project-issues-dev mailing list
 cross-project-issues-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] RAP 3.x for Mars

[Markus Knauer]

Hi all,

the RAP project will deliver two 3.x releases until Mars in 2015, a
complete overview of our currently planned releases is available from our
mailing list [1].

Up to and including Mars M4, we are going to contribute RAP 3.0 milestone
builds to Mars: Plan is available at [2].
From 2015 on we will contribute RAP 3.1 builds to Mars [3]. Content is
still to be defined, but all the dates are already in the plan document.

As always... RAP contributions should be available with +2.

Thanks,
Markus

[1] http://dev.eclipse.org/mhonarc/lists/rap-dev/msg01153.html
[2] https://projects.eclipse.org/projects/rt.rap/releases/3.0.0
[3] https://projects.eclipse.org/projects/rt.rap/releases/3.1.0
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] EPP 4.5 for Mars

[Markus Knauer]

Next one...

EPP is planning to provide download packages based on the aggregated Mars
p2 repository; build time is +EPP (i.e. after +3) usually on Thursdays. See
[1] for a plan with the dates that will be adjusted according to the
Simultaneous Release dates. Other plan items will be added during the first
milestones.

Thanks,
Markus


[1]
https://projects.eclipse.org/projects/technology.packaging/releases/4.5.0/plan
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev