Re: [platform-dev] Immediate feedback on ecj changes for jdt and platform build

Wow! Eating your own dogfood to the extreme. Great stuff. Thanks! ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Progress with JDT-LS in Eclipse IDE integration

Hey Mickael, Thanks for working on this. What does this mean in terms of LSP/DAP in general? Do other languages also benefit from this work or is it a java specialization? Cheers, Wim On Tue, 9 May 2023 at 17:19, Mickael Istria wrote: > Hello, > > For those interested, I'm willing to share

Re: [platform-dev] Dedicated "issues" repository

t; https://github.com/eclipse-platform/.github/issues > > > On 16.04.2022 13:29, Wim Jongman wrote: > > Hi, > > It would be great if the issues could be filed on the organization level > but since this is not possible: > > Did someone already suggest creating dedicated "issue&qu

[platform-dev] Dedicated "issues" repository

Hi, It would be great if the issues could be filed on the organization level but since this is not possible: Did someone already suggest creating dedicated "issue" repositories as the place to store issues? e,g, https://github.com/eclipse-platform/issues Issues can be referenced from each

Re: [platform-dev] Migration of Eclipse TLP to GitHub complete

Woot! Thank you so much! On Fri, 15 Apr 2022 at 13:21, Sravan K Lakkimsetti wrote: > Hi, > > > > Thanks to enormous effort from Michael Istria in experimenting, > identifying tasks on exactly what needs be done and migrating most of the > repositories, we are now able to migrate all source code

Re: [platform-dev] eclipse.platform.text migrated to GitHub

The transition team is making great progress. On behalf of everyone: Thank you all! Cheers, Wim On Fri, 25 Mar 2022 at 16:16, Mickael Istria wrote: > eclipse.platform.text Git repository is now moved to GitHub: > https://github.com/eclipse-platform/eclipse.platform.text > If you see this

Re: [platform-dev] Turn on protected branches?

+1 On Fri, 25 Mar 2022 at 11:50, Lars Vogel wrote: > +1 for protecting master from direct pushes, IMHO build verification > should be mandatory > > Jonah Graham schrieb am Fr., 25. März 2022, > 11:48: > >> >> >> On Fri., Mar. 25, 2022, 05:32 Mickael Istria, wrote: >> >>> >>> >>> On Fri, Mar

Re: [platform-dev] Github workflow

I like all this. I don't like forks and used to have branches on main repo - not recommended. > > Indeed. The "upstream" repo shouldn't be used as a workspace for ongoing work. Your workspace is your fork. Also, this is free to choose from. If one wants to work with a fork (e.g. to stash WIP),

Re: [platform-dev] Github workflow

Yes, a great starting point Sravan. This workflow matches my preferred way of working. In this way, contributors and committers follow the same workflow. Cheers, Wim Eclipse Github Workflow On

Re: [platform-dev] Github workflow

> I don't have the same experience here in general: You are right. After the force, there is a backdoor to previous comments. [image: image.png] On Tue, 22 Mar 2022 at 13:45, Mickael Istria wrote: > > > On Tue, Mar 22, 2022 at 1:39 PM Wim Jongman wrote: > >> >> &

Re: [platform-dev] Github workflow

> What particularly do you think does not work well with it? > File reviews or bound to the commit id and when you force push, the review is gone. See the screenshot below. This makes it very hard for the reviewer to see if their suggestions have been followed. > > >> I propose to just keep

Re: [platform-dev] Github workflow

king-with-forks/configuring-a-remote-for-a-fork >> > >> https://stackoverflow.com/questions/9257533/what-is-the-difference-between-origin-and-upstream-on-github >> > >> > >> > Op di 22 mrt. 2022 om 11:13 schreef Mickael Istria > >: >> >&

Re: [platform-dev] Github workflow

. It will not work well with the Github review system. I propose to just keep committing on the branch (a bit like Gerrit change sets) and then always(!) Squash and Merge Cheers, Wim On Tue, 22 Mar 2022 at 11:13, Mickael Istria wrote: > Hi, > > On Tue, Mar 22, 2022 at 10:46 AM Wim Jongman

[platform-dev] Github workflow

In BIRT, Windowbuilder, and Nebula we successfully use the following workflow: 1. Fork the main repo 2. Create an issue in the main repo e.g. "My Issue" #1 (#1 being the next ID) 3. Make changes in a branch in your fork (not in master/main)!!! 4. Commit with "My Issue #1"(include

Re: [platform-dev] Github migration and Gerrit reviews

I have two stale open Gerrits that still might be useful. Will Gerrit be available after the move so that I can convert them to PR's? Cheers, Wim On Fri, 18 Mar 2022 at 09:15, Aleksandar Kurtakov wrote: > Hey everyone, > This is a kind request for everyone having open gerrits in the following

Re: [platform-dev] Using MasterDetailBlock on e.g. Dialog without FormHeading (whitespace)

Hi Marcus, The subclassing warning is a generic one. Similar to the checkSubclass method in SWT widgets. Please subclass to fix your issue and consider sharing it if you think it is useful for others. Cheers, Wim On Mon, 14 Mar 2022 at 15:44, Hoepfner, Marcus via platform-dev <

Re: [platform-dev] Adding new menus using the menuContribution extension point into Search menu

Can't you also redefine the dialogGroup in your stub menu? Cheers, Wim On Sun, 6 Mar 2022 at 12:08, Gayan Perera wrote: > Hi all, > > I'm trying to insert a new sub menu in to search menu using the > menuContribution extension point. I want to insert my sub menu just after > the dialogGroup in

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

Thanks for counting. It has been a good discussion. Cheers, Wim On Fri, 4 Mar 2022 at 10:14, Andrey Loskutov wrote: > Hi all, > > this is an update on current state. > I consider voting is done now, the results are (sorry if I've missed > anyone) 19:10 for stop current practice. > I think the

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

> The difference is that that has nothing to do with auto-closing at all. If the bug that was now worked on was correctly triaged we would have found the auto-closed bug and reopened that. Point is that even if bugs are automatically closed, they are not gone. Anyway, the point is moot. I

[platform-dev] Freeze?

Is there now a freeze period? We get issues on this Gerrit. https://git.eclipse.org/r/c/platform/eclipse.platform.ui/+/190740 Cheers, Wim ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

description > and you just linked it to a very old bug ;-) > > Am 20.02.22 um 16:25 schrieb Wim Jongman: > > Here is some good news: Jörg Kubitz just resolved bug 89838 from march > 2005. > > > > Bug 89838 was automatically closed after 15 years but emerged again

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

Here is some good news: Jörg Kubitz just resolved bug 89838 from march 2005. Bug 89838 was automatically closed after 15 years but emerged again by someone who cared and was resolved. Cheers, Wim On Sat, Feb 19, 2022 at 12:47 PM Liviu Ionescu wrote: > > > > On 19 Feb 2022, at 13:38, Rolf

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

I can still hear Erich Gamma say in Ludwigsburg: "Every bug report is a love letter" . It is true, and we get a lot of love! > I'm surprised that people still hope that a 20+ years old project that has been used constantly by 3 to 12 million users can have an empty backlog and expect its

Re: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform projects

-1 close close close Please note that it is *LESS *work to keep open because *no one will ever look at it again.* If it still matters to people then they can reopen. It is a tool to restart the discussion. Without closing, it would be sitting there forever. This bug hasn't had any activity in

Re: [platform-dev] Where is the e4 model for the workbench located?

Hi Marcus, You won't see any of that in the model because it does not depend on a specific UI implementation. It is the platform that renders the model. Take a look at project *o.e.e4.ui.workbench.swt* class: *org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine* It is in this repo

Re: [platform-dev] 4.21 (2021-09) M3 milestone reminders

Hi, there is no next release scheduled on the project page: https://projects.eclipse.org/projects/eclipse/governance On Fri, Aug 13, 2021 at 4:46 PM Kit Lo wrote: > Team, > > Next week is the milestone week for 4.21 M3. > > Monday > - Last day of development (and even then, no "big changes").

[platform-dev] Eclipse hangs on merging xpath

Hi, Before I file an issue, does anyone know about performance issues about merging model fragments? I see a 2 minute hang in this area: "main" #1 prio=6 os_prio=0 cpu=85015.63ms elapsed=87.72s tid=0x0278e800 nid=0x11f4 runnable [0x004fc000] java.lang.Thread.State: RUNNABLE

Re: [platform-dev] Website idea

t; I gave it a try https://github.com/eclipse/birt-website/pull/11 but ran > into some problems. I am happy to help you debug/test out the flow as a > non-committer on BIRT. > > Jonah > > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com > > > On Mon, 17 M

[platform-dev] Website idea

Hi, In the BIRT project, we have converted the website exactly as I have it in mind for our website. *Not the L but the workflow*. 1. The website is generated from markdown 2. An "edit this page" link brings you to the source 3. A change and pull request will update an intermediate website on

[platform-dev] Gerrit user

Hi, I created a new Eclipse account because the webmaster blocked mailing list deliveries to outside accounts. I want mailing list mail to be delivered to Gmail and committer-related stuff to my work mail. Now I see that people are adding this non-committer email to Gerrit reviews. Is there a

Re: [platform-dev] E4 + Table Foreground color

I suspect you run with theming of some sort? Can you switch of theming and check if that changes it? Cheers, Wim On Thu, Apr 22, 2021 at 10:17 AM Christoph Läubrich wrote: > If I create a JFace table in "plain" swt I can change the foreground > color with a ColumnLabelProvider. > > But when I

Re: [platform-dev] most performant way to paint a (platform-specific) pixel-array

Are you looking to animate things? On Mon, Apr 19, 2021 at 11:20 AM Christoph Läubrich wrote: > I have a pixel-buffer and like it o be painted in the most performant > way onto a SWT Canvas. > > Current approach is to convert this into an ImageData, create an image > and then paint it inside

Re: [platform-dev] Build from source problem

Also, don't compile with sudo, that will cause the build artifacts to be created for root and you might not be able to access them later on. On Fri, Apr 16, 2021 at 7:47 AM Sravan K Lakkimsetti < sravankum...@in.ibm.com> wrote: > Here you are seeing compilation failure in SWT. > In SWT we have

Re: [platform-dev] Track SWT allocations

Christoph* On Thu, Apr 15, 2021 at 8:17 PM Wim Jongman wrote: > Hi Christophe, > > > This is triggered when the widget is garbage collected (but was not > disposed). Just set the property as described in the N It works really > nice. > > https://bugs.eclipse.org/bug

Re: [platform-dev] Track SWT allocations

Hi Christophe, This is triggered when the widget is garbage collected (but was not disposed). Just set the property as described in the N It works really nice. https://bugs.eclipse.org/bugs/show_bug.cgi?id=569752 Cheers, Wim On Thu, Apr 15, 2021 at 5:16 PM Christoph Läubrich wrote: >

Re: [platform-dev] canonical way to handle optional dependencies

Yes, those are two good options. AFAIK there is no additional magic that you miss. I would wrap the dependency checking in a static class. e.g use if(DepBundleChecker.isAvailable()){ .. do something ..} instead of catching class loading exceptions. It's a bit more elegant but it stays a pita.

Re: [platform-dev] New Website

/show_bug.cgi?id=572624 I will create individual Gerrits to get rid of old stuff and references thereto. Cheers, Wim On Wed, Mar 31, 2021 at 4:55 PM Wim Jongman wrote: > Yes, that is an advantage. The disadvantage is that we start with a > neglected packed-with-rubbish website we have to cle

[platform-dev] Restart failure after update

Hi, Does anyone else see a failure to restart after an (i-builds) update? Cheers, Wim !ENTRY org.eclipse.osgi 4 0 2021-04-02 20:51:29.395 !MESSAGE Application error !STACK 1 java.lang.NullPointerException at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:724) at

Re: [platform-dev] New Website

Our wiki points to http://eclipsercp.org/book/chapters/RCP_Foreward2.pdf Are we hacked or did we ditch this domain? On Fri, Apr 2, 2021 at 7:37 PM Wim Jongman wrote: > Is this mention still relevant? It is on the platformui page. > https://www.eclipse.org/eclipse/platform-ui/ >

Re: [platform-dev] New Website

Is this mention still relevant? It is on the platformui page. https://www.eclipse.org/eclipse/platform-ui/ Thanks to Yourkit YourKit is kindly supporting open source projects with its full-featured YourKit Java Profiler . YourKit, LLC

Re: [platform-dev] New Website

the history then we can archive the old site. *Website genesis:* commit c5ae5f6bae863ec80a6d563a30d834279d48059c Author: jeff Date: Fri Nov 2 13:46:54 2001 + initial On Wed, Mar 31, 2021 at 3:11 AM Mickael Istria wrote: > On Tue, Mar 30, 2021 at 11:56 PM Wim Jongman >

Re: [platform-dev] New Website

Yes, a hybrid hugo/php works fine. I have pushed one single PHP file: https://staging.eclipse.org/eclipse/ant/index.php One question: would it be possible for the site to contain a mix of > hugo/markdown and HTML/PHP ? That would IMO allow to transition right now: > we start with the Git repo

Re: [platform-dev] New Website

Yes, I agree and I have already experimented with that. Whatever PHP, HTML you put in the content directory will be copied as-is. So if the webserver is configured properly it should be able to serve this. I have to ask webmasters to be sure. Cheers, Wim On Tue, Mar 30, 2021 at 5:11 PM Mickael

Re: [platform-dev] New Website

a list of pages NOT included in the new site (we don't add anything). This list will be brought to the PMC * After PMC approval we go live Cheers, Wim On Tue, Mar 30, 2021 at 4:23 PM Wim Jongman wrote: > > > >> Sorry about this being mistrusting and bureaucratic; but on th

Re: [platform-dev] New Website

> Sorry about this being mistrusting and bureaucratic; but on the other hand > this is sometimes useful to ensure that resources and energy is optimized > and that value/risk ratio is good. > I rest my case.  > > I agree many documents can probably be discarded, and a cleanup would help > in

Re: [platform-dev] New Website

> > Live already (with full Hugo workflow) > https://staging.eclipse.org/eclipse > > The username / password is testuser:plaintext ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit

Re: [platform-dev] New Website

Mikael, In the first message of this thread, I announced that I am incubating the website at *STAGING*.eclipse.org/eclipse where it will be developed until we can release it. Step by step Live already (with full Hugo workflow) https://staging.eclipse.org/eclipse I was going to respond to your

Re: [platform-dev] New Website

Dude, you cannot drop this bomb right now. I have spent 5 full working days to get this party started. And now you come with an "opinion"? I have communicated very early that I was working on bringing the website to Hugo which has full support from the foundation. Listen carefully: I am not

Re: [platform-dev] New Website

tarted > [2] > https://wiki.eclipse.org/Jenkins#How_to_build_my_project.27s_website_with_Jenkins.3F > [3] https://gohugo.io/ > > Thanks Wim! > > Jonah > > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com > > > On Mon, 29 Mar 2021 at 17:22, Wim Jongm

Re: [platform-dev] New Website

It took a long struggle but our webmasters did it and we now have a very easy website process. 1. We just edit some markdown files e.g. [1] 2. The whole process can be tested locally to make sure the changes are ok [2] 3. The build converts the website to static HTML and pushes it to the main

Re: [platform-dev] How to best document consumed OSGi/DS services?

I don't think we strongly need such specific javadoc annotations at the > moment. Specific annotations were not required for extension points, so I > don't think they should be necessary for services. > Extension points are not documented in the Javadoc. It would be nice if they'd be documented

Re: [platform-dev] Has the time come?

contributors.) Possible solution: J don't create forks but create branches in the clone from main and are allowed to push to a branch in the main repo. On Mon, Mar 22, 2021 at 1:39 PM Wim Jongman wrote: > I want to mention one thing in Gerrit that I probably do wrong or is > indeed difficult: W

Re: [platform-dev] Has the time come?

I want to mention one thing in Gerrit that I probably do wrong or is indeed difficult: Working together on the same change. When I work on my own, I can sequentially push new changes. If someone is helping me (e.g. changed the commit message in the Gerrit UI, or anything more substantial) then

Re: [platform-dev] Has the time come?

Thanks for your input and contributions, Ingo. We hope many may follow ;) ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] How to best document consumed OSGi/DS services?

Just brainstorming I would say, extend the javadoc engine to process the service xml with some style sheet and insert that in the HTML output? Does anyone know if Javadoc can be extended like that? The doc on javadoc suggest the usage of an extension mechanism [1] Cheers, Wim [1]

Re: [platform-dev] Has the time come?

A friendly reminder to no one in particular. We are all in this together. Let's not form camps and bury ourselves in the trenches. Pros and cons are valuable, personal attacks en frustration venting not. If you want to write a hot-headed response, do it tomorrow (a piece of advice I should take

Re: [platform-dev] Has the time come?

I agree. Maybe we can allow ECA contributors to push to a branch in the main repo? On Thu, Mar 18, 2021 at 2:13 PM Lars Vogel wrote: > Hi Dirk, > > > For GitHub projects I always need to fork, update my fork, create the > PR, force push on every review comment. > > I also find the Github

Re: [platform-dev] Has the time come?

Great discussions. We all want the best of Eclipse. Some remarks to Rolf's post. > *From an external perspective, the project seems outdated and dying. For instance, many of the website pages and wiki pages contain outdated content (e.g. https://www.eclipse.org/eclipse/development/ next release

Re: [platform-dev] Has the time come?

> > > It just seems like the website is basically the only repo we cannot move > easily because of current deployment. > We can use the double push method. We have a CI job that pulls the website from Git and pushes it to the deployment repo. The link below has some extra HUGO processing that we

Re: [platform-dev] Has the time come?

> It's not a rule, it's just the way it works Right! jumped to false conclusions. Thanks for clarifying. 蘿 ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Has the time come?

Mikael, I did not mean to lecture you (after reading my reply again ). It's funny, really; we have this hosting rule, but also a trick how to circumvent it  On Tue, Mar 16, 2021 at 4:57 PM Wim Jongman wrote: > > Just a quick note that content served by https://www.eclip

Re: [platform-dev] Has the time come?

On Thu, Mar 11, 2021 at 5:50 PM Wim Jongman wrote: > I think the move to GitLab is for projects that stay on the foundation > infra. > > On Thu, Mar 11, 2021 at 5:05 PM Jonah Graham > wrote: > >> >> >> On Thu, 11 Mar 2021 at 11:00, Ed Merks wrote: >> >&g

Re: [platform-dev] Manual fix in swt .classpath file required

Totally fine! Thank you. On Mon, Mar 15, 2021 at 6:39 PM Aleksandar Kurtakov wrote: > In order to simplify SWT project structure a bit I've merged common and > common_j2se source folders [1]. This requires that whoever has it setup in > the workbench removes common_j2se source folder from the

Re: [platform-dev] Has the time come?

general developers list. > *Subject:* [EXTERNAL] Re: [platform-dev] Has the time come? > > > > On Wed, Mar 10, 2021 at 4:56 PM Wim Jongman > wrote: Maybe we can skip adding features completely for one or two releases > and have all hands focusing entirely on the releng proce

Re: [platform-dev] Has the time come?

On Wed, Mar 10, 2021 at 8:48 PM Mickael Istria wrote: > The thing is that, technically speaking, GitHub is not an improvement over > Gerrit and Bugzilla. A few things are better, many things are worse... > Going to GitHub wouldn't improve the workflows themselves. The only major > benefit is the

Re: [platform-dev] Has the time come?

On Wed, Mar 10, 2021 at 4:31 PM Aleksandar Kurtakov wrote: > > > On Wed, Mar 10, 2021 at 4:56 PM Wim Jongman wrote: > >> Maybe we can skip adding features completely for one or two releases and >> have all hands focusing entirely on the releng process. >> > &g

Re: [platform-dev] Has the time come?

> > > Eclipse has a GUI, and it's really helpful to develop GUIs using a tool >> which allows inline images. GitHub PRs and issues work really well together. >> > > It looks like Bugzilla can do that: > https://bugzilla.mozilla.org/show_bug.cgi?id=1472522 . Would you mind > opening a bug to

Re: [platform-dev] Has the time come?

f code is just a mess. > > > Am 10.03.21 um 15:37 schrieb Wim Jongman: > > Hi, > > > > Can we discuss the move to GitHub again? > > > > Cons: > > * No Gerrit -> best review system ever > > > > Pros: > > * All the developers are there

[platform-dev] Has the time come?

Hi, Can we discuss the move to GitHub again? Cons: * No Gerrit -> best review system ever Pros: * All the developers are there. * No Gerrit -> easy entry for new devs Cheers, Wim ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe

[platform-dev] Replacing cglib with bytebuddy.

Hi, I am trying to get rid of cglib class injection in WindowBuilder. I have to replace this code where *projectClassLoader *is a parameter and *bytes* the serialized class. ReflectUtils.defineClass( "org.eclipse.wb.internal.rcp.databinding.parser.DefaultBean", *bytes*,

[platform-dev] DBeaver

Hi, I recently found the DBeaver project on MP. It is a stunning plug-in to connect to various databases. I'm really impressed. Do we know the DBeaver committers? Are there any on this list? Cheers, Wim ___ platform-dev mailing list

[platform-dev] Gerrit Spam

Hi, I can do without the "Build started" messages from Gerrit. Do I have supporters for this? Otherwise, I don't want to waste the webmaster's time asking for a solution. Cheers, Wim ___ platform-dev mailing list platform-dev@eclipse.org To

Re: [platform-dev] [osgi-wg] How to document OSGi extensibility?

ervice without an need for adding > another extensionpoint and asking people to implement that. > > So from a user POV it makes much more sense to document at the service > interface the intent to use this as a "WhiteBoardService". > > > Am 22.01.21 um 20:31 schrie

Re: [platform-dev] [osgi-wg] How to document OSGi extensibility?

The annotations idea is very creative but I don't think it is the answer to Mickaels question. Mostly because the documentation is the wrong way around. We want to make clear from the generic editor user's POV that a whiteboard pattern can be used to inject code, not from the interface. Besides,

Re: [platform-dev] Parallel Builds

Cool. I am new to this too. I have activated it (set to 5 (5 jobs?). But a full java build takes just as long and I do not see multiple build jobs. I have a 270 project workspace. For normal 99% work, the incremental build is working fine. It is slow (or rather, it takes a long time) when a full

[platform-dev] New splash screen

A new splash screen is being discussed here https://bugs.eclipse.org/bugs/show_bug.cgi?id=569333 ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] [eclipse.org-planning-council] 2021-06, 2021-09, 2021-12 schedule - Change December release date?

I haven't thought it through, but that is not a bad idea. It gives us a proper Apr M1 period and it would also solve this December squeeze. Cheers, Wim On Mon, Jan 11, 2021 at 2:30 PM Aleksandar Kurtakov wrote: > > > On Mon, Jan 11, 2021 at 3:28 PM Wim Jongman wrote: >

Re: [platform-dev] [eclipse.org-planning-council] 2021-06, 2021-09, 2021-12 schedule - Change December release date?

You asked for opinions. My opinion is that the schedule pain is not in the december release but in the march release, On Mon, Jan 11, 2021 at 2:22 PM Aleksandar Kurtakov wrote: > > > On Mon, Jan 11, 2021 at 3:19 PM Wim Jongman wrote: > >> >> Hi, >> >>

Re: [platform-dev] [eclipse.org-planning-council] 2021-06, 2021-09, 2021-12 schedule - Change December release date?

Hi, Assuming everyone starts again Jan 2, there are about 10 workdays for March M1. I prefer combining March M1 and M2 over shortening December. Cheers, Wim On Mon, Jan 11, 2021 at 1:03 PM Aleksandar Kurtakov wrote: > Planning council discusses moving one week earlier the 2021-12 release so

Re: [platform-dev] I-Builds repo is not current

9 I-builds > > > > Thanks > > Sravan > > > > *From:* Wim Jongman > *Sent:* 06 January 2021 20:02 > *To:* Eclipse platform general developers list. > *Subject:* [EXTERNAL] [platform-dev] I-Builds repo is not current > > > > Hi, > > >

[platform-dev] I-Builds repo is not current

Hi, Until recently I was updating from the i-build update site. It does not contain the 4.19 i-builds. Did this recently change or did I find an issue? https://download.eclipse.org/eclipse/updates/I-builds/ Cheers, Wim ___ platform-dev mailing list

Re: [platform-dev] [e4-dev] Moving "e4" bugzilla component and e4-dev mailing into Platform?

+1 great idea. > Merging git repos is a separate topic, please don't inject it here :) Too late ;) On Fri, Nov 27, 2020 at 10:18 AM Alexander Fedorov < alexander.fedo...@arsysop.ru> wrote: > +1 to "inline" e4 channels to Platform and to archive unused e4 > repositories. > > Merging git repos is

Re: [platform-dev] Review/Update of Acknowledgements for 4.18

*Subject:* [EXTERNAL] Re: [platform-dev] Review/Update of > Acknowledgements for 4.18 > > > > We definitely need a special note for him! > > We can use the bug to suggest the note. > > > > Thanks & Regards, > > Sarika > > > > - Original message - >

Re: [platform-dev] Review/Update of Acknowledgements for 4.18

х утопающих > > https://www.eclipse.org/user/aloskutov > > > *Gesendet:* Dienstag, 24. November 2020 um 12:54 Uhr > *Von:* "Wim Jongman" > *An:* "Eclipse platform general developers list." < > platform-dev@eclipse.org> > *Betreff:* Re: [platform-dev] R

Re: [platform-dev] Using custom font for welcome page

Hey Nikifor, Is "text-center" overriding the font? What happens when you remove "text-center". https://www.w3schools.com/cssref/tryit.asp?filename=trycss_sel_class_more2 Cheers, Wim On Sat, Nov 7, 2020 at 4:51 PM Nikifor Fedorov wrote: > Hello, I'm trying to use a custom font loaded from

Re: [platform-dev] Review/Update of Acknowledgements for 4.18

It's good to see so many names on this list. Thanks, Sravan! Cheers, Wim On Tue, Nov 24, 2020 at 8:23 AM Sravan K Lakkimsetti < sravankum...@in.ibm.com> wrote: > All, > > Please go through the acknowledgements for Eclipse 4.18 and add/remove > items as appropriate/required. > >

Re: [platform-dev] Using WeavingHook in eclipse

Hi, Is the bundle started? Cheers, Wim On Sun, Oct 25, 2020 at 1:58 PM Gayan Perera wrote: > Hi, > > I’m trying to register a weavinghook using services descriptors. I > annotated my weavinghook class with component annotation and inhave the > osgi folder with the service descriptor xml in

Re: [platform-dev] Commit messages

t; Tom > > > On 2020-10-24 16:53, Wim Jongman wrote: > > In general, I would say that the commit message must clearly explain to > > others what has changed. > > > > On Sat, Oct 24, 2020 at 2:39 PM Alex Blewitt > wrote: > > > >> > >&g

Re: [platform-dev] Commit messages

In general, I would say that the commit message must clearly explain to others what has changed. On Sat, Oct 24, 2020 at 2:39 PM Alex Blewitt wrote: > > > On 24 Oct 2020, at 13:12, Wim Jongman wrote: > > > > Andrey recently pointed out on a couple of commits that co

[platform-dev] Commit messages

Hello, Andrey recently pointed out on a couple of commits that commit messages could be better. I agree with that. Can we discuss this? Cheers, Wim A list of recent commits is here: https://git.eclipse.org/c/platform/eclipse.platform.ui.git/log/ ___

Re: [platform-dev] Inconsistent version change in SWT 4.18

Hey Greg, (I am not part of the releng team so all of this is just what I would do if I was in a similar situation.) This is a very specific use case. You should probably revisit your algorithm. The versioning scheme is not etched in stone. I don't know if this can get included for M1a on

Re: [platform-dev] SWT is great

Oops! I nearly missed a beautiful opportunity to plug the Nebula project. All build on SWT: https://eclipse.org/nebula On Wed, Oct 7, 2020 at 1:40 PM Wim Jongman wrote: > I agree, Thomas. It is brilliant. Thanks for reminding everyone. > > On Wed, Oct 7, 2020 at 9:27 AM Aleksandar

Re: [platform-dev] SWT is great

I agree, Thomas. It is brilliant. Thanks for reminding everyone. On Wed, Oct 7, 2020 at 9:27 AM Aleksandar Kurtakov wrote: > > > On Wed, Oct 7, 2020 at 9:59 AM Thomas Singer wrote: > >> Hi all, >> >> Since the last few months I'm evaluating different other programming >> languages and GUI

Re: [platform-dev] Getting a list of files that are modified in given project

Maybe the team synchronize API is of use. This is SCM agnostic: I know it works with git, svn and cvs. I dug up some info here. Scroll down on this page https://www.eclipse.org/eclipse/platform-team/team3.0/synchronizing_solution.html On Mon, Oct 5, 2020 at 10:27 PM Gayan Perera wrote: > Hi

Re: [platform-dev] Recent API Removal breaks clients

umbrella bug is here. *Bug 567195* <https://bugs.eclipse.org/bugs/show_bug.cgi?id=567195> - Optimize the API removal process Cheers, Wim On Thu, Sep 17, 2020 at 9:05 PM Wim Jongman wrote: > Hi, > > jface.util.Assert was removed as well as platform.getJobManager. > > I love

Re: [platform-dev] Recent API Removal breaks clients

> or (perhaps a silly idea, don't hate me) create a class PlatformDeprecated > that Platform extends and move dead wood there. > This cleans up Platform with almost 400 lines of deadwood. https://git.eclipse.org/r/c/platform/eclipse.platform.runtime/+/169614

Re: [platform-dev] Recent API Removal breaks clients

> > For JFace Assert, the deprecation is now 7 years old, and the alternative > API to use has been available for 15 years. > For platform.getJobManager(), the deprecation is now 6 years old, and the > alternative API to use has been available for 15 years. > I don't disagree. I want to add one

Re: [platform-dev] Recent API Removal breaks clients

> A lot of people watch this list and are not interested in this discussion. I think everybody is interested in this discussion. Discussions like these are the exact purpose of this list. ___ platform-dev mailing list platform-dev@eclipse.org To

Re: [platform-dev] Recent API Removal breaks clients

wrote: > > > On Fri, Sep 18, 2020 at 12:30 PM Aleksandar Kurtakov > wrote: > >> >> >> On Fri, Sep 18, 2020 at 11:27 AM Wim Jongman >> wrote: >> >>> >>> Should we not support older versions of Eclipse? >>>>> >>>

Re: [platform-dev] Recent API Removal breaks clients

> > Although I'm not against such a rule, I don't think it will really fix > those cases. > The reason why consumer code is broken is because it wasn't maintained > properly for several years and left usage of deprecated APIs while better > alternatives have existed and are well documented, so I

  1   2   >