Re: [cross-project-issues-dev] Sorry, entering a bug into the product JDT has been disabled.,

2022-04-18 Thread Sravan K Lakkimsetti
Thanks Ed for the response.

Regarding search across organizations, you can use github advanced query 
feature https://github.com/search/advanced
I added 
https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+org%3Aeclipse-platform+org%3Aeclipse-jdt+org%3Aeclipse-pde+org%3Aeclipse-equinox+%s
 as search engine in google chrome to search across organizations. I would say 
it is possible and with one time configuration of browser, search should become 
simpler.

Hope this helps

-Sravan



From: cross-project-issues-dev  
On Behalf Of Ed Merks
Sent: 18 April 2022 17:26
To: cross-project-issues-dev@eclipse.org
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Sorry, entering a bug into 
the product JDT has been disabled.,


Ed,

The fate of Bugzilla, Gerrit, git.eclipse.org.and wiki.eclipse.org was 
announced to all committers:

  https://www.eclipse.org/lists/eclipse.org-committers/msg01340.html

The announcement included a plan:

  
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Gerrit/Gerrit-and-Bugzilla-deprecation-and-migration-plan

It also included a place for providing feedback:

  https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/678

The platform has diligently migrated everything to Github, so that's a done 
deal and will not be undone.

Certainly there are issues with issues, e.g., you can't really move them 
between organizations, when an organization has many repos, it's not so clear 
where to open and issue, and how to search for issues across repos and 
organizations isn't clear.

Note that the Eclipse TLP has 4 organizations.

https://github.com/eclipse-equinox/
https://github.com/eclipse-jdt/
https://github.com/eclipse-pde/
https://github.com/eclipse-platform/

There are also advantages to issue, e.g., the user interface is much richer, 
allowing to create nice documentation with images and examples.

In any case, the place to  have a discussions, and to suggest concrete 
proposals to mitigate the downsides, is here rather than the mailing list:

  https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/678

Regards,
Ed
On 18.04.2022 13:19, Ed Willink wrote:

Hi

Surely the fix is to abort this mad vandalism and so avoid the need to chase 
endless ripples?

While changing the spelling of git.eclipse.org and wiki.eclipse.org might be 
necessary and a manageable pain mitigated by redirects, terminating Bugzilla is 
madness.

Bugzilla has been providing an invaluable to service to the platform and JDT 
for over 20 years and as such is THE record of many design decisions. The 
integrity of this record should not lightly be discarded, particularly given 
that Bugzilla is not EOL. Ok it is not seeing much progress towards version 6, 
but to me that just demonstrates that it is adequate. Proposed replacements are 
far from adequate.

Eclipse is an aggregate of many projects and so we have long encouraged users 
to report their bug making a best guess at the correct product, sure in the 
knowledge that it can be re-componented.

For instance https://bugs.eclipse.org/bugs/show_activity.cgi?id=578944 was 
recently plausibly raised as an EMF bug, but then equally plausibly triaged as 
an OCL bug. Upon investigation this was bounced back again to EMF with the 
option to bounce further to platform. Bugzilla supports this very cleanly.

For instance again, last week I was forced to raise 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=579718 against PDE since JDT has 
gone. hoping that some PDE recipient would know what the new technology for 
re-componenting was. Instead a comment suggests that this is likely a side 
effect of the 16 year old https://bugs.eclipse.org/bugs/show_bug.cgi?id=99622 
that is still being worked on.

Examination of Bug 99622 shows that although JDT bugs have been moved to 
archive the active bugs have not yet been migrated and that no moved 
notifications have been sent.

It seems essential that ALL bugzillas from ALL 'platform' projects should be 
kept in the SAME search space; Bugzilla provides this. Replacements do not. 
This would seem to apply until some major disruption such as "e5" may justify 
the new team starting a new bug train for the new activity. Until then please 
keep e3 and e4 together.

For Modeling projects this is even more of an imperative. Sadly Eclipse and 
World Modeling is dying so the amount of new work in the next 20 years is 
likely to be much less than that in the last twenty. It is therefore crazy to 
split the dying embers off from their predecessors. If/when some magic new team 
of

Re: [cross-project-issues-dev] Contribution of 4.23 RC2a from platform

2022-03-09 Thread Sravan K Lakkimsetti
Hi,

Platform has completed its RC2a contribution to simrel.
RC2a has fix for Bug 
579119<https://bugs.eclipse.org/bugs/show_bug.cgi?id=579119> - Large file 
association editor prompt appears even when disabled

Thanks
Sravan


From: Sravan K Lakkimsetti
Sent: 08 March 2022 10:30
To: cross-project-issues-dev@eclipse.org
Subject: Contribution of 4.23 RC2a from platform

Hi,

Platform team got a new Bug 
579119<https://bugs.eclipse.org/bugs/show_bug.cgi?id=579119> - Large file 
association editor prompt appears even when disabled requiring respin of 4.23.
We are in the process of respin and will contribute platform RC2a by 
tomorrow(Wednesday)

Thanks and Regards,
Sravan

Sravan Kumar Lakkimsetti
Eclipse Platform Co-lead
IBM India Pvt Ltd,
Embassy Golf Links Business Park, C Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India

___
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] Contribution of 4.23 RC2a from platform

2022-03-07 Thread Sravan K Lakkimsetti
Hi,

Platform team got a new Bug 
579119 - Large file 
association editor prompt appears even when disabled requiring respin of 4.23.
We are in the process of respin and will contribute platform RC2a by 
tomorrow(Wednesday)

Thanks and Regards,
Sravan

Sravan Kumar Lakkimsetti
Eclipse Platform Co-lead
IBM India Pvt Ltd,
Embassy Golf Links Business Park, C Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India

___
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] SimRel: retention time for milestone and release candidate repos

2021-08-26 Thread Sravan K Lakkimsetti



+1
At platform we do remove all milestones and release candidates on the
release day. According to Photon's final daze
https://wiki.eclipse.org/Photon/Final_Daze we are supposed to remove
previous milestones and release candidates during RC phase. I propose
removal by M1 itself.

Thanks and Regards,
Sravan

Sravan Kumar Lakkimsetti
IBM India Pvt Ltd,
Embassy Golf Links Business Park, C Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India



From:   "Ed Merks" 
To: cross-project-issues-dev@eclipse.org
Date:   26-08-2021 20:12
Subject:[EXTERNAL] Re: [cross-project-issues-dev] SimRel: retention
time for milestone and release candidate repos
Sent by:"cross-project-issues-dev"




+1


I expect that most people with time and diligence remove all milestones and
release candidates after a release's GA.



On 26.08.2021 15:42, Jonah Graham wrote:

  ~~~
  Jonah Graham
  Kichwa Coders
  www.kichwacoders.com


  On Thu, 26 Aug 2021 at 09:00, Aleksandar Kurtakov <
  akurt...@redhat.com> wrote:


On Thu, Aug 26, 2021 at 3:49 PM Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:
 Hi,

 Are there any good reasons to keep milestone repos, release
 candidate
 repos and repos that were replaced with a respin around for an
 extended
 time (or forever)?

 @Jonah: A similar question could be asked for the retention time
 of EPP
 milestone and release candidates _repos_.

 This should not concern the EPP artifacts for milestones and
 release
 candidates on the download website. I think there are good reasons
 to
 keep the EPP packages around.

 E.g. the 2018-09 SimRel release contains seven p2 repos (M1, M2,
 M3,
 RC1, RC2, and two respins). Only the final release (the last
 respin) is
 relevant AFAICT. This would save 10-15GB disk space per release
 depending on the number of respins.

 I'd propose that all repos of a release (e.g. 2021-06) are kept
 until
 the next final release (e.g. 2021-09) has dropped. Everything
 except the
 final release repo (of 2021-06) will then be removed. This would
 set the
 retention time to roughly three months.

 WDYT?

+1. Keeping M* and RC* builds is pointless past GA.

  +1 - to be clear, you can probably reduce the retention time you have
  proposed. AFAIK Incoming projects (like Platform / CDT) discard M and
  RC builds just after GA.

  EPP's retention policy is to only keep releases (repos and full
  products) after release. I am supposed to do the cleanup on each
  release, but I sometimes run out of time and clean up multiple
  releases in one go. It is one of the steps in my release checklist.
  See "rsync the downloads area to archive.eclipse.org and remove non-R
  downloads." in
  
https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/RELEASING.md


  Jonah





 Regards,

 Fred


 --
 Frederic Gurr
 Release Engineer | Eclipse Foundation Europe GmbH

 Berliner Allee 47, D-64295 Darmstadt
 Handelsregister: Darmstadt HRB 92821
 Managing Directors: Gaël Blondelle, Mike Milinkovich
 ___
 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


--
Aleksandar Kurtakov
Red Hat Eclipse Team
___
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] git rollback?

2021-08-03 Thread Sravan K Lakkimsetti



Platform I-build from July 31(last successful build for platform) has gone
missing
https://download.eclipse.org/eclipse/downloads/drops4/I20210731-1800/ also
related git tags gone missing from the repository.

Thanks and Regards,
Sravan

Sravan Kumar Lakkimsetti
IBM India Pvt Ltd,
Embassy Golf Links Business Park, C Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India



From:   "Ed Willink" 
To: cross-project-issues-dev@eclipse.org
Date:   04-08-2021 10:00
Subject:[EXTERNAL] Re: [cross-project-issues-dev] git rollback?
Sent by:"cross-project-issues-dev"




Hi


Same for OCL.


I pushed a branch commit that successfully refreshed everything on the
branch with the result that the IT team now need to resolve a merge of the
rolled back copy, the incremental backed up history and the post
'no-outage' changes.


    Regards


        Ed Willink


On 04/08/2021 02:34, Jonah Graham wrote:

  On Tue, 3 Aug 2021 at 18:25, Stephan Herrmann <
  stephan.herrm...@berlin.de> wrote:
Has the jdt.core git been rolled back?

  I don't know - it certainly looks like it. AFAIK the git URL links
  you posted are mirrors of the gerrit repos. The gerrit repos are the
  primary IIUC. In gerrit the referenced review is still active -
  https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/183569 - so it
  looks like gerrit took a step backwards, rather than just git by
  itself. For the latter commit, the gerrit entry is "broken"
  https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/183573

Locally pulling doesn't provide anything newer than 2021-07-26.

  Same for me.


Is this an effect of the recent incident?

  Probably, but I don't know. @Webmaster will have to comment.


Any other project seeing similar effects?

  Yes. CDT has at least one gerrit from July 31st that has lost a
  patchset and associated comments. I have them in my email, but they
  are missing from gerrit:

  https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/183568

  The metadata in the email is below, and there is no such comment in
  the gerrit:

  Gerrit-Project: cdt/org.eclipse.cdt
  Gerrit-Branch: master
  Gerrit-Change-Id: I96589e86bee561aa200a4a4487549305765d6409
  Gerrit-Change-Number: 183568
  Gerrit-PatchSet: 4
  Gerrit-Owner: Mat Booth 
  Gerrit-Reviewer: CDT Bot 
  Gerrit-Comment-Date: Sat, 31 Jul 2021 20:04:45 +

  You can also see evidence of the mismatch in CDT's build jobs.

  https://ci.eclipse.org/cdt/job/cdt-verify-test-cdt-ui-only-pipeline/3450/
   and
  https://ci.eclipse.org/cdt/job/cdt-verify-test-cdt-ui-only-pipeline/3451/
   both built PS4, but 3450 built the now lost patchset, so the sha1
  for the same ref is different:

  image.png


  HTH,
  Jonah



Stephan
___
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

 --- 
Virus-free.  
www.avast.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] Move JDT to Java 11

2021-06-16 Thread Sravan K Lakkimsetti

ECJ is a standalone jar doesn't have any other dependencies. I guess this
request to move this jar to Java 11.
Since Oracle has dropped compilation targets below 8 in latest JDK I would
suggest restricting support to LTS versions of Java. This doesn't mean we
make code changes to drop the support explicitly. We just don't continue to
test on these non LTS versions and no support will be provided.

Thanks
Sravan

-Original Message-
From: Christian Dietrich 
Sent: 16 June 2021 19:05
To: cross-project-issues-dev@eclipse.org
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Move JDT to Java 11

as org.eclipse.equinox.common already requires java 11 and this is a
(transitive) dependency of jdt,
i assume jdt already effectively needs java 11 with the current release

Am 16.06.21 um 15:31 schrieb Andrey Loskutov:
> Hi all,
>
> sorry for cross-posting, but I would like to take your attention to JDT
specific topic that may affect some downstream JDT consumers.
>
> *** Request to move JDT to Java 11 ***
>
> 1) I request that JDT stops supporting compilation of JDT code on Java 8
and execution of JDT code on Java 8, for the 4.21 release, and switches to
compile JDT project code against Java 11 libraries.
> 2) If this request would be agreed / approved, I would like to add an
item to the 4.21 release plan [1] that Eclipse Compiler for Java (ecj) can
only be used on Java 11+ runtime environment.
>
> *** Reason for this request ***
>
> JDT team is a very small team, overloaded since a very long time with
support of various Java releases in compiler.
> This team can't afford to support running ecj on Java 8 AND on Java 11
AND on Java 16 AND on Java 17+ etc.
> The code complexity and the issues we see in JDT are overwhelming and
constantly growing.
> With every Java release more and more features need to be added to the
code base, and the maintenance burden is becoming bigger, not smaller!
>
> To simplify maintainers life and save time for proper Eclipse Java
compiler support we should declare end of "run on Java 8" support in JDT
code.
> To be honest: since we are not testing ecj on Java 8 since long time, no
one can guarantee that any recent ecj version can run on Java 8 anyway.
>
> *** Important note ***
>
> This request doesn't mean JDT would not support compilation of programs
with Java 8 target!
> We still support compilation targets from Java 1.3 to the latest Java
release.
>
> This request is only about JDT own project code that will be compiled
with Java 11 target. Moving JDT to Java 11 would also open a door for
possible contributions that could use API's only available since Java 9+,
but that's not the main driver here.
>
> Please note, that Eclipse platform (IDE/RCP) as a whole does not support
compilation/execution on Java 8 since 4.17 release (2020-09) and we do not
run any tests on Java 8 that would guarantee Java 8 compliance.
>
> There is a discussion on bug 572389 [2], which is not a new one. Most of
the Platform projects are already moved to compile against Java 11, only
some parts of JDT related to the standalone compiler are still
(theoretically) compatible to Java 8, the IDE part of JDT has dependencies
to libraries / bundles that only support Java 11+.
>
> *** What downstream consumers could do after move ***
>
> If JDT code base is moved to Java 11, downstream consumers can do
following:
>
> 1) Use previously released JDT / ecj versions.
> 2) Run the build/application using JDT on Java 11+.
> 3) Clone JDT code and build / maintain own fork, compatible to Java 8.
> 4) Contribute to JDT.
>
> *** Action item for PMC / JDT team ***
>
> Please, can we make a decision & have an agreement to drop "run on Java
8" support for 4.21, and move JDT code to Java 11?
> *If* not 4.21, can we please make a decision & have an agreement to drop
"run on Java 8" support in JDT for some *concrete* platform version?
>
> PS
>
> Before someone would write an answer asking JDT project to continue "run
on Java 8" support - please provide a *concrete* proposal, how *you* or
your organisation could contribute to JDT, because nobody else is there
that would have time to do that.
>
> [1]
> https://www.eclipse.org/projects/project-plan.php?planurl=http://www.e
> clipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml
> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389
>
> Kind regards,
> Andrey Loskutov
>
> Спасение утопающих - дело рук самих утопающих
>
> https://www.eclipse.org/user/aloskutov
>
> ___
> 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/

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

2021-06-12 Thread Sravan K Lakkimsetti
It took some time for me realize the problem with WTP. 

Here is what is happening. WTP uses 
https://download.eclipse.org/eclipse/updates/4.20-I-builds/ to fetch platform. 
This link is a composite p2 repository having last 5 successful builds. This 
also means if you use this link one can get jetty 10.0.5.SNAPSHOT versions as 
they are there in previous build(I20210610-1250 
 ). So 
WTP build is resolving jetty bundles against previous build(I20210610-1250 
 )  and 
mirroring them into WTP repository.

 

There are two options to fix this

1.  WTP to use specific build
2.  Platform to remove previous build (I20210610-1250 
 ) from 
composite

I removed I20210610-1250 
  from 
composite now. Please check if the jetty mirroring problem is resolved with WTP.

 

Thanks

Sravan

 

From: Nitin Dahyabhai  
Sent: 12 June 2021 09:32
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

 

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 mailto:thatnit...@gmail.com> > 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 mailto:jo...@kichwacoders.com> > 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, mailto:thatnit...@gmail.com> > 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 mailto:jo...@kichwacoders.com> > 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 mailto:thatnit...@gmail.com> > 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

___
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




 

-- 

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

___
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




 

-- 

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

2021-06-11 Thread Sravan K Lakkimsetti
Platform rebuild has been started. Kitlo will be doing the contribution after 
the build is ready.

 

Thanks

Sravan

 

From: Jonah Graham  
Sent: 12 June 2021 01:25
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

 

Thanks Joakim and the rest of the Jetty project for the fast turnarounds on 
your releases!

 

Hi folks,

 

Thanks to the Jetty project doing their release of 10.0.5 we are now ready to 
respin what needs to change.

 

@Ondrej I don't think there is anything to do for Reddeer anymore? Thank you 
for your earlier contributions.

 

Eclipse Platform / Webtools / RAP - please let me know when your pieces are in 
so that I can build the EPP build and Fred can do the simrel release prep work.

 

Jonah

 




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Fri, 11 Jun 2021 at 15:29, Joakim Erdfelt mailto:joakim.erdf...@gmail.com> > wrote:

Eclipse Jetty 10.0.5 release (not snapshot) is now available on maven central.

 

- Joakim

 

On Fri, Jun 11, 2021 at 5:48 AM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Platform testing is also complete. Verified the help feature and no issues 
found.

 

Thanks

Sravan

 

From: Markus Knauer mailto:mkna...@eclipsesource.com> > 
Sent: 11 June 2021 15:50
To: Cross project issues mailto:cross-project-issues-dev@eclipse.org> >
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

 

I finished my testing of local RAP builds based on the Jetty 10.0.5 snapshot 
consumed via WTP p2 repository, and with the latest platform build from 
yesterday:

 

Everything is looking good!

 

For those interested in the details: My tests were based on the Gerrit changes 
#181804 <https://git.eclipse.org/r/c/rap/org.eclipse.rap/+/181804>  and #181803 
<https://git.eclipse.org/r/c/rap/org.eclipse.rap.tools/+/181803>  and cover the 
installation of the RAP Tools into the new Eclipse SDK build, and the creation 
of several RAP demo projects with the new RAP Runtime. All this worked 
flawlessly and only the expected bundle versions from Jetty and SLF4J were 
installed. Now I am looking forward to the final Jetty build.

 

Thanks

Markus

 

 

On Fri, 11 Jun 2021 at 03:09, Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

On Thu, 10 Jun 2021 at 21:07, Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

The local build of simrel worked perfectly well - The expected 10.0.5 snapshot 
version* was there. You can see a log of the build and tree of the output 
directory attached.

 

Because RAP only provided me a private build for the 10.0.5 snapshot test which 
I used for my local tests, the local build doesn't match 
https://download.eclipse.org/staging/2021-06/. The staging repo has no slf4j 
(great!) but has two versions of Jetty (as expected).

 

I have built and smoke tested (basic operation, help, checked which versions 
are installed of jetty and slf4j) EPP packages locally against my local simrel 
build and all looks good. I am not running the EPP build against the public 
staging repo. Other than the final versions of Jetty we can do preliminary 
testing on that ahead of the final build.

 

I am *now* running the EPP build

 


So now we wait for the official 10.0.5 release of Jetty and we'll be good to go.

 

Jonah

 

 

* The Platform and WTP repackaging of 10.0.5-SNAPSHOT took different 
approaches, so while they are built from the same maven coordinates, the ones 
in platform are version 10.0.5.SNAPSHOT and the ones from webtools is 
10.0.5.20210610181657




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Thu, 10 Jun 2021 at 18:50, Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

I have just seen that WTP has done the simrel contribution (thanks Nitin). 

 

RAP have provided me a private build.

 

I am building everything locally now and will advise later today.

 

Thanks,

Jonah 

 

On Thu., Jun. 10, 2021, 18:47 Jonah Graham, mailto:jo...@kichwacoders.com> > wrote:

👍

 

I was curious whether there is any changes to rerdeer needed going forward now 
that it isn't republishing SLF4J alpha.

 

Perhaps there is nothing more needed.

 

I assume the WTP update is coming soon. Nitin, let me know if you need anything 
in this regard.

 

Thanks

Jonah 

 

On Thu., Jun. 10, 2021, 18:37 Ondrej Dockal, mailto:odoc...@redhat.com> > wrote:

Hi Jonah,

 

I have rebuilt my release update site, though, anything except reddeer bundles 
timestamps have changed, as expected. But to initiate an aggregator validation 
I have prepared a gerrit commit (without actual change to 

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

2021-06-11 Thread Sravan K Lakkimsetti
Platform testing is also complete. Verified the help feature and no issues 
found.

 

Thanks

Sravan

 

From: Markus Knauer  
Sent: 11 June 2021 15:50
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

 

I finished my testing of local RAP builds based on the Jetty 10.0.5 snapshot 
consumed via WTP p2 repository, and with the latest platform build from 
yesterday:

 

Everything is looking good!

 

For those interested in the details: My tests were based on the Gerrit changes 
#181804 <https://git.eclipse.org/r/c/rap/org.eclipse.rap/+/181804>  and #181803 
<https://git.eclipse.org/r/c/rap/org.eclipse.rap.tools/+/181803>  and cover the 
installation of the RAP Tools into the new Eclipse SDK build, and the creation 
of several RAP demo projects with the new RAP Runtime. All this worked 
flawlessly and only the expected bundle versions from Jetty and SLF4J were 
installed. Now I am looking forward to the final Jetty build.

 

Thanks

Markus

 

 

On Fri, 11 Jun 2021 at 03:09, Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

On Thu, 10 Jun 2021 at 21:07, Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

The local build of simrel worked perfectly well - The expected 10.0.5 snapshot 
version* was there. You can see a log of the build and tree of the output 
directory attached.

 

Because RAP only provided me a private build for the 10.0.5 snapshot test which 
I used for my local tests, the local build doesn't match 
https://download.eclipse.org/staging/2021-06/. The staging repo has no slf4j 
(great!) but has two versions of Jetty (as expected).

 

I have built and smoke tested (basic operation, help, checked which versions 
are installed of jetty and slf4j) EPP packages locally against my local simrel 
build and all looks good. I am not running the EPP build against the public 
staging repo. Other than the final versions of Jetty we can do preliminary 
testing on that ahead of the final build.

 

I am *now* running the EPP build

 


So now we wait for the official 10.0.5 release of Jetty and we'll be good to go.

 

Jonah

 

 

* The Platform and WTP repackaging of 10.0.5-SNAPSHOT took different 
approaches, so while they are built from the same maven coordinates, the ones 
in platform are version 10.0.5.SNAPSHOT and the ones from webtools is 
10.0.5.20210610181657




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Thu, 10 Jun 2021 at 18:50, Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

I have just seen that WTP has done the simrel contribution (thanks Nitin). 

 

RAP have provided me a private build.

 

I am building everything locally now and will advise later today.

 

Thanks,

Jonah 

 

On Thu., Jun. 10, 2021, 18:47 Jonah Graham, mailto:jo...@kichwacoders.com> > wrote:

👍

 

I was curious whether there is any changes to rerdeer needed going forward now 
that it isn't republishing SLF4J alpha.

 

Perhaps there is nothing more needed.

 

I assume the WTP update is coming soon. Nitin, let me know if you need anything 
in this regard.

 

Thanks

Jonah 

 

On Thu., Jun. 10, 2021, 18:37 Ondrej Dockal, mailto:odoc...@redhat.com> > wrote:

Hi Jonah,

 

I have rebuilt my release update site, though, anything except reddeer bundles 
timestamps have changed, as expected. But to initiate an aggregator validation 
I have prepared a gerrit commit (without actual change to aggrcon file) [1]. I 
can probably wait for [2] WTP change to rebase and rerun to make sure we are 
good.

 

[1]: https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/181811

[2]: https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/181810

 

On Thu, Jun 10, 2021 at 6:50 PM Jonah Graham mailto:jo...@kichwacoders.com> > 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 <http://www.kichwacoders.com> 

 

 

On Thu, 10 Jun 2021 at 12:26, Sravan K Lakkimsetti mailto: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 
<https://github.com/eclipse/jetty.project/issues/6354#issuecomm

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

2021-06-10 Thread Sravan K Lakkimsetti
I just contributed respin of platform to simrel with Jetty 10.0.5-snapshot. 

 

Thanks

Sravan

 

From: Jonah Graham  
Sent: 11 June 2021 00:49
To: Cross project issues ; Frederic Gurr 

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 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. 

 

 <mailto:frederic.g...@eclipse-foundation.org> @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, mailto:thatnit...@gmail.com> > 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 mailto:mkna...@eclipsesource.com> > 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 mailto:jo...@kichwacoders.com> > 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 <http://www.kichwacoders.com> 

 

 

On Thu, 10 Jun 2021 at 12:26, Sravan K Lakkimsetti mailto: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 
<https://github.com/eclipse/jetty.project/issues/6354#issuecomment-858764165> 

 

Thanks

Sravan

 

From: Jonah Graham mailto:jo...@kichwacoders.com> > 
Sent: 10 June 2021 21:36
To: Cross project issues mailto:cross-project-issues-dev@eclipse.org> >
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 
<https://github.com/eclipse/jetty.project/issues/6354#issuecomment-858733158> 

 

Thanks,

Jonah 

 

On Thu., Jun. 10, 2021, 10:23 Jonah Graham, mailto:jo...@kichwacoders.com> > wrote:

Hi folks,

 

We are making very good progress on resolving this issue, in no part thanks to 
everyone that has been super responsive in updating their bits.

 

I checked all the EPP packages and (as expected) only JEE has 
slf4j.api_2.0.0.alpha1.jar. All the packages (also as expected) have 
org.slf4j.api_1.7.30.v20200204-2150.jar (including JEE).

 

The Jetty project is just about to push out a snapshot 
(https://github.com/eclipse/jetty.project/issues/6390 
<https://github.com/eclipse/jetty.project/issues/6390> ) of 10.0.5 that fully 
resolves the slf4j 2.0.0 alpha1 dependency so that the SimRel and JEE package 
won't have alpha1 jar anymore.

 

To reduce the change of a turnaround time again we can collectively test that 
the 10.0.5 snapshot resolves all the issues. Note that this a further 10.0.5 
snapshot than we had yesterday.

 

RIght now, I don't know how to do this test without a full respin of everything 
(platform , redeer(?) , webtools, rap).

 

Any suggestions are very welcome.

 

Thanks,
Jonah

 

 

 




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Wed, 9 Jun 2021 at 16:56, Ondrej Dockal mailto:odoc...@redhat.com> > 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

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

2021-06-10 Thread Sravan K Lakkimsetti
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 
 

 

Thanks,

Jonah 

 

On Thu., Jun. 10, 2021, 10:23 Jonah Graham, mailto:jo...@kichwacoders.com> > wrote:

Hi folks,

 

We are making very good progress on resolving this issue, in no part thanks to 
everyone that has been super responsive in updating their bits.

 

I checked all the EPP packages and (as expected) only JEE has 
slf4j.api_2.0.0.alpha1.jar. All the packages (also as expected) have 
org.slf4j.api_1.7.30.v20200204-2150.jar (including JEE).

 

The Jetty project is just about to push out a snapshot 
(https://github.com/eclipse/jetty.project/issues/6390 
 ) of 10.0.5 that fully 
resolves the slf4j 2.0.0 alpha1 dependency so that the SimRel and JEE package 
won't have alpha1 jar anymore.

 

To reduce the change of a turnaround time again we can collectively test that 
the 10.0.5 snapshot resolves all the issues. Note that this a further 10.0.5 
snapshot than we had yesterday.

 

RIght now, I don't know how to do this test without a full respin of everything 
(platform , redeer(?) , webtools, rap).

 

Any suggestions are very welcome.

 

Thanks,
Jonah

 

 

 




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com  

 

 

On Wed, 9 Jun 2021 at 16:56, Ondrej Dockal mailto:odoc...@redhat.com> > 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 mailto:jo...@kichwacoders.com> > 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 mailto:jo...@kichwacoders.com> > 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 mailto:odoc...@redhat.com> > 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 mailto:jo...@kichwacoders.com> > 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 Code

Re: [cross-project-issues-dev] Eclipse platform contribution with Jetty 10.0.4 upgrade

2021-06-09 Thread Sravan K Lakkimsetti
Thanks Patrick for understanding I will fix it in 2021-09 M1.

 

Thanks

Sravan

 

From: Patrick Tasse  
Sent: 09 June 2021 21:49
To: Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Eclipse platform 
contribution with Jetty 10.0.4 upgrade

 

Ok, yes we can put back the workaround that we added in M2.

 

If it's fixed in 2021-09 we'll remove it again like we did in M3 ;)

 

Thanks,

Patrick

 

On Wed, Jun 9, 2021 at 12:11 PM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Hi,

 

Can org.slf4j.api be added to target platform in 
https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/releng/org.eclipse.tracecompass.target/tracecompass-e4.20.target
 (we get it from Orbit see 
https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target#n73)
  and/or can this be added to 
https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/rcp/org.eclipse.tracecompass.rcp.product/tracing.product
 in the plugins section.

 

We mirror org.slf4j.api from orbit. My preference here is to fetch from orbit.

 

I would prefer not rebuild platform again.

 

Thanks 

Sravan

 

From: Patrick Tasse mailto:patrick.ta...@gmail.com> > 
Sent: 09 June 2021 20:59
To: Cross project issues mailto:cross-project-issues-dev@eclipse.org> >
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Eclipse platform 
contribution with Jetty 10.0.4 upgrade

 

Hi,

 

We depend on platform which includes help feature.

The help feature used to depend on jetty.http 10.0.2 which depends on org.slf4j 
2.0, with Bundle-SymbolicName: slf4j.api

The help feature now depends on jetty.http 10.0.4 which depends on org.slf4j 
1.7, with Bundle-SymbolicName: org.slf4j.api

 

The help feature.xml used to include feature slf4j.api, this has just been 
removed.

 

So I believe the help feature.xml must now include feature org.slf4j.api 
instead?

 

Thanks,

Patrick

 

 

On Wed, Jun 9, 2021 at 11:05 AM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Based on https://www.eclipse.org/lists/cross-project-issues-dev/msg18389.html 
there are some places you will need slf4j version 2. In all other places we 
should be good with slf4j 1.7.30. 

 

Thanks

Sravan

 

From: Nitin Dahyabhai mailto:thatnit...@gmail.com> > 
Sent: 09 June 2021 19:36
To: Cross project issues mailto:cross-project-issues-dev@eclipse.org> >
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Eclipse platform 
contribution with Jetty 10.0.4 upgrade

 

WTP doesn't contribute it either, just the ones that were needed and not 
provided in the Platform build. What I find curious is that both 
https://download.eclipse.org/eclipse/jetty/10.0.4/plugins/ and 
https://download.eclipse.org/webtools/jetty/10.0.4/repository/plugins/ ended up 
with the 2.0.0 jar in their output. What I find troubling is that we use 
jetty-plus to resolve some OSGI Require/Provide-Capability configuration once 
installed, so I expect our build will compile cleanly but the related 
functionality will fail to load properly. :(

 

On Wed, Jun 9, 2021 at 9:45 AM Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

:-( But the Platform contribution does not have slf4j.api_2.0.0.alpha1, is that 
because Platform doesn't use  jetty-jndi and jetty-plus but WTP does?

 

Thanks

Jonah




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Wed, 9 Jun 2021 at 09:40, Nitin Dahyabhai mailto:thatnit...@gmail.com> > wrote:

It looks like jetty-jndi and jetty-plus did not have their SLF4J ranges lowered 
under 2.0, so the Jetty sites from Platform and WTP both still contain 
slf4j.api_2.0.0.alpha1.

 

On Wed, Jun 9, 2021 at 9:20 AM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Hi,

 

I contributed eclipse platform with Jetty 10.0.4 and with slf4j 1.7.30. Please 
let me know if there are any problems.

 

Thanks

Sravan

 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto:cross-project-issues-dev@eclipse.org> 
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

-- 

Regards,

Nitin Dahyabhai

Eclipse WTP PMC

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto: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 
<mailto:cross-project-issues-dev@eclipse.org> 
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

-- 

Regards,


Re: [cross-project-issues-dev] Eclipse platform contribution with Jetty 10.0.4 upgrade

2021-06-09 Thread Sravan K Lakkimsetti
Hi,

 

Can org.slf4j.api be added to target platform in 
https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/releng/org.eclipse.tracecompass.target/tracecompass-e4.20.target
 (we get it from Orbit see 
https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target#n73)
  and/or can this be added to 
https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/rcp/org.eclipse.tracecompass.rcp.product/tracing.product
 in the plugins section.

 

We mirror org.slf4j.api from orbit. My preference here is to fetch from orbit.

 

I would prefer not rebuild platform again.

 

Thanks 

Sravan

 

From: Patrick Tasse  
Sent: 09 June 2021 20:59
To: Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Eclipse platform 
contribution with Jetty 10.0.4 upgrade

 

Hi,

 

We depend on platform which includes help feature.

The help feature used to depend on jetty.http 10.0.2 which depends on org.slf4j 
2.0, with Bundle-SymbolicName: slf4j.api

The help feature now depends on jetty.http 10.0.4 which depends on org.slf4j 
1.7, with Bundle-SymbolicName: org.slf4j.api

 

The help feature.xml used to include feature slf4j.api, this has just been 
removed.

 

So I believe the help feature.xml must now include feature org.slf4j.api 
instead?

 

Thanks,

Patrick

 

 

On Wed, Jun 9, 2021 at 11:05 AM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Based on https://www.eclipse.org/lists/cross-project-issues-dev/msg18389.html 
there are some places you will need slf4j version 2. In all other places we 
should be good with slf4j 1.7.30. 

 

Thanks

Sravan

 

From: Nitin Dahyabhai mailto:thatnit...@gmail.com> > 
Sent: 09 June 2021 19:36
To: Cross project issues mailto:cross-project-issues-dev@eclipse.org> >
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Eclipse platform 
contribution with Jetty 10.0.4 upgrade

 

WTP doesn't contribute it either, just the ones that were needed and not 
provided in the Platform build. What I find curious is that both 
https://download.eclipse.org/eclipse/jetty/10.0.4/plugins/ and 
https://download.eclipse.org/webtools/jetty/10.0.4/repository/plugins/ ended up 
with the 2.0.0 jar in their output. What I find troubling is that we use 
jetty-plus to resolve some OSGI Require/Provide-Capability configuration once 
installed, so I expect our build will compile cleanly but the related 
functionality will fail to load properly. :(

 

On Wed, Jun 9, 2021 at 9:45 AM Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

:-( But the Platform contribution does not have slf4j.api_2.0.0.alpha1, is that 
because Platform doesn't use  jetty-jndi and jetty-plus but WTP does?

 

Thanks

Jonah




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Wed, 9 Jun 2021 at 09:40, Nitin Dahyabhai mailto:thatnit...@gmail.com> > wrote:

It looks like jetty-jndi and jetty-plus did not have their SLF4J ranges lowered 
under 2.0, so the Jetty sites from Platform and WTP both still contain 
slf4j.api_2.0.0.alpha1.

 

On Wed, Jun 9, 2021 at 9:20 AM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Hi,

 

I contributed eclipse platform with Jetty 10.0.4 and with slf4j 1.7.30. Please 
let me know if there are any problems.

 

Thanks

Sravan

 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto:cross-project-issues-dev@eclipse.org> 
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

-- 

Regards,

Nitin Dahyabhai

Eclipse WTP PMC

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto: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 
<mailto:cross-project-issues-dev@eclipse.org> 
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

-- 

Regards,

Nitin Dahyabhai

Eclipse WTP PMC

 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto: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] Eclipse platform contribution with Jetty 10.0.4 upgrade

2021-06-09 Thread Sravan K Lakkimsetti
Based on https://www.eclipse.org/lists/cross-project-issues-dev/msg18389.html 
there are some places you will need slf4j version 2. In all other places we 
should be good with slf4j 1.7.30. 

 

Thanks

Sravan

 

From: Nitin Dahyabhai  
Sent: 09 June 2021 19:36
To: Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Eclipse platform 
contribution with Jetty 10.0.4 upgrade

 

WTP doesn't contribute it either, just the ones that were needed and not 
provided in the Platform build. What I find curious is that both 
https://download.eclipse.org/eclipse/jetty/10.0.4/plugins/ and 
https://download.eclipse.org/webtools/jetty/10.0.4/repository/plugins/ ended up 
with the 2.0.0 jar in their output. What I find troubling is that we use 
jetty-plus to resolve some OSGI Require/Provide-Capability configuration once 
installed, so I expect our build will compile cleanly but the related 
functionality will fail to load properly. :(

 

On Wed, Jun 9, 2021 at 9:45 AM Jonah Graham mailto:jo...@kichwacoders.com> > wrote:

:-( But the Platform contribution does not have slf4j.api_2.0.0.alpha1, is that 
because Platform doesn't use  jetty-jndi and jetty-plus but WTP does?

 

Thanks

Jonah




~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com <http://www.kichwacoders.com> 

 

 

On Wed, 9 Jun 2021 at 09:40, Nitin Dahyabhai mailto:thatnit...@gmail.com> > wrote:

It looks like jetty-jndi and jetty-plus did not have their SLF4J ranges lowered 
under 2.0, so the Jetty sites from Platform and WTP both still contain 
slf4j.api_2.0.0.alpha1.

 

On Wed, Jun 9, 2021 at 9:20 AM Sravan K Lakkimsetti mailto:sravankum...@in.ibm.com> > wrote:

Hi,

 

I contributed eclipse platform with Jetty 10.0.4 and with slf4j 1.7.30. Please 
let me know if there are any problems.

 

Thanks

Sravan

 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto:cross-project-issues-dev@eclipse.org> 
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

-- 

Regards,

Nitin Dahyabhai

Eclipse WTP PMC

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto: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 
<mailto:cross-project-issues-dev@eclipse.org> 
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

-- 

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


[cross-project-issues-dev] Eclipse platform contribution with Jetty 10.0.4 upgrade

2021-06-09 Thread Sravan K Lakkimsetti
Hi,

 

I contributed eclipse platform with Jetty 10.0.4 and with slf4j 1.7.30.
Please let me know if there are any problems.

 

Thanks

Sravan


___
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-pmc] [eclipse.org-planning-council] m2e 1.18.0 and SimRel 2021-06

2021-06-04 Thread Sravan K Lakkimsetti
Hi,

 

As I understand we will have fix this even if it means delaying eclipse 
release. If Platform is not able to get the build out before Wednesday June 9, 
Simrel will have to do a RC2 respin.

 

For this effort I raised  
 Bug 574035 - Update to 
Jetty 10.0.4. Can you please give a +1 on this effort.

 

Thanks

Sravan

 

From: Mike Wilson  
Sent: 05 June 2021 02:36
To: eclipse-...@eclipse.org
Cc: eclipse-...@eclipse.org; eclipse.org-planning-coun...@eclipse.org
Subject: [EXTERNAL] Re: [eclipse-pmc] [eclipse.org-planning-council] 
[cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06

 

So, if it takes a week or even two, then that's what we should do. Release 
dates do not justify doing the wrong thing.

 

McQ.

 

- Original message -
From: "Thomas Watson" mailto:tjwat...@us.ibm.com> >
Sent by: "eclipse-pmc" mailto:eclipse-pmc-boun...@eclipse.org> >
To: eclipse.org-planning-coun...@eclipse.org 
 
Cc: eclipse-...@eclipse.org  , 
eclipse.org-planning-coun...@eclipse.org 
 
Subject: [EXTERNAL] Re: [eclipse-pmc] [eclipse.org-planning-council] 
[cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06
Date: Fri, Jun 4, 2021 11:13 AM
 
Update. I tried out the snapshot jetty bundles with the fix. It did allow me to 
remove slf4j 2.0. But it sounds like the earliest we would see a Jetty release 
with the fix is the middle/end of next week: 
https://github.com/eclipse/jetty.project/issues/6354 
  
ZjQcmQRYFpfptBannerStart 




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd

Update.  I tried out the snapshot jetty bundles with the fix.  It did allow me 
to remove slf4j 2.0.  But it sounds like the earliest we would see a Jetty 
release with the fix is the middle/end of next week: 
https://github.com/eclipse/jetty.project/issues/6354 
 


Tom
 

 

 

- Original message -
From: "Thomas Watson" mailto:tjwat...@us.ibm.com> >
Sent by: "eclipse.org-planning-council" 
mailto:eclipse.org-planning-council-boun...@eclipse.org> >
To: eclipse.org-planning-coun...@eclipse.org 
 , eclipse-...@eclipse.org 
 
Cc: eclipse.org-planning-coun...@eclipse.org 
 
Subject: [EXTERNAL] Re: [eclipse.org-planning-council] 
[cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06
Date: Fri, Jun 4, 2021 7:25 AM
 
Not to throw a wrench into the whole plan here, but I did manage to get a PR 
merged into Jetty to allow 10.0.x Jetty to tolerate slf4j 1.7.x. I don't know 
the feasibility of either of these things but what if: 1) Jetty was able to 
quickly turn ZjQcmQRYFpfptBannerStart 




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd

Not to throw a wrench into the whole plan here, but I did manage to get a PR 
merged into Jetty to allow 10.0.x Jetty to tolerate slf4j 1.7.x.  I don't know 
the feasibility of either of these things but what if:

1) Jetty was able to quickly turn around a service release of 10.0.x including 
the fix (https://github.com/eclipse/jetty.project/pull/6356 
 )

2) The Eclipse project updated to the latest release and returned to pulling in 
the stable version of slf4j

3) Everything else on the train goes back to the way it was?

 

Do we have time, is this possible?  Wouldn't this be a better solution all 
around, even if it causes a delay?


Tom
 

 

 

- Original message -
From: Jonah Graham mailto:jo...@kichwacoders.com> >
Sent by: "eclipse.org-planning-council" 
mailto:eclipse.org-planning-council-boun...@eclipse.org> >
To: Eclipse Planning Council private list 
mailto:eclipse.org-planning-coun...@eclipse.org> >
Cc:
Subject: [EXTERNAL] Re: [eclipse.org-planning-council] 
[cross-project-issues-dev] m2e 1.18.0 and SimRel 2021-06
Date: Fri, Jun 4, 2021 5:28 AM
 
Hi Ed, The EPP builds from the staging repo, not from the release repo as the 
staging repo is what is in the announcement email - 
https://www.eclipse.org/lists/cross-project-issues-dev/msg18401.html. As for 
your screenshot, that seems to be ZjQcmQRYFpfptBannerStart 




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd

Hi Ed, 

 

The EPP builds from the staging repo, not from the release repo as the staging 
repo is what is in the announcement email - 
https://www.eclipse.org/lists/cross-project-issues-dev/msg18401.html.

 

As for your screenshot, that seems to be showing correct versions as expected, 
so that is good.

 

Jonah

  

~~~
Jonah Gra

Re: [cross-project-issues-dev] IMHO serious issues in the Eclipse Java IDE 2021-06 M3

2021-06-03 Thread Sravan K Lakkimsetti
I am not sure whether we should do it or not but this can be achieved by adding 
this line to .product files like 
https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/packages/org.eclipse.epp.package.cpp.product/epp.product#n28

 

SDK completed their RC2 work and in quiet period now. So unless it is 
absolutely necessary I would prefer not to do a RC2a. 

 

Thanks

Sravan

 

From: Jonah Graham  
Sent: 03 June 2021 22:39
To: Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] IMHO serious issues in the 
Eclipse Java IDE 2021-06 M3

 

Hi Wim/all,

 

Can the --illegal-access=permit be simply added to all eclipse.ini files by 
default (by EPP and/or SDK)? This would be similar to how Java 8 -> Java 9 
transition was handled with --add-modules=ALL-SYSTEM?

 

Thanks

Jonah

 

 

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com  

 

 

On Thu, 3 Jun 2021 at 05:05, Wim Jongman mailto:wim.jong...@gmail.com> > wrote:

The windowbuilder issue (using cglib) can maybe be fixed by using p2 
touchpoints?

 

Can a plugin add stuff to the eclipse.ini by using touchpoints [1]? 

 

[1] 
https://help.eclipse.org/2021-03/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_actions_touchpoints.html

 

On Wed, Jun 2, 2021 at 9:23 AM Holger Voormann mailto:ecli...@voormann.de> > wrote:

Hi all,

IMHO the following two issues of the Eclipse Java IDE 2021-06 M3 are 
serious, since they probably affect many and since there are no known 
workarounds for them:

1. Empty Maven console
https://github.com/eclipse-m2e/m2e-core/issues/182 
 

2. Creating of a Gradle project via the "New Gradle Project" dialog is 
broken:
https://github.com/eclipse/buildship/issues/1077 
 


In contrast, the following two issues, which I guess will also affect 
many, are not serious from my point of view, since workarounds are known:

3.
[JEE] .js files opened by default in the Text Editor instead of in the 
Generic Text Editor
Workaround: right-click a .js file + "Open With > Other...", select 
"Generic Text Editor" and choose "Use it for all '.js' files"
https://eclip.se/573902  

4.
WindowBuilder does not work with Java 16
Workaround: in "eclipse.ini" add the line "--illegal-access=permit"
https://eclip.se/572210  


It would be great when these issues could be fixed for the 2021-06 release.


Thanks,

Holger
___
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] FW: Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: IMHO serious issues in the Eclipse Java IDE 2021-06 M3

2021-06-02 Thread Sravan K Lakkimsetti
Slf4j version 2 dependency is coming from jetty 10. At platform we are 
consuming jetty. This is where the slf4j.api version 2 is coming from. Since 
Jetty stopped building p2 repositories we built jetty p2 repositories with bare 
minimum components that are required for platform. 

 

We tried to use update Jetty around 2021-03 M3. But we thought this upgrade 
will be disruptive so we postponed to 2021-06 M1.

 

We added the feature announcement in N&N  
 
https://www.eclipse.org/eclipse/news/4.20/platform_isv.php#jetty-10-update

We also sent a note because of jetty upgrade there are conflicts in simrel to 
crossproject-dev list. There was a considerable discussion on this topic.

 

I am just listing what happened with update Jetty 10. Now we cannot go back to 
older version of slf4j that means downgrading Jetty. Now what should be the way 
forward?

 

-Sravan

 

From: Mickael Istria <  mist...@redhat.com> 
Sent: 02 June 2021 14:49
To:   eclipse-...@eclipse.org
Cc: Discussions on Eclipse IDE Working Group < 
 eclipse-ide...@eclipse.org>
Subject: [EXTERNAL] Re: [eclipse-ide-wg] [eclipse-pmc] Fwd: 
[cross-project-issues-dev] IMHO serious issues in the Eclipse Java IDE 2021-06 
M3

 

Thanks for raising this issue folks. About Orbit or not, I fail at seeing what 
would that change: if slf4j 2.0 -which is a requirement- were in Orbit, how 
would that have prevented this issue in m2e from happening? ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ 
‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ZjQcmQRYFpfptBannerStart 




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd

Thanks for raising this issue folks.

About Orbit or not, I fail at seeing what would that change: if slf4j 2.0 
-which is a requirement- were in Orbit, how would that have prevented this 
issue in m2e from happening?


___
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] Disabling of XWT and in turn papyrus for 2021-06 M3 due to bug 570454

2021-05-20 Thread Sravan K Lakkimsetti
Hi,

 

In 2021-06 M3, as part of
 Bug 570454 - Make
ECommandService and EHandlerService API official some of e4
services(org.eclipse.e4.core.commands) have been made official and their
major versions have been incremented. Because of this contribution from
XWT has been failing as it was dependent on older version. 

I am disabling XWT and Papyrus as they are dependent on
org.eclipse.e4.core.commands for now

Please create a new version of XWT and reenable XWT and Papyrus in simrel.

Thanks and Regards,
Sravan 

Sravan Kumar Lakkimsetti
IBM India Pvt Ltd,
Embassy Golf Links Business Park, C Block,
Off Indiranagar-Kormangla Inner Ring Road,
Bangalore - 560071, India

 


___
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] [platform-dev] Signed content

2021-05-03 Thread Sravan K Lakkimsetti
Hi Ed,

 

I am sorry If I offended you with my earlier mail. Let me clarify my stance on 
signing.

 

Any bundle that is built by Eclipse project has to be signed. To me this is 
non-negotiable.

 

The discussion is on the orbit bundles that gets built by fetching from maven 
central. By signing these we are actually creating new bundle which can 
diverge(technically) from the source(maven central). In this case the vendor 
will not responsible(as we modified the bundle) from problems we encounter in 
the bundle. This is something I want to find a solution for. We had discussions 
but there is no concrete solution in this matter. 

 

I hope I clarified my position in this matter.  

 

Thanks

Sravan

 

From: Ed Merks  
Sent: 03 May 2021 11:57
To: Eclipse platform general developers list. ; Cross 
project issues ; Eclipse Planning Council 
; eclipse-ide...@eclipse.org
Subject: [EXTERNAL] Re: [cross-project-issues-dev] [platform-dev] Signed content

 

Sravan, I flushed the cache on the job's workspace and reran it from scratch. 
https://ci.eclipse.org/oomph/job/repository-analyzer/ This time it did not find 
unsigned jars from the platform's builds nor in the SimRel aggregation. So most 
likely ZjQcmQRYFpfptBannerStart 




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd



Sravan,

I flushed the cache on the job's workspace and reran it from scratch.  

  https://ci.eclipse.org/oomph/job/repository-analyzer/

This time it did not find unsigned jars from the platform's builds nor in the 
SimRel aggregation.  So most likely there was some build at some time in which 
these were not signed, and those were cached the first time they were visible.  
There's no way to track down such artifact history when the IU IDs are 
identical; and these IUs have no qualifier in the version...

Sorry for the false alarm.  The platform never has made such mistakes in the 
past, so the basic assumption was that this therefore was a deliberate choice, 
especially given the ongoing discussions about not signing things like Jetty in 
particular.  Sorry for jumping to conclusions.  

I feel better with your statement that such a change would not be made 
unilaterally and without notice.

Regards,
Ed

On 02.05.2021 14:11, Sravan K Lakkimsetti wrote:

I don’t this mail is in good intentions. This is really offending and upsetting.

 

This was not reported with the repository analysers either in platform 
<https://download.eclipse.org/eclipse/downloads/drops4/I20210429-1800/buildlogs/reporeports/index.html>
  or simrel 
<https://download.eclipse.org/staging/2021-06/buildInfo/reporeports/> . 

Here is the output of jarsigner when I ran on org.eclipse.jetty.util.ajax

 

C:\Users\SRAVANLAKKIMSETTI\Downloads>"c:\EclipseTest\JAVA\jdk-11.0.10+9\bin\jarsigner.exe"
 -verify org.eclipse.jetty.util.ajax_10.0.2.jar

 

jar verified.

 

We do have a test in platform to verify unsigned content in the repository. 
That test will fail if any bundle is reported as unsigned. This is based on the 
repository analyser report generated during the build. We have been using this 
for quite some time. I myself has stopped simrel contribution multiple times 
the moment I notice a problem with signing.

 

I don’t see a problem when the jarsigner returns as success.

 

-Sravan

 

 

From: Ed Merks  <mailto:ed.me...@gmail.com>  
Sent: 02 May 2021 13:41
To: Eclipse platform general developers list.  
<mailto:platform-...@eclipse.org> ; Cross project 
issues  <mailto:cross-project-issues-dev@eclipse.org> 
; Eclipse Planning Council  
<mailto:eclipse.org-planning-coun...@eclipse.org> 
; eclipse-ide...@eclipse.org 
<mailto:eclipse-ide...@eclipse.org> 
Subject: [EXTERNAL] [platform-dev] Signed content

 

Hi, I am assume from observation that the platform team has decided to change 
its signing policy to not physically sign some jars anymore:   
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/eclipse/updates/4.20-I-builds/index.html
 




Hi,

I am assume from observation that the platform team has decided to change its 
signing policy to not physically sign some jars anymore:

  
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/eclipse/updates/4.20-I-builds/index.html

This of course propagates to SimRel:

  
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/staging/2021-06/index.html

I don't recall a Planning Council policy decision to drop/change the need for 
signed jars.  I don't know the full impact this has on the installer nor on 
consumers.   The installer at least appears to happily install such things and 
the IDE presents such things to the user as if they are signed:



Slowly I get the feeling that SimRel is a no longer process where we all work 
together as a team.  Rather it feels as if t

Re: [cross-project-issues-dev] [platform-dev] Signed content

2021-05-02 Thread Sravan K Lakkimsetti
I don’t this mail is in good intentions. This is really offending and upsetting.

 

This was not reported with the repository analysers either in platform 

  or simrel 
 . 

Here is the output of jarsigner when I ran on org.eclipse.jetty.util.ajax

 

C:\Users\SRAVANLAKKIMSETTI\Downloads>"c:\EclipseTest\JAVA\jdk-11.0.10+9\bin\jarsigner.exe"
 -verify org.eclipse.jetty.util.ajax_10.0.2.jar

 

jar verified.

 

We do have a test in platform to verify unsigned content in the repository. 
That test will fail if any bundle is reported as unsigned. This is based on the 
repository analyser report generated during the build. We have been using this 
for quite some time. I myself has stopped simrel contribution multiple times 
the moment I notice a problem with signing.

 

I don’t see a problem when the jarsigner returns as success.

 

-Sravan

 

 

From: Ed Merks  
Sent: 02 May 2021 13:41
To: Eclipse platform general developers list. ; Cross 
project issues ; Eclipse Planning Council 
; eclipse-ide...@eclipse.org
Subject: [EXTERNAL] [platform-dev] Signed content

 

Hi, I am assume from observation that the platform team has decided to change 
its signing policy to not physically sign some jars anymore:   
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/eclipse/updates/4.20-I-builds/index.html
 ZjQcmQRYFpfptBannerStart 




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd



Hi,

I am assume from observation that the platform team has decided to change its 
signing policy to not physically sign some jars anymore:

  
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/eclipse/updates/4.20-I-builds/index.html

This of course propagates to SimRel:

  
https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/staging/2021-06/index.html

I don't recall a Planning Council policy decision to drop/change the need for 
signed jars.  I don't know the full impact this has on the installer nor on 
consumers.   The installer at least appears to happily install such things and 
the IDE presents such things to the user as if they are signed:



Slowly I get the feeling that SimRel is a no longer process where we all work 
together as a team.  Rather it feels as if the platform team can and does 
unilaterally make decisions for everyone else.

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] [tycho-user] Problem building with latest 2021-06 and tycho 2.3

2021-04-17 Thread Sravan K Lakkimsetti
We tried to add support for Mac M1(arm64/aarch64) processor support. It is 
still experimental. Thats the reason we did not add it to simrel.

We need to add this support in future. So please go ahead and merge this.

 

Thanks

Sravan

 

From: Ed Merks  
Sent: 17 April 2021 13:17
To: tycho-u...@eclipse.org; Eclipse Packaging Project ; 
Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] [tycho-user] Problem 
building with latest 2021-06 and tycho 2.3

 

Christian,

I imagine it's incomplete because it's not configured to be complete:



Probably it should look like this:

 



 

I tried adding it and the verification job passed:

 

  https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/179454

 

I suppose I should merge this to master; I amended it to group the mac 
configurations together.

 

I'll wait for a few hours for someone to object and then merge this; it can 
always be reverted if it's not the right decision.

 

Regards,
Ed

 

On 17.04.2021 09:16, Christian Dietrich wrote:

Hi, we have http://download.eclipse.org/releases/2021-06/202104161000
only. thus i assume the M1 repo is incomplete only.
 
here is the project i try to build
https://github.com/itemis/xtext-reference-projects/tree/cd_tycho23/domainmodel/2.26.0
 

 
and here the target
https://github.com/itemis/xtext-reference-projects/blob/cd_tycho23/domainmodel/2.26.0/org.eclipse.xtext.example.domainmodel.releng/tp/domainmodel.target
 

 
 
we have this extra requirement
https://github.com/itemis/xtext-reference-projects/blob/024c607d898937cb647e9455db7c2387a8dbdb5b/domainmodel/2.26.0/org.eclipse.xtext.example.domainmodel.releng/pom.xml#L90
 

 
 

eclipse-feature
org.eclipse.rcp
0.0.0

 
 
Am 17.04.21 um 09:05 schrieb Ed Merks:

 
Christian,
 
The http://download.eclipse.org/eclipse/updates/4.20-I-builds repos
has such IUs but the train repo
http://download.eclipse.org/releases/2021-06/202104161000 does not.
 
Which repos are available during the resolution?
 
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] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-16 Thread Sravan K Lakkimsetti
Hi Ed,

 

Here is the process we follow,

 

There are two steps in promotion. 

1.  Promote build to downloads pages. To serve users who want to download.
2.  Add to I-builds composite repository

 

When we find problems with build we mark a build as unstable. This removes 
offending build from I-builds composite repository. This enables end users to 
use a good build for upgrade process. These broken builds stay for a week on 
the download page and after they are automatically removed. This process is 
there for developers to analyse problems.

 

Due to this process whenever downstream projects point to I-builds composite 
most often they’ll see a good build. We also mark a build unstable if we find 
any problems during the build process itself. 

 

Because of above mentioned process Tycho will not pull a bad build in maximum 
cases.

 

Hope this explanation helps

 

Thanks

Sravan

 

From: Ed Willink  
Sent: 16 April 2021 12:36
To: cross-project-issues-dev@eclipse.org
Subject: [EXTERNAL] Re: [cross-project-issues-dev] SWT win32 Broken in Latest 
4.20 IBuild?

 

Hi

There is something much stranger gong on.

I ran an early OCL build that would have run on Sunday. It has SWT usage but 
the build runs fine, because it used 

https://download.eclipse.org/eclipse/updates/4.20-I-builds/I20210413-1400 
<https://download.eclipse.org/eclipse/updates/4.20-I-builds/I20210413-1400/plugins/>
 

although that is the earliest of the 3 listed in the compositeArtifacts.jar. If 
it had used the more recent then the problem might have shown up.

?? Why did Tycho fail to pull in the broken build ??

http://download.eclipse.org/eclipse/downloads/drops4/I20210413-1400/ has 63 
test fails which is rather disturbing.

http://download.eclipse.org/eclipse/downloads/drops4/I20210415-0010/, which is 
not marked as unstable, has 7057 fails.

Surely such a high number of fails should be a private matter to be resolved by 
the platform committers with no more trouble to the community as a whole than 
perhaps a polite message to cross-project-dev announcing the lack of build 
promotions while a problem is investigated.

Why does http://download.eclipse.org/eclipse/downloads/ show unstable builds? 
Surely these too should not have been promoted to waste disc space / confuse 
the community?

Why do any builds have any fails at all? Surely a test that fails is a test 
that fails? In my code, if a test is proving problematic then I raise a 
Bugzilla and comment out the test until a solution is found.

Regards

Ed Willink

 

 

On 16/04/2021 07:45, Niraj Modi wrote:

Hi All,

We learned that Windows Signing service is down/broken:
http://build.eclipse.org:31338/winsign.php

 

Raised a blocker below bug with Eclipse foundation:

 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=572896> Bug 572896 - Windows 
Signing service is down or link broken 

 

Regards,

Niraj Modi

- Original message -
From: Sravan K Lakkimsetti/India/IBM
To: "Cross project issues"  <mailto:cross-project-issues-dev@eclipse.org> 
, Niraj Modi/India/IBM@IBM
Cc:
Subject: RE: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest 
4.20 IBuild?
Date: Fri, Apr 16, 2021 11:46 AM
 
Found the faulty commit 
https://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=a26b79c959e884b3a3a96ce2e2cbf0b6ef9e6d23

Need to investigate why this happened.

@Niraj Modi
Can you please help?

Thanks
Sravan

-Original Message-
From: Ed Merks  <mailto:ed.me...@gmail.com>  
Sent: 16 April 2021 11:18
To: Cross project issues  <mailto:cross-project-issues-dev@eclipse.org> 

Subject: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 
IBuild?

Hi,

I updated my target platform from
http://download.eclipse.org/eclipse/updates/4.20-I-builds and after that I 
could not run any SWT applications anymore:

java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:

  
D:\Users\merks\oomph-1.21\ws\.metadata\.plugins\org.eclipse.pde.core\IDE\org.eclipse.osgi\480\0\.cp\swt-win32-4944r16.dll:
 %1 is not a valid Win32 application
 no swt-win32 in java.library.path: [C:\Program 
Files\Java\jdk-11.0.9\bin,]
 D:\Users\merks\.swt\lib\win32\x86_64\swt-win32-4944r16.dll: %1 is not a 
valid Win32 application
 Can't load library: D:\Users\merks\.swt\lib\win32\x86_64\swt-win32.dll
 D:\Users\merks\.swt\lib\win32\x86_64\swt-win32-4944r16.dll: %1 is not a 
valid Win32 application

Using http://download.eclipse.org/releases/2021-06/202104161000 instead works 
fine, so it seems to be something that's happened between M1 and today.

Has anyone else noticed this?  For those who "eat our own dog food", such a 
problem could cripple your IDE if you update the IDE itself...

Regards,
Ed


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto:cross-project-issue

Re: [cross-project-issues-dev] SWT win32 Broken in Latest 4.20 IBuild?

2021-04-15 Thread Sravan K Lakkimsetti


Found the faulty commit
https://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=a26b79c959e884b3a3a96ce2e2cbf0b6ef9e6d23


Need to investigate why this happened.

@Niraj Modi
Can you please help?

Thanks
Sravan

-Original Message-
From: Ed Merks 
Sent: 16 April 2021 11:18
To: Cross project issues 
Subject: [EXTERNAL] [cross-project-issues-dev] SWT win32 Broken in Latest
4.20 IBuild?

Hi,

I updated my target platform from
http://download.eclipse.org/eclipse/updates/4.20-I-builds and after that I
could not run any SWT applications anymore:

java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:

  D:\Users\merks\oomph-1.21\ws\.metadata\.plugins\org.eclipse.pde.core\IDE
\org.eclipse.osgi\480\0\.cp\swt-win32-4944r16.dll: %1 is not a valid Win32
application
 no swt-win32 in java.library.path: [C:\Program Files\Java\jdk-11.0.9
\bin,]
 D:\Users\merks\.swt\lib\win32\x86_64\swt-win32-4944r16.dll: %1 is not
a valid Win32 application
 Can't load library: D:\Users\merks\.swt\lib\win32\x86_64\swt-win32.dll
 D:\Users\merks\.swt\lib\win32\x86_64\swt-win32-4944r16.dll: %1 is not
a valid Win32 application

Using http://download.eclipse.org/releases/2021-06/202104161000 instead
works fine, so it seems to be something that's happened between M1 and
today.

Has anyone else noticed this?  For those who "eat our own dog food", such a
problem could cripple your IDE if you update the IDE itself...

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
___
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] Problem with SimRel Validation Builds

2020-12-05 Thread Sravan K Lakkimsetti
Looks like Fred is migrating Simrel project to JIRO. Please ignore ci-staging 
path. This patch did not put a -1 on the gerrit patch for me yesterday. 

 

Thanks

Sravan

 

From: Ed Merks  
Sent: 06 December 2020 11:13
To: Cross project issues 
Subject: [EXTERNAL] [cross-project-issues-dev] Problem with SimRel Validation 
Builds

 

Hi, SimRel validation builds like this are failing:...  







This Message Is From an External Sender 


This message came from outside your organization. 

Hi,

SimRel validation builds like this are failing:

https://ci-staging.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/1904/console

I think this is the problem:

06:24:12 No JDK named ‘jdk11-latest’ found

Then it uses Java 8:

06:24:24 Java version: 1.8.0_262, vendor: Eclipse OpenJ9, runtime: 
/opt/java/openjdk/jre

But Java 8 doesn't work:

06:24:40 Caused by: java.lang.UnsupportedClassVersionError: JVMCFRE003 bad 
major version; class=org/eclipse/tycho/extras/eclipserun/EclipseRunMojo, 
offset=6

How did JDK 11 disappear and how do we get it back?

I opened the following:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=569506

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


[cross-project-issues-dev] Removal of market place entries for java 14, java 12 support

2020-09-15 Thread Sravan K Lakkimsetti
Hi,

 

The following entries from market place entries will be removed at the end
of this month(Sep 30)

 

1.
 Java 12 Support for Eclipse 2019-03 (4.11) - This feature is included
in Eclipse 4.12 and above
2.
 Java 14 Support for Eclipse 2020-03 (4.15) - This feature is included
in Eclipse 4.12 and above

 

Please use latest version of Eclipse for the above features.

 

Thanks

Sravan


___
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] Disabled CFT contribution in simrel

2020-08-20 Thread Sravan K Lakkimsetti
Hi,

 

CFT has a conflict with JDT debug version contributed by platform. Because
of this I had to disable CFT temporarily. Please enable it again once the
dependencies are corrected.

 

Thanks

Sravan


___
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] Webtools p2 repository broken

2020-03-18 Thread Sravan K Lakkimsetti
Hi,

 

We use this to create and publish eclipse platform’s webpages. 

 

Thanks

Sravan

 

From: Nick Boldt  
Sent: 19 March 2020 03:45
To: Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] Webtools p2 repository broken

 

https://download.eclipse.org/webtools/repository/releng/  fixed. 

 

Sorry about that -- I blame the COVID quarantine for these typos. :D

 

Also great to know people are still using that site. I was kind of wondering if 
we were building useless crap. :)

 

 

 

On Wed, Mar 18, 2020 at 5:44 PM Thomas Wolf mailto:thomas.w...@paranor.ch> > wrote:

https://download.eclipse.org/webtools/repository/releng/compositeContent.xml is 
broken and contains a non-existing child.

https://download.eclipse.org/webtools/downloads/drops/R3.16.0/R-3.17.0-20200306035042/repositoryunittests/
 does not exist.

Same problem in compositeArtifacts.xml.

This breaks builds. Please fix.

Cheers,

  Thomas
___
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




 

-- 

Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

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
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] [platform-releng-dev] No SDK build I20200207-1800, gerrit/jenkins login issues etc

2020-02-09 Thread Sravan K Lakkimsetti
I am having same issues. Unable to login to Jenkins/gerrit

 

From: Ralf Heydenreich  
Sent: 08 February 2020 14:46
To: cross-project-issues-dev@eclipse.org
Subject: [EXTERNAL] Re: [cross-project-issues-dev] [platform-releng-dev] No SDK 
build I20200207-1800, gerrit/jenkins login issues etc

 

Hi all,

currently I can't push to Gerrit and can't login via Web Interface. Login to 
bugs.eclipse.org is possible.

 

Cheers,

Ralf.

 

Am 08.02.2020 um 09:44 schrieb Daniel Megert:

For me log into Gerrit and Jenkins works.

The build did not get published (yet).

Dani



From:Andrey Loskutov   
To:"Eclipse platform release engineering list."  
 , 
webmas...@eclipse.org  , 
cross-project-issues-dev@eclipse.org 
 
Date:08.02.2020 09:02
Subject:[EXTERNAL] [platform-releng-dev] No SDK build I20200207-1800,   
 gerrit/jenkins login issues etc
Sent by:platform-releng-dev-boun...@eclipse.org 
 

  _  




Hi all,

I miss SDK build results for I20200207-1800.

Also I see that lot of other infrastructure seem to be not working, I've
opened   
https://bugs.eclipse.org/bugs/show_bug.cgi?id=559938.

Interestingly   
https://accounts.eclipse.org/committertools/infra-status
doesn't show me anything special that I could understand as a root cause.

--
Kind regards,
Andrey Loskutov

 


___
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 end of an era: shell access.

2019-07-07 Thread Sravan K Lakkimsetti
Hi,

 

I do share Ed and Markus’ opinion. There are many tasks I do with shell access. 
Restricting will cause losing flexibility to do these jobs. I will have to do 
these in circuitous(very inefficient) way. I would be very unhappy with these 
restrictions.

 

Thanks

Sravan

 

From: Markus Knauer  
Sent: Friday, July 05, 2019 2:39 PM
To: Cross project issues 
Subject: [EXTERNAL] Re: [cross-project-issues-dev] The end of an era: shell 
access.

 

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 mailto:ed.me...@gmail.com> > 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 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] Disabling Wild Web Developer project

2019-06-09 Thread Sravan K Lakkimsetti
Hi,

 

Wild Web Develiper project's contribution is causing build failures in
Simrel(it is using snapshot repo and there is a mismatch in the expected
versions). I am disabling the project for now. Please reenable this
project after updating the version numbers.

 

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

 


___
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] Please enable simrel aggregation gerrit jobs

2019-06-02 Thread Sravan K Lakkimsetti
Hi,

 

Simrel aggregation gerrit validation jobs are disabled. Can you please
enable them We would like to contribute to RC1. We already created a
gerrit patch https://git.eclipse.org/r/#/c/143105/ we are waiting for
verified +1 from the gerrit job.

 

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

 


___
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] Is SimRel final for M7?

2018-05-14 Thread Sravan K Lakkimsetti
That’s not possible now but we can still contribute to RC1, which is end of 
this week

 

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: Wim Jongman [mailto:wim.jong...@gmail.com] 
Sent: Tuesday, May 15, 2018 11:25 AM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] Is SimRel final for M7?

 

Hi,

 

Yes, Tips is part of Platform. Is there a way to update only the Tip of the Day 
version in the M7 SimRel repo? No other bundles or features depend on it.

 

Cheers,

 

Wim

 

On Mon, May 14, 2018 at 5:55 PM, Mikaël Barbero 
mailto:mikael.barb...@eclipse-foundation.org> > wrote:

Staging will be complete on Wed night as Nick said. However, tip of the day is 
(IIRC) part of Eclipse platform and their contribution is already done as +0 
deadline is on Friday.

 

Cheers,


--

Mikaël Barbero - Eclipse Foundation

IT Services - Release Engineering

📱 (+33) 642 028 039

📧 mikael.barb...@eclipse-foundation.org 
 

🐦 @mikbarbero





Le 14 mai 2018 à 17:21, Nick Boldt mailto:nbo...@redhat.com> > a écrit :

 

I imagine there will be several more respins since it's only +1 day today. 

 

Last build is likely Wed night / Thurs morning, per the Photon calendar. 

 

https://calendar.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9t...@group.calendar.google.com
 

 

 

On Mon, May 14, 2018 at 11:06 AM, Wim Jongman mailto:wim.jong...@gmail.com> > wrote:

Hi,

 

Is there going to be another SimRel build? I would like to update it with the 
latest Tip of the Day feature version.

 

Cheers,

 

Wim


___
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

Senior 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
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] Heads Up: Simrel issues with Jetty 9.4.10 for Photon M7

2018-05-10 Thread Sravan K Lakkimsetti
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()
ADDEDorg.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
REMOVEDorg.eclipse.jetty.server.Request#__MULTIPART_INPUT_STREAM
REMOVED
org.eclipse.jetty.server.session.AbstractSessionCache$PlaceHolderSession#PlaceHolderSession(AbstractSessionCache,
 SessionData)
ADDED
org.eclipse.jetty.server.session.AbstractSessionCache$PlaceHolderSession#PlaceHolderSession(AbstractSessionCache,
 SessionHandler, SessionData)
ADDEDorg.eclipse.jetty.server.session.FileSessionDataStore#_contextString
CHANGED
org.eclipse.jetty.server.session.FileSessionDataStore#_deleteUnrestorableFiles
ADDEDorg.eclipse.jetty.server.session.FileSessionDataStore#_lastSweepTime
AD

[cross-project-issues-dev] Announcing delay in Eclipse and equinox contribution to 4.7.3a RC1

2018-03-23 Thread Sravan K Lakkimsetti
Hi,

 

We found couple of major problems while testing platform. These problems
have been fixed and a new build is currently underway. 

 

In this regard, we will be contributing to 4.7.3a RC1 on simrel tomorrow.
There is going to 1 day delay

 

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

 


___
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 branch for 4.7.3a

2018-03-23 Thread Sravan K Lakkimsetti


Thanks Fred for the information. I will add eclipse and equinox
contribution tomorrow

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

-Original Message-
From: Frederic Gurr [mailto:frederic.g...@eclipse-foundation.org]
Sent: Friday, March 23, 2018 7:19 PM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Simrel branch for 4.7.3a

Hi Sravan,

I've created a branch for Oxygen.3a called:

=> Oxygen.3a_JDK10

Regards,

Fred


--
Frederic Gurr

Release Engineer
Eclipse Foundation


On 23.03.2018 11:40, Sravan K Lakkimsetti wrote:
> Hi,
>
>
>
> Do we have a separate branch for 4.7.3a or use Oxygen_update branch
>
>
>
> 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
>
>
>
>
>
>
> ___
> 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__dev.eclipse.org_m
> ailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwIF-g&c=jf_iaSHvJObT
> bx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=RB6m1XVbtTD
> YfkDOkFZVDPkrWNraGUJaKMsRM-bSTqo&s=Rhyu3-S0vypSKn3vqYVbttBi5hRrD3IV93K
> EtsZBS5w&e=
>
___
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__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwIF-g&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=RB6m1XVbtTDYfkDOkFZVDPkrWNraGUJaKMsRM-bSTqo&s=Rhyu3-S0vypSKn3vqYVbttBi5hRrD3IV93KEtsZBS5w&e=


___
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] Simrel branch for 4.7.3a

2018-03-23 Thread Sravan K Lakkimsetti
Hi,

 

Do we have a separate branch for 4.7.3a or use Oxygen_update branch

 

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

 


___
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] 4.7.3 Eclipse and Equinox contribution for Simrel (jetty upgrade)

2018-03-02 Thread Sravan K Lakkimsetti
Hi,

 

I already sent this message to project contacts individually. I am forwarding 
this to Cross Project for wider audience.

 

Platform had to upgrade Jetty to 9.4.8 in RC4 (see  
 Bug 531803 - Update 
Jetty to 9.4.8 for details). This caused problems with the following projects 
while doing contribution to simrel

 

1.  Java Workflow Tooling
2.  m2e-wtp
3.  RAP Tools
4.  Scout
5.  SOA-BPEL
6.  WebTools

 

I have disabled the above projects for now. Please adjust the version ranges 
for jetty and re-enable.

 

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

 


___
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] Issues with windows7tests slave on Shared JIPP

2018-02-21 Thread Sravan K Lakkimsetti


Hi Fred,

We have issue with Mac machine also. The Xvnc utility is not getting
invoked anymore. Raised Bug 531436 - Xvnc failure on shared hipp

Thanks
Sravan

-Original Message-
From: Frederic Gurr [mailto:frederic.g...@eclipse-foundation.org]
Sent: Wednesday, February 21, 2018 4:14 AM
To: Cross project issues 
Subject: [cross-project-issues-dev] Issues with windows7tests slave on
Shared JIPP

Hi,

After migrating the Shared Hudson instance
(https://urldefense.proofpoint.com/v2/url?u=https-3A__ci.eclipse.org_shared&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=bAp6atU0ZyHeDA8S8oonh72YTE2PIGToLDQD0mROSRA&s=7suQTRu4LFxcyD5OqQG0qQ05r3nilc8YDWi4sayGtkc&e=)
 to Jenkins we are facing some connection problems between the
windows7tests slave and the Shared JIPP (master).

Therefore the windows7tests slave is currently offline.
We will continue to investigate.


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://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=bAp6atU0ZyHeDA8S8oonh72YTE2PIGToLDQD0mROSRA&s=0pUnrWJcGUZVFRo2GTvx0iBr8Nrbs2-DXda7At3vi0k&e=


___
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] HIPP2JIPP migration and cascaded jobs

2018-02-07 Thread Sravan K Lakkimsetti


Hi,

I have converted the jobs on shared hipp to freestyle.

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

-Original Message-
From: Frederic Gurr [mailto:frederic.g...@eclipse-foundation.org]
Sent: Wednesday, February 07, 2018 11:33 PM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] HIPP2JIPP migration and cascaded
jobs

Hi,

Unfortunately some projects still use cascaded jobs:

- shared
 - ep-unit-lin64
 - ep-unit-mac64
 - ep-unit-win32
 - ep47U-unit-win32
 - ep47Y-unit-lin64
 - ep47Y-unit-mac64
 - ep47Y-unit-win32
 - ep48I-unit-mac64
 - ep48I-unit-win32
 - ep47M-unit-mac64
 - ep47M-unit-win32
 - ep47U-unit-mac64

- virgo
 - virgo.documentation.snapshot
 - virgo.ide.snapshot
 - virgo.kernel-tools.snapshot
 - virgo.kernel.3.6.snapshot
 - virgo.packaging.3.6.snapshot
 - virgo.samples.snapshot
 - virgo.util.3.6.snapshot
 - virgo.web.3.6.snapshot

Please convert them to freestyle jobs immediately to not cause any delays
in the Hudson to Jenkins migration.

Regards,

Fred


On 17.01.2018 13:46, Frederic Gurr wrote:
> Hi,
>
> Since Jenkins does not support cascaded jobs, such jobs need to be
> converted to normal freestyle jobs before a HIPP2JIPP migration.
>
> A scan found the following projects that use cascaded jobs:
>
> - diffmerge
> - virgo
> - mpc
> - triquetrum
> - tinydtls
> - emfcompare
> - mylyn
> - shared
>
> If your project is on this list, please convert any cascaded job to a
> normal freestyle job by copying all configuration settings from the
> parent job.
>
>
> Please let me know, if you have any concerns or questions.
>
>
> 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://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=PXIculuLUirUXkALItvK_ubMt4GXSP2fGr5tLC6LE4o&s=0uQZO-OX-SpGfAc7zsrgClS4tCuODM2IxhxL32MEp30&e=


___
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] Removal of CVS from SDK bundle

2017-11-30 Thread Sravan K Lakkimsetti
Hi,

 

>From Photon M4 we are dropping CVS bundle from SDK product. Refer Bug
  359466 - Remove
CVS from Eclipse SDK feature

 

CVS bundle is part of build repository. And it can be installed using
"Install new software" option from eclipse.

 

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

 


___
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-dev] Respin of M3

2017-10-30 Thread Sravan K Lakkimsetti
Started Respin at 4:00 AM Eastern time. Should be available in couple of hours

 

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: Niraj Modi [mailto:niraj.m...@in.ibm.com] 
Sent: Monday, October 30, 2017 12:46 PM
To: Eclipse platform release engineering list. 
Cc: eclipse-dev-boun...@eclipse.org; Cross project issues 
(cross-project-issues-dev@eclipse.org) ; 
General development mailing list of the Eclipse project. 

Subject: Re: [eclipse-dev] Respin of M3

 

Hi Releng,
We have reverted the problematic fix for  

 https://bugs.eclipse.org/518737, request a respin of Photon M3 build.

Regards,
Niraj Modi


From:"Daniel Megert" mailto:daniel_meg...@ch.ibm.com> >
To:"Cross project issues (cross-project-issues-dev@eclipse.org 
 )" 
mailto:cross-project-issues-dev@eclipse.org> >, "General development mailing 
list ofthe Eclipse project." mailto:eclipse-...@eclipse.org> >
Date:10/29/2017 03:20 PM
Subject:[eclipse-dev] Respin of M3
Sent by:eclipse-dev-boun...@eclipse.org 
 

  _  




The Platform will most likely respin M3 tomorrow.

The change for  

 https://bugs.eclipse.org/518737reveals  

 https://bugs.eclipse.org/511355in the IDE. Together with the bad color, it 
also removes the row lines of the column.

Dani___
eclipse-dev mailing list
eclipse-...@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__dev.eclipse.org_mailman_listinfo_eclipse-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=_TZ5U2NJh9lXkaj4_qKbwIbEVB6nLCFcKlW-Qi4EQTE&m=Tgy0KJ_cqzCFZtvhTvl7jnZVClFXRmX4uDpMKgcfalQ&s=nZplD00vT9HE-c46qgFXvwEX4T813xPlTe3B7RZzZGY&e=




___
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] Spam bugs on all platform projects

2017-09-25 Thread Sravan K Lakkimsetti
Hi,

 

We are getting SPAM bugs from ma...@watchmtv.co 
on all platform projects. Please disable this ID. 

 

Thanks

Sravan


___
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] download.eclipse.org down?

2017-08-22 Thread Sravan K Lakkimsetti
Hi,

 

Thanks David. I raised a Bug 
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=521284>  521284 - 
Download.eclipse.org is down to address this

 

Thanks

Sravan

 

From: David Williams [mailto:david_willi...@acm.org] 
Sent: Wednesday, August 23, 2017 9:36 AM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] download.eclipse.org down?

 

On 08/22/2017 11:47 PM, Sravan K Lakkimsetti wrote:

Hi,

 

Download.eclipse.org is down for me. Any one facing this issue?

 

Thanks

Sravan

Down for me too. 
And, down for Down For Everyone Or Just Me 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__downforeveryoneorjustme.com_&d=DwMFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=MzOAfieCZiarMtI7jsLHDckyedulbdl4lc0mq7_4t0Y&s=yAb1zFCdwNi2Oct1dHL3fnbJcnA0iiw9_S70tdu6pDs&e=>
  as well.

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 
<mailto: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__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_cross-2Dproject-2Dissues-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=MzOAfieCZiarMtI7jsLHDckyedulbdl4lc0mq7_4t0Y&s=mzFH6Wul8dObISSmiBiKY2yVCfnptvedH-8SFj16Oxw&e>
 
&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=BbJ1i82pNJnkXoEbqK7sZDkJsrJ7wkY_no7y0H4rMzE&m=MzOAfieCZiarMtI7jsLHDckyedulbdl4lc0mq7_4t0Y&s=mzFH6Wul8dObISSmiBiKY2yVCfnptvedH-8SFj16Oxw&e=
 

 


___
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] download.eclipse.org down?

2017-08-22 Thread Sravan K Lakkimsetti
Hi,

 

Download.eclipse.org is down for me. Any one facing this issue?

 

Thanks

Sravan


___
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] Download.eclipse.org is down Bug 515596

2017-07-26 Thread Sravan K Lakkimsetti

Hi,

We are not able to reach download.eclipse.org websites today. Can you
please have a look?

ref: https://bugs.eclipse.org/bugs/show_bug.cgi?id=515596

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
___
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?

2017-03-14 Thread Sravan K Lakkimsetti
Hi,

 

Thanks Arthur for clarification

 

Thanks

Sravan

 

From: Arthur van Dorp [mailto:arthur.vand...@bsi-software.com] 
Sent: Tuesday, March 14, 2017 7:13 PM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] Severe regression in PDT Neon.3 RC4 - 
chance for a respin?

 

Hi,

 

The change is in 
http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/?h=Neon.3_respin.

 

Regards,

Arthur

 

Von: cross-project-issues-dev-boun...@eclipse.org 
<mailto:cross-project-issues-dev-boun...@eclipse.org>  
[mailto:cross-project-issues-dev-boun...@eclipse.org] Im Auftrag von Sravan K 
Lakkimsetti
Gesendet: Dienstag, 14. März 2017 14:39
An: Cross project issues
Betreff: Re: [cross-project-issues-dev] Severe regression in PDT Neon.3 RC4 - 
chance for a respin?

 

Hi,

I don't see any contribution here  
<http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/?h=Neon_maintenance>
 
http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/?h=Neon_maintenance.
 Is this merged to simrel repo?

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

Frederic Gurr ---14-03-2017 06:08:14 PM---Hi, Respin is in progress.

From: Frederic Gurr mailto:frederic.g...@eclipse.org> >
To: cross-project-issues-dev@eclipse.org 
<mailto:cross-project-issues-dev@eclipse.org> 
Date: 14-03-17 06:08 PM
Subject: Re: [cross-project-issues-dev] Severe regression in PDT Neon.3 RC4 - 
chance for a respin?
Sent by: cross-project-issues-dev-boun...@eclipse.org 
<mailto:cross-project-issues-dev-boun...@eclipse.org> 

  _  




Hi,

Respin is in progress.

Regards,

Fred

On 14.03.2017 10:53, Markus Knauer wrote:
> Any status updates and progress on this issue?
> 
> Thanks,
> Markus
> 
> On 13 March 2017 at 19:57, Kaloyan Raev  <mailto:kaloya...@zend.com%0b> 
> <mailto:kaloya...@zend.com>> 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
> <http://download.eclipse.org/tools/pdt/updates/4.3-rc5>
> [2] https://git.eclipse.org/r/#/c/92967/
> <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 <http://www.roguewave.com>  <http://www.roguewave.com> /
> kaloyan.r...@roguewave.com <mailto:kaloyan.r...@roguewave.com>  
> <mailto: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
>>> <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 663
>>> www.roguewave.com <http://www.roguewave.com>  
>>> <http://www.roguewave.com> <http://www.r

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

2017-03-14 Thread Sravan K Lakkimsetti

Hi,

I don't see any contribution here
http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/?h=Neon_maintenance
. Is this merged to simrel repo?

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:   Frederic Gurr 
To: cross-project-issues-dev@eclipse.org
Date:   14-03-17 06:08 PM
Subject:Re: [cross-project-issues-dev] Severe regression in PDT Neon.3
RC4 - chance for a respin?
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi,

Respin is in progress.

Regards,

Fred

On 14.03.2017 10:53, Markus Knauer wrote:
> 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 663
>>> www.roguewave.com  <
http://www.roguewave.com>  /
kaloyan.r...@roguewave.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-issu

Re: [cross-project-issues-dev] Fwd: Simrel repo contributions

2017-01-19 Thread Sravan K Lakkimsetti
Hi David,

 

The problem arose from the fact that one of the project’s URL stayed at RC 
level which was removed at end of release. So we did not had access to the URL. 
In this case the build was failing. Once that team updated the URL the problem 
got resolved.

 

So these are my conclusions:

1.  We build with the content available in simrel repo. At RC4 it will be 
last RC URLs. These will contain final content(if there is a bug discovered we 
will have RC4a for that component)
2.  The content for final release and last RC would be same. So from build 
point of view there would be no change in the build content if we build with 
release URLs or last RC URLs. 
3.  It is project’s responsibility to update the URLs at the time release 
with release URLs. If not there is a fair chance that build may fail(as some of 
the URLs may not be available) at the next checkpoint
4.  There are two ways we can fix 

a.  Ask the project team to update. (Preferred)
b.  Disable the project (use it as last resort)

 

Please correct me if I am wrong

 

Thanks

Sravan

 

 

 

From: David Williams [mailto:david_willi...@acm.org] 
Sent: Friday, January 20, 2017 12:37 AM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] Fwd: Simrel repo contributions

 

I will answer to "cross-project" list, since may be of general interest.

And before answering the question, I will remind everyone the purpose of the 
"checkpoint build 
<https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Checkpoint_deliverable>
 " was primarily to allow any new projects, or projects with new features, to 
"get into" the build, on a  relatively stable base. Unlike "RC builds" not all 
projects would be expected to update their contributions for mere bug fixes. I 
also noticed that this is stated in the Neon Plan 
<https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan> , but not the Oxygen 
plan <https://wiki.eclipse.org/Oxygen/Simultaneous_Release_Plan>  so ... 
someone ... should update the Oxygen plan as well (assuming the Planning 
Council still wants to provide that checkpoint, for Oxygen update releases). 

I am assuming that the original issue or question revolved around someone's URL 
in the aggrcon file was not literally the "final release" one, in the sense 
that repositories are normally moved or copied to their final location during 
quiet week, and then the project must remember to also update their URLs in the 
aggrcon file. 

If that is the issue, then I'll make the following comments: 

a. What you say is true, project decides "the release" URL. BUT the "right 
content" is a little stronger than you say. It should be exactly the same. Not 
simply "fit in". 
b. We (or, I) never hounded projects much to update their URLs to their final 
ones, because every year a few would not and unless everyone does it, it really 
does not make the build "reproducible" so I thought it not worth the hounding. 
c. I did, however, set the 'validate' job (on both branches) to not only run 
upon git repo changes, but also to run once every Monday morning, to help spot 
"broken URLs". [I did not write much about these triggering events, so just now 
added it to the Simrel release engineering 
<https://wiki.eclipse.org/SimRel/Simultaneous_Release_Engineering#Hudson_Jobs>  
wiki.]

If that is not the issue, then I will need more specific questions, or 
symptoms. It appears all the URL stuff was fixed 5 days ago, so if it is still 
an issue, then I suspect something else is wrong. 

HTH





On 01/19/2017 12:40 PM, Frederic Gurr wrote:

Hi David,
 
Can you help me with Sravan's questions?
I assume that every project is responsible to put in the right URLs for
a release. SimRel in general does not care if something is a "release"
URL, as long as the right content (whatever a project considers to be
right and what does not cause dependency issues) is available, right?
 
 
Regards,
 
Fred
 
 Forwarded Message 
Subject:  Simrel repo contributions
Date:Mon, 16 Jan 2017 07:51:06 +
From:Sravan K Lakkimsetti  <mailto:sravankum...@in.ibm.com> 

To:  frederic.g...@eclipse.org <mailto:frederic.g...@eclipse.org> 
CC:  Daniel Megert  <mailto:daniel_meg...@ch.ibm.com> 

 
 
 
Hi Fred,
 
 
I was trying to update simrel with latest 4.6.3 M-Build for 4.6.3 check
point. I noticed an issue with Sirius project. This raised following
questions in my mind relating to 4.6.2
 
 
 1. Did we build 4.6.2 with right repos?
 2. When do we do build with release urls?
 3. If we did build with wrong repo urls, how to rectify that?
 4. How can we catch this situation in future.
 
 
It may turn out to be non-issue. But would like to have clarification.
 
 
Thanks and Regards,
 
Sravan
 
 
Sravan Kum

Re: [cross-project-issues-dev] Repo.eclipse.org not reachable

2016-12-20 Thread Sravan K Lakkimsetti

The issue is tracked in Bug 508658 - repo.eclipse.org is down
https://bugs.eclipse.org/bugs/show_bug.cgi?id=508658

-Sravan

-Original Message-
From: Aleksandar Kurtakov [mailto:akurt...@redhat.com]
Sent: Tuesday, December 20, 2016 3:54 PM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] Repo.eclipse.org not reachable



- Original Message -
> From: "Frederic Gurr" 
> To: cross-project-issues-dev@eclipse.org
> Sent: Tuesday, 20 December, 2016 12:17:04 PM
> Subject: Re: [cross-project-issues-dev] Repo.eclipse.org not reachable
>
> Nexus is back up again.

Fred, please explain what is going on. This on/off game is too toxic for
everyone.

>
> Regards,
>
> Fred
>
> On 20.12.2016 02:21, Pascal Rapicault wrote:
> > From the EGerrit Hudson server (hipp4), repo.eclipse.org is not
reachable.
> > Is that a known issue?
> >
> > 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
>

--
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

Re: [cross-project-issues-dev] Repo.eclipse.org not reachable

2016-12-19 Thread Sravan K Lakkimsetti

It went down again today around 8:00PM EDT. Reopened Bug 508658 -
repo.eclipse.org is down to track this.

-Sravan


-Original Message-
From: Pascal Rapicault [mailto:pas...@rapicorp.com]
Sent: Tuesday, December 20, 2016 6:52 AM
To: Cross project issues 
Subject: [cross-project-issues-dev] Repo.eclipse.org not reachable

 From the EGerrit Hudson server (hipp4), repo.eclipse.org is not reachable.
Is that a known issue?

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] repo.eclipse.org seems down

2016-12-07 Thread Sravan K Lakkimsetti
Repo.eclipse.org has been restarted. Please try again

 

From: LE MENEZ Quentin [mailto:quentin.leme...@cea.fr] 
Sent: Wednesday, December 07, 2016 3:28 PM
To: Cross project issues 
Subject: [cross-project-issues-dev] repo.eclipse.org seems down

 

Hi,

I can’t seem to access it from our Hudson instance and it keeps failing our job 
(e.g. https://hudson.eclipse.org/papyrus/job/Papyrus-Gerrit/9511/console). When 
I asked http://downforeveryoneorjustme.com/repo.eclipse.org it told me that it 
wasn’t only down for me. Trying to build locally gets me a lot of timed out 
connections too (INFO: I/O exception (java.net.SocketException) caught when 
processing request to {s}->https://repo.eclipse.org:443: Connection reset).

 

Am I missing something on our end and am I the only one seeing this?

 

Thanks,

Quentin

 


___
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] FW: Moving away from N-builds

2016-11-10 Thread Sravan K Lakkimsetti
I am forwarding this mail again. I have no clue why it did not reach 
cross-project-issues mailing list first time

 

From: Sravan K Lakkimsetti [mailto:sravankum...@in.ibm.com] 
Sent: Wednesday, November 09, 2016 7:33 PM
To: platform-releng-...@eclipse.org; eclipse-...@eclipse.org; 'Cross project 
issues' 
Subject: Moving away from N-builds

 

Hi,

 

We will be stopping N-builds from today and there will not be any more 
N-builds. The repos will not populated any more. And the builds will also get 
removed from downloads in coming days

 

We will have I-builds daily at 8 PM Eastern Standard time. 

 

Every week Monday’s build will be retained for the period of milestone and last 
7 days builds will be retained. Remaining builds will be dropped from the 
downloads.

There is no change in the retention policy of update repository (only last 4 
builds will be available).

 

In case of broken build(due to some important test failures) please notify 
releng team using platform-releng-dev mailing list. We will do the needful like 
removing from update sites etc

 

For more information please refer to Bug 
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=507272>  507272 - Move away from 
daily N-builds and start with daily I-builds

 

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

 


___
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] Moving away from N-builds

2016-11-10 Thread Sravan K Lakkimsetti
Hi,

 

We will be stopping N-builds from today and there will not be any more 
N-builds. The repos will not populated any more. And the builds will also get 
removed from downloads in coming days

 

We will have I-builds daily at 8 PM Eastern Standard time. 

 

Every week Monday’s build will be retained for the period of milestone and last 
7 days builds will be retained. Remaining builds will be dropped from the 
downloads.

There is no change in the retention policy of update repository (only last 4 
builds will be available).

 

In case of broken build(due to some important test failures) please notify 
releng team using platform-releng-dev mailing list. We will do the needful like 
removing from update sites etc

 

For more information please refer to Bug 
  507272 - Move away from 
daily N-builds and start with daily I-builds

 

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

 


___
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] repo.eclipse.org down?

2016-10-24 Thread Sravan K Lakkimsetti
I doing a rebuild at 4:10AM

 

From: Sravan K Lakkimsetti [mailto:sravankum...@in.ibm.com] 
Sent: Monday, October 24, 2016 12:37 PM
To: 'Cross project issues' 
Cc: platform-releng-...@eclipse.org
Subject: Re: [platform-releng-dev] [cross-project-issues-dev] repo.eclipse.org 
down?

 

Yes I am seeing this issue. Yesterday’s I build failed due to this issue. A bug 
has been raised Bug <https://bugs.eclipse.org/bugs/show_bug.cgi?id=506402>  
506402 - repo.eclipse.org is down

 

 

 

From: "Marc-André Laperle" [mailto:marc-andre.lape...@ericsson.com] 
Sent: Monday, October 24, 2016 11:08 AM
To: cross-project-issues-dev@eclipse.org 
<mailto:cross-project-issues-dev@eclipse.org> 
Subject: [cross-project-issues-dev] repo.eclipse.org down?

 

Hello,

 

My local Maven builds and browser can't access https://repo.eclipse.org 

Is anyone else seeing this?

 

Thank you,

Marc-André

 


___
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] repo.eclipse.org down?

2016-10-24 Thread Sravan K Lakkimsetti
Yes I am seeing this issue. Yesterday’s I build failed due to this issue. A bug 
has been raised Bug   
506402 - repo.eclipse.org is down

 

 

 

From: "Marc-André Laperle" [mailto:marc-andre.lape...@ericsson.com] 
Sent: Monday, October 24, 2016 11:08 AM
To: cross-project-issues-dev@eclipse.org
Subject: [cross-project-issues-dev] repo.eclipse.org down?

 

Hello,

 

My local Maven builds and browser can't access https://repo.eclipse.org 

Is anyone else seeing this?

 

Thank you,

Marc-André


___
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] Who can I ask for releng assistance?

2016-09-26 Thread Sravan K Lakkimsetti

is this the same behavior as
https://bugs.eclipse.org/bugs/show_bug.cgi?id=502121 ? If yes can you try
again. this has been fixed


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:   Stefan Xenos 
To: "Eclipse JDT Core developers list." ,
platform-releng-...@eclipse.org, Cross project issues

Date:   26-09-16 10:06 PM
Subject:[cross-project-issues-dev] Who can I ask for releng assistance?
Sent by:cross-project-issues-dev-boun...@eclipse.org



The latest hudson builds for this patch have been freezing up:

https://git.eclipse.org/r/#/c/76660/

They seem to freeze up after the message "Recording test results". Is there
anyone on the greater Eclipse team who knows how to debug hudson builds?

The tail end of the console logs for the problematic builds always looks
like this:

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time: 01:13 h
[INFO] Finished at: 2016-09-25T22:19:41-04:00
[INFO] Final Memory: 174M/5216M
[INFO]

[DEBUG] Closing connection to remote
[DEBUG] Waiting for process to finish
[DEBUG] Result: 0
Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to
exception
java.lang.InterruptedException
 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:503)
 at hudson.model.Run$Runner$CheckpointSet.waitForCheckPoint
(Run.java:1388)
 at hudson.model.Run.waitForCheckpoint(Run.java:1354)
 at hudson.model.CheckPoint.block(CheckPoint.java:129)
 at hudson.tasks.junit.JUnitResultArchiver.perform
(JUnitResultArchiver.java:162)
 at hudson.tasks.BuildStepMonitor$1.perform
(BuildStepMonitor.java:34)
 at hudson.model.AbstractBuild$AbstractRunner.perform
(AbstractBuild.java:736)
 at hudson.model.AbstractBuild
$AbstractRunner.performAllBuildSteps(AbstractBuild.java:714)
 at hudson.model.AbstractBuild
$AbstractRunner.performAllBuildSteps(AbstractBuild.java:690)
 at hudson.model.Build$RunnerImpl.post2(Build.java:163)
 at hudson.model.AbstractBuild$AbstractRunner.post
(AbstractBuild.java:652)
 at hudson.model.Run.run(Run.java:1519)
 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
 at hudson.model.ResourceController.execute
(ResourceController.java:82)
 at hudson.model.Executor.run(Executor.java:137)
___
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] How to provide HDPI icons in yourplug-in

2016-09-22 Thread Sravan K Lakkimsetti

When I am doing this work. I tried using SVG images instead of PNG images.
The estimated footprint increase is about 70MB. whereas a set of @2x images
increases the footprint by 4MB.

My approach was to load scaled up images at startup based on the scaling
factor and use them through out the platform(as suggested by Stefan). From
this we need a capability of reading SVG files and create image objects.
When we did the research we found GTK(unix) and Cocoa(Mac) has this
capability but not (Windows). On windows we use GDI+ library for graphics
and this does not have this capability. We had to build this capability.
This is where we had performance issues.


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:   David Williams 
To: Cross project issues 
Date:   22-09-16 06:31 AM
Subject:Re: [cross-project-issues-dev] How to provide HDPI icons in
yourplug-in
Sent by:cross-project-issues-dev-boun...@eclipse.org



On 09/21/2016 08:20 PM, Stefan Xenos wrote:
> What I proposed would occur once, so it would slow down *installation*
> time but not startup time. We could show a message along the lines of
> "installing icons" to make it clear to the user what's going on.
>
> Or do you have some reason to believe this would have some impact on
> startup time once the icons are installed?
>

I do not know a definitive answer, but found some hints. At first I was
thinking something similar and did some googling for "svg png
performance" and "does OS cache SVG" and a) did not find much about
icons, per se, but otherwise seemed to be a lot of out-of-date
information that I think is not always currently true ... most of it
browser and webpage focused but (that is, low signal to noise ratio) and
b) also found some bugs in Firefox's system that had titles such as "SVG
cache must be invalidated if System theme changes". That, and even
"scaling" seems like the kind of thing that might effect us. At that
point I decided "this is complicated" and didn't read further. :)
  HTH

___
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 is failing to connect to https://hudson.eclipse.org

2016-08-31 Thread Sravan K Lakkimsetti

I am still having connection issues. I use curl to connect to
hudson.eclipse.org. but I am getting the following error
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current
 Dload  Upload   Total   SpentLeft
Speed

  0 00 00 0  0  0 --:--:--  0:00:58 --:--:--
0
  0 00 00 0  0  0 --:--:--  0:00:59 --:--:--
0
  0 00 00 0  0  0 --:--:--  0:01:00 --:--:--
0
  0 00 00 0  0  0 --:--:--  0:01:00 --:--:--
0
curl: (56) Received HTTP code 503 from proxy after CONNECT


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:   "Webmaster(Matt Ward)" 
To: Cross project issues 
Date:   31-08-16 07:58 PM
Subject:Re: [cross-project-issues-dev] Gerrit is failing to connect to
https://hudson.eclipse.org
Sent by:cross-project-issues-dev-boun...@eclipse.org



Sorry folks this was the result of a missing dns update .  I've fixed
that so things should now be back to normal.

-Matt.

On 08/30/2016 08:28 PM, Jeff Johnston wrote:
> I hit the restart button on the account page and it appeared to bring
down
> the hipp instance as I had to wait a bit for it to come up.  I will try
your
> suggestion, but for the time-being I have cheated and put the launchbar
stuff
> in the Linux Tools download area as a temporary work-around.
>
> -- Jeff J.
>
> - Original Message -
>> On 08/30/2016 05:32 PM, Jeff Johnston wrote:
>>
>>
>> I tried restarting our hipp instance and now linuxtools hudson pages are
>> unavailable (503). This is bad
>> timing since we are trying to get RC2 out for tomorrow.
>> While I don't know if "restarting" will fix the issue, just thought I
would
>> mention that I have not seen "restart" work for a very long time.
>> (Even though it "acts like" it does on the account page.)
>>
>> But what does work, for me, is to "stop" the server. And, then "start"
it.
>> [Not sure if you meant "restart" literally or not or if this is common
>> knowledge.]
>>
>> HTH
>>
>> ___
>> 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

Re: [cross-project-issues-dev] Upgrade Hudson Shared instance to SLES12(reloaded)

2016-08-29 Thread Sravan K Lakkimsetti

Hi Fred,

Can you delay the upgrade by three hours. At 10AM we still be having tests
being run on the machine. It will take another 3 hours to complete. Please
delay the upgrade by 3 hours to 1 PM EDT on Aug 31


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:   Frederic Gurr 
To: cross-project-issues-dev@eclipse.org
Date:   29-08-16 10:33 PM
Subject:[cross-project-issues-dev] Upgrade Hudson Shared instance to
SLES12  (reloaded)
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi,

Due to time constraints the upgrade did not happen on Thursday, August
25th as originally announced.

Therefore I'd like to announce that the upgrade is scheduled to happen
on Wednesday, August 31st, 10am EDT.

Downtime for the Hudson Shared instance should only be a few hours, as
the move mainly consists of file copying.


Please let me know if you have any concerns.

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

[cross-project-issues-dev] Oxygen(4.7) M1 is available

2016-08-05 Thread Sravan K Lakkimsetti


We are pleased to announce that Oxygen M1 is available for download and
updates.

 Eclipse downloads:

http://download.eclipse.org/eclipse/downloads/drops4/S-4.7M1-201608032000/

 Update existing (non-production) installs:
 http://download.eclipse.org/eclipse/updates/4.7milestones/

 Specific repository good for building against:

http://download.eclipse.org/eclipse/updates/4.7milestones/S-4.7M1-201608032000/


 Equinox specific downloads:

http://download.eclipse.org/equinox/drops/S-OxygenM1-201608032000/

Please note Eclipse has dropped support for the following Unix based
platforms: AIX, Solaris, HP-UX and Linux s390. The builds for these
platforms are not available on the eclipse.org downloads page.
For more information, please read the announcement made by the Eclipse PMC

Also we don't have Linux PPC64LE platform for this release due to
unforeseen circumstances. This will be available from M2.

Thank you to everyone who made this checkpoint possible.


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
___
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 Neon Looks Strange and Misbehaves (Ed Merks)

2016-05-06 Thread Sravan K Lakkimsetti

Hi Ed,

The image Scale up is related to hidpi support introduced in Eclipse M6. In
M6 we supported 100% 150% and 200%. In M7 we started supporting scaling
level in multiples of 25%. From the screen shot I guess you have the
scaling set to 125%. So the UI is scaled to 125%. there are two ways to
stop scaling
   Set the display settings to 100% as shown below


   Disable scaling using the flag -Dswt.enable.autoScale=false you can add
   this to eclipse.ini as well.


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:   cross-project-issues-dev-requ...@eclipse.org
To: cross-project-issues-dev@eclipse.org
Date:   06-05-16 05:15 PM
Subject:cross-project-issues-dev Digest, Vol 124, Issue 5
Sent by:cross-project-issues-dev-boun...@eclipse.org



Send cross-project-issues-dev mailing list submissions to
 cross-project-issues-dev@eclipse.org

To subscribe or unsubscribe via the World Wide Web, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
or, via email, send a message with subject or body 'help' to
 cross-project-issues-dev-requ...@eclipse.org

You can reach the person managing the list at
 cross-project-issues-dev-ow...@eclipse.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cross-project-issues-dev digest..."


Today's Topics:

   1. Eclipse Neon Looks Strange and Misbehaves (Ed Merks)


--

Message: 1
Date: Fri, 6 May 2016 13:45:03 +0200
From: Ed Merks 
To: Cross project issues 
Subject: [cross-project-issues-dev] Eclipse Neon Looks Strange and
 Misbehaves
Message-ID: <9457fed5-8336-2fba-879d-5250bc3d8...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi,

When I install the Eclipse Eierlegende Wollmilchsau for Neon M7, there
are some units with strange licenses present

Once the installation launches, the splash screen starts out nice, but
at some point it becomes pixelated like this:

After that, the state it comes up in isn't lovely.  Several technologies
feel the immediate need to prompt the user, and even to open a console.


Ignoring those problems, the IDE does not look pretty.

Notice that all the toolbar buttons are all bigger than they were in
Mars.  I.e., they're not showing in their native resolution but are
scaled up.  It looks sloppy in my opinion.  How can I get back the look
I had before?  Note that this problem occurs for all packages.

The error log is quite full of problems:

One exception of them occurs for all packages.  Why is this file
expected to exist at this location?

java.io.FileNotFoundException:
D:\sandbox\USER-HOME\jee-latest\eclipse\introData.xml (The system cannot
find the file specified)
 at java.io.FileInputStream.open0(Native Method)
 at java.io.FileInputStream.open(FileInputStream.java:195)
 at java.io.FileInputStream.(FileInputStream.java:138)
 at java.io.FileInputStream.(FileInputStream.java:93)
 at
sun.net.www.protocol.file.FileURLConnection.connect
(FileURLConnection.java:90)
 at
sun.net.www.protocol.file.FileURLConnection.getInputStream
(FileURLConnection.java:188)
 at
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity
(XMLEntityManager.java:623)
 at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion
(XMLVersionDetector.java:189)
 at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
(XML11Configuration.java:812)
 at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
(XML11Configuration.java:777)
 at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
(XMLParser.java:141)
 at
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse
(DOMParser.java:243)
 at
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse
(DocumentBuilderImpl.java:339)
 at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:177)
 at
org.eclipse.ui.internal.intro.universal.IntroData.parse(IntroData.java:159)
 at
org.eclipse.ui.internal.intro.universal.IntroData.initialize
(IntroData.java:63)
 at
org.eclipse.ui.internal.intro.universal.IntroData.(IntroData.java:47)
 at
org.eclipse.ui.internal.intro.universal.UniversalIntroConfigurer.loadData
(UniversalIntroConfigurer.java:533)
 at
org.eclipse.ui.internal.intro.universal.UniversalIntroConfigurer.
(UniversalIntroConfigurer.java:55)

We can't really expect David to police all these things.   If you
contribute something to the train, please make sure you properly test
the impact of what you contribute in combination with all the other
things being contributed.  The all-in-one product makes that very easy...


Regards,
Ed


-- next part --