Thanks Holger for this excellent video!
As a reminder, if anyone is interested in managing the @EclipseJavaIDE
twitter account to eg. post this video on the day of the release; please
get in touch and I'll share the credentials. As mentioned earlier, I'm not
going to do it this time as I'm
Hello,
While we should make efforts to minimize duplications, and thanks to Ed to
encourage that, it's also great to acknowledge that this is not a primary
goal of SimRel and that we should praise the people who decided to make
Eclipse Platform rely on OSGi so such duplications of non-singleton
Reproduced in
https://ci.eclipse.org/releng/job/Builds/job/I-build-4.27/96/console . Have
you already open a ticket to EF infra support?
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
On Thu, Jan 19, 2023 at 4:20 PM Ed Willink wrote:
> Is this serious or have I totally misunderstood?
>
Both.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
tures and
some build customization; in the worst case you'll report issue.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat
Developers <https://developers.redhat.com/>
___
cross-project-issue
On Wed, Jan 4, 2023 at 8:53 AM Andrey Loskutov wrote:
> Also for the sake of entertainment: WHERE is the not supported CVS support
> code?
> Is it available in some eclipse/github/gitlab repo?
>
https://github.com/eclipse-platform/eclipse.platform.team/issues/8 and
Well, if there is a consensus that Platform should fully and stricly
implement semantic versioning, even for internal classes; we'll end up with
Platform bumping its major version every 3 months. I hope you -and everyone
else- is ready to be very careful at defining the version ranges in your
On Tue, Jan 3, 2023 at 3:12 PM Ed Willink wrote:
> I thought that Open Source was friendly; not a facilitator for a
> proprietary business case.
>
Well, sometimes allowing contributors to make money from their work is
actually one way to try being friendly.
But indeed, if one wants to do that
Hello,
The older version of CVS support seem to not be working any more with newer
Platform:
https://github.com/eclipse-platform/eclipse.platform.team/issues/29#issuecomment-1369456296
. While there is clearly no intention for Platform to revive CVS support or
anything of that form. the broken or
Hi,
Note that if you're running on a pod based on a recent Fedora version which
has Gnome >= 40, you should be able to leverage
https://www.phoronix.com/news/GNOME-40-Headless-Virtual and replace Xvnc &
metacicty with `mutter --headless`. If this is of high enough interest to
be able to leverage
On Fri, Sep 16, 2022 at 12:03 PM Lorenzo Bettini
wrote:
> has it been abandoned for good?
Yes.
But if you're willing to revive it, please consider joining the m2e-dev
mailing-list to state your intent and submitting PRs to restore it.
___
Thank you very much Holger, that a great resource!
___
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
n on this.
Particularly Ed who would have to do the work of respinning the SimRel
repo. My vote is +1.
> Thanks,
> Jonah
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
>
>
> On Thu, 8 Sept 2022 at 11:44, Mickael Istria wrote:
>>
>> Sorry, ag
2-09, basically requiring a respin.
The proposed change to SimRel is
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/195683 ; the
change in m2e-wtp is https://github.com/eclipse-m2e/m2e-wtp/pull/16 .
What do you think?
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide>
Hi Wayne,
m2e has to publish an important bugfix release. So it now contributes 2.0.3
to SimRel:
https://projects.eclipse.org/projects/technology.m2e/releases/2.0.3
Cheers
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
This should now be fixed with
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/195380
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
On Fri, Aug 26, 2022 at 11:02 AM Christian Dietrich <
christian.dietr...@itemis.de> wrote:
> This is long fixed in lsp4e but I don’t know why no new milestone was
> contributed
>
There are no real reasons against it, it just has to be important enough
for someone to report it and for someone
of m2e. I had to disable it for the moment.
I recommend Scout maintainers to evaluate migration to m2e 2.0.1 ASAP to
ensure both can participate simultaneously in SimRel.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat
Developers
On Thu, Jul 28, 2022 at 9:32 PM Martin Lippert wrote:
> Execution default-target-platform of goal
> org.eclipse.tycho:target-platform-configuration:2.7.3:target-platform
> failed: The Maven artifact to be added to the target platform is not stored
> at the required location on disk: required
>
On Thu, Jul 28, 2022 at 6:41 PM S A
wrote:
> Hi all,
>
Hi,
are there guidelines on how to name tests for specific bugs/issues, now
> that the Eclipse code base has mostly moved to GitHub?
>
There is no particular guidelines for test method names. It's up to the
contributor to name the tests
f you have relied on
3rd-party artifacts being provided in the Eclipse Platform p2 repo.
Remediation is documented at
https://github.com/eclipse-platform/eclipse.platform.common/blob/master/bundles/org.eclipse.platform.doc.isv/porting/4.25/incompatibilities.html
.
Cheers,
--
Mickael Istria
Eclipse
Hi,
I think this should be covered by the info in this document:
https://docs.google.com/document/d/1MnDBvOUwKvKacB-QKnH_PzK88dUlHkjs-D-DWEKmvkY/edit#heading=h.tir6oo3i3el8
HTH
___
cross-project-issues-dev mailing list
Again an excellent one, thanks!
___
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
ake those "bureaucracy" tasks are delayed. So anyone who
wants graduation to happen, please state your interest in taking care of
it, that would help a lot!
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat
Developers <h
Hi,
You may want to report an issue to
https://issues.redhat.com/projects/NEXUS/summary .
HTH
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
Hello,
Why particularly do you use this Maven plugin? Couldn't you simply get rid
of it?
Cheers,
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
Hi,
Do both version end in SimRel? I think the version constraint in Platform
are lax enough to let it use Orbit's version; so SimRel may actually
resolve it to only 1 version. If not and if this can help, we can consider
relaxing constraints in Platform to enable that.
HTH
On Tue, Apr 19, 2022 at 8:35 PM Torbjorn SVENSSON via
cross-project-issues-dev wrote:
> Hello,
>
Hi,
> What you are talking about here is more or less requiring anyone using
> SimRel to also move to a JRE 17.
Not directly (SimRel can still use older versions of TM4E), but yes, I
guess it
Thanks a lot Martin, it's indeed an annoyance.
Is specifying a (older) Gradle version on project a common practice? How
does it work in CLI if one uses a newer Gradle install to run some build
that defines an older Gradle version?
What are the chances that this bug gets fixed soon enough? (I'm
On Tue, Apr 19, 2022 at 4:38 PM Jonah Graham wrote:
> PS Where is "SimRel targets Java 11" defined? Is it just implicit at the
> moment (because Eclipse Platform is Java 11), or is it explicit somewhere?
>
Good question. It's more something that seems to me as an ad-hoc rule; but
maybe I'm just
right now" especially since JustJ
and thus SimRel and EPP packages ships a recent Java; but acknowledge that
this may require more discussion, hence why I'm sharing this plan for TM4E
early.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Re
___
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
Hi,
Wild Web Developer 0.13.3 is part of SimRel (for a relatively long time
already, so no extra things like respins to worry about). Can the 2022-03
metadata please be changed accordingly?
Thanks in advance
___
cross-project-issues-dev mailing list
Hi Christoph,
Thanks for sharing. Ability to mix felix, bnd and Tycho in a Maven builds
can really make many things much easier!
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
LemMinX-Maven was fixed to be compatible with Maven 3.8.3 to 3.8.5, m2e was
tested as working fine with this patch.
The only remaining thing to verify is Tycho.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe
Seems like Maven 3.8.5 candidate causes major issue with Tycho
"""
Plugin org.eclipse.tycho:tycho-maven-plugin:3.0.0-SNAPSHOT or one of its
dependencies could not be resolved: The following artifacts could not be
resolved: org.codehaus.plexus:plexus-archiver:jar:4.2.7,
Hi Christoph,
Thanks for the notification. Some important PR/jobs to look at for Eclipse
ecosystem to provide a minimal validation of upcoming Maven releases are
* m2e: https://github.com/eclipse-m2e/m2e-core/pull/602
* Tycho: https://ci.eclipse.org/tycho/job/tycho-build-with-maven-snapshots/
On Thu, Feb 17, 2022 at 3:49 PM Wim Jongman wrote:
> Dude, lighten up. You talk about the EF webmasters and the infra like they
> are about to die.
>
I was 1 year in the board of EF as committer representative. It was
moreover a bad year (they happen) with bad consequences for some EF
services
On Thu, Feb 17, 2022 at 12:15 PM Wim Jongman wrote:
> Having our own blogging server would make sure that useful blogs are
> archived forever, and it is organized and searchable from one place.
>
Define "our" ;)
The issue with asking Foundation for more services is that -with limited
manpower-
On Sunday, January 16, 2022, Lorenzo Bettini
wrote:
> So the limitations (not failing because of missing dependencies) of Tycho
mirror are real (I seem to understand they come from the eclipse mirror
application on which it's built).
Yes.
--
Mickael Istria
Eclipse IDE <https://www.eclip
On Saturday, January 15, 2022, Lorenzo Bettini
wrote:
> Mickael, IIRC your proposal was based on Tycho mirror goal
Nope, except for exceptions. See
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170553/14/pom.xml
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/ecli
On Fri, Jan 14, 2022 at 9:50 AM Christoph Läubrich
wrote:
> If Tycho is used
>
I tried for a long time to migrate SimRel from p2 aggregator (which is a
technology very few are capable of using, much fewer are capable of
maintaining, and much even fewer -if any- is willing to maintain) to Tycho
On Fri, Dec 10, 2021 at 8:12 PM Denis Roy
wrote:
> I guess I'm trying to determine if there are any versions of Eclipse,
> Jetty, jGit, etc that are vulnerable.
>
Eclipse Platform, and its transitive deps (including some parts of Jetty),
do not require nor ship log4j.
EGit does include log4j
As usual, it's a great resource. Thanks!
___
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
lipse-ide...@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat
Developers
Hi,
TM4E contributes 0.4.3 (released and added to SimRel earlier today).
LSP4E will most likely contribute a 0.20.1 and m2e a 1.19.0. Both are
supposed to get released next week.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for Red Hat
Developers
Hi,
What can be done?
>
Stop depending on repositories which don't have SLAs that fits your project
;)
I sincerely recommend you consider stopping usage of the
org.jboss.tools.tycho-plugins stuff, they're very old, not so well
maintained and the most interesting ones have been workarounds for
Thanks all!
Here are the known social media resources/discussions you may want to
share/upvote/discuss:
Tweet: https://twitter.com/EclipseJavaIDE/status/1438152934278238211
Reddit:
* https://www.reddit.com/r/java/comments/por5ko/eclipse_421_available/
*
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
M2e contributes 1.18.1 to SimRel:
https://projects.eclipse.org/projects/technology.m2e/releases/1.18.1
Thanks Holger and Jonah for noticing and fixing this contribution, together
with Wild Web Developer.
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/eclipseide> developer, for R
On Mon, Jul 5, 2021 at 3:39 PM Jörg Kubitz "Bundle-RequiredExecutionEnvironment: JavaSE-1.8"
> is not a guarantee it will still run on later java JDK versions. But we
> treat it as that.
> API removals will go on.
Actually, neither BREE or osgi.ee requirement do guarantee anything about
EE
Thanks all!
Tweeted https://twitter.com/EclipseJavaIDE/status/1405165811803856899
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
Thanks a lot 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
On Thursday, June 3, 2021, Matthias Sohn wrote:
> you can create a patch in Gerrit from a web browser, see
https://git.eclipse.org/r/Documentation/user-inline-edit.html
Thanks for the tip!
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer
On Thu, Jun 3, 2021 at 7:01 PM Jonah Graham wrote:
> Can we respin 2021-06 RC1 to include m2e 1.18.0? If so, that would be my
> vote. Based on your message about laptop this seems unlikely?
>
I just published m2e 1.18.0 release from current master. It's available at
1.17.2 in 2021-06 with the bug and just tell people
who face it to update to m2e 1.18.0, or
* we rush a m2e 1.18.0 in 2021-06, which can be a source of quirks in the
release process (especially since my work laptop just died so I'm not going
to be very efficient at it)
Cheers,
--
Mickael Istria
@Denis and Infra team: can such restrictions be setup on Eclipse Bugzilla
instance? If so, I guess it's only a matter of opening a bug when project
is ready to migrate, isn't it?
On Fri, Mar 19, 2021 at 9:42 AM Mickael Istria wrote:
> [...]
> One approach would be to make the BZ t
On Fri, Mar 19, 2021 at 10:28 AM Rolf Theunissen
wrote:
> RTFM:
> https://bugzilla.readthedocs.io/en/5.0/administering/categorization.html#basic-product-group-restriction
> Based on group permissions it is controlled who can enter, edit, read,
> etc., on a product granularity, So it should be
ing issues? Is it possible to make the product issues "read-only" (no
creation, no edition)?
My favorite one at the moment would be to block creation of new issues but
still allow edition.
Thanks in advance for your insights.
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/dow
And some (longer) discussion on hackernews:
https://news.ycombinator.com/item?id=26494952
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
t; 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 fro
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
On Thu, Mar 4, 2021 at 2:52 PM Wim Jongman wrote:
> We lose 99% of our casual contributors.
>
That's a huge exaggeration ;) But thanks for bringing attention on this
important topic!
I agree the "Signed-Off-By" is becoming a point of friction and making the
contribution barrier higher than for
Hi,
Please bring this question to tycho-u...@eclipse.org mailing-list
Cheers,
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
d your own protocol handlers for your integrations; the
gain on usability is huge as this allow more straightforward workflows.
The only tweak with GitHub is that it doesn't allow other links than http://
and https:// so a redirection service is necessary.
Cheers,
--
Mickael Istria
Eclipse
Hi Wayne,
I created new (empty at the moment) release entries for projects that will
have a new release to include in SimRel 2021-03 between now and March 17th.
At the moment, I did set the date to March 17th, but some of them will
probably be released sooner. I'll adapt the entries accordingly.
>
> Firstly because in these corona times, it seems involvement is lower than
> normal. And secondly because when ship a next release we want people to be
> able to update to it, so the question of whether EPP's sites will be found
> by existing 2020-12 installations is relevant. These
> I thought Jonah was solving this problem and already has a "fix" for it?
I think he's solving 1 instance of this problem, but not the whole class.
And the fix has some drawbacks (eg more p2 repositories necessary to
install certain packages).
On Thu, Feb 4, 2021 at 1:58 PM Ed Merks wrote:
>
is: would it hurt if we stop SimRel referencing EPP
site?
Cheers
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
___
cross-project-issues-dev
This also prevents from shipping the PDE/Maven integration by default in
packages because it contains BND artifact (unmodified from Maven) that is
not signed with the Eclipse certificate.
___
cross-project-issues-dev mailing list
tion
> _______
> 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
>
--
Mickael Istria
Eclipse IDE <htt
On Fri, Jan 15, 2021 at 11:57 AM Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:
> On 15.01.21 07:22, Aleksandar Kurtakov wrote:
> > In my experience with the same topic but in Platform releng the only way
> > to make issues not be introduced is make them break the build whenever
> >
On Tue, Jan 5, 2021 at 12:27 PM Ed Merks wrote:
> how are they IP reviewed if they've been pulled straight from some Maven
> repository somewhere?
>
Just like adding any 3rd-party jar to the dependencies, projects will still
have to verify *themselves* (ie not by delegating work to Orbit) that
uch better (simpler) handled
problem than consuming OSGi artifacts in plain Java.
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
___
cross-
Thanks all! Here is a tweet about it:
https://twitter.com/EclipseJavaIDE/status/1339255844316327939
Some Reddit posts:
https://www.reddit.com/r/java/comments/keaniu/eclipse_2020124180_released/
and
https://www.reddit.com/r/programming/comments/keant6/eclipse_2020124180_released/
Thanks for this video Holger, great as usual!
___
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
>> >
>>
>> --
>> Frederic Gurr
Hi all,
I've updated
https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170553 so it
looks more like a "final" change (although it's based on an older commit,
so the files would need to be updated/regenerated before we can consider
merging). It covers most concerns I've read here, and
On Fri, Nov 27, 2020 at 10:47 AM Eike Stepper wrote:
> Would our current *.aggrcon files be migrated to the new format for us?
Yes.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
Hi,
Wild Web Developer will attempt to release a 0.11.4 for SimRel 2020-12:
https://projects.eclipse.org/projects/tools.wildwebdeveloper/releases/0.11.4
m2e will attempt to release a 1.17.0 for SimRel 2020-12:
https://projects.eclipse.org/projects/technology.m2e/releases/1.17.0
Cheers,
On Fri, Nov 27, 2020 at 9:54 AM Ed Merks wrote:
> There is a big size difference between the *.jar versus the *.xml.xz,
> especially for the content.jar/content.xml.xz:
> https://download.eclipse.org/justj/?file=releases/2020-12/202011271000
> We'd not want to lose that I think, because this has
Thanks for having a look Fred.
On Thu, Nov 26, 2020 at 8:58 PM Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:
> * is there a good reason why the pom.xml has been moved to a module
> instead of keeping it in the root pom.xml/directory?
>
No, I just wanted to keep all files in the
in advance
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To
On Tue, Nov 10, 2020 at 5:21 PM Jonah Graham wrote:
> - The gerrit today only has a subset of the parts of CDT that are in
> simrel.aggr/cdt.aggrcom (the only contribution I looked at closely). AFAICT
> only the items that are categorized are present in category.xml. Where do
> uncategorized
On Wed, Nov 11, 2020 at 10:06 AM Christoph Läubrich
wrote:
> So it does not really fix anything in the file itself?
It's better if it modifies the file directly IMO.
> Currently, if tycho can't resolve it simply fails with: "can't resolve
> because missing requirement XYZ and so on"
> It
On Wed, Nov 11, 2020 at 9:00 AM Christoph Läubrich
wrote:
> As I'm currently working on category.xml adding support for source
> features/bundles if someone can explain what exactly this "fix versions"
> does I can investigate if it is possible to be added to tycho.
>
Fix version will fix the
Hello Jonah,
Thanks for having a look, answer inline
On Tue, Nov 10, 2020 at 5:21 PM Jonah Graham
wrote:
> 1. Merge conflicts - this is probably not such a big deal as the tycho
> validation seems very fast (2 minutes!).
>
I think the case of merge conflicts are almost non-existent for
, and the value/savings in changing
to Tycho is compelling enough to consider this migration for 2021-03.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.r
On Fri, Oct 9, 2020 at 9:12 AM Aleksandar Kurtakov
wrote:
> With that struggle I couldn't resist to ask myself why do we
> overcomplicate things and not do what most projects contributing to simrel
> already do - create their p2 repository via Tycho.
> There is a bug for moving to Tycho already
Hi all,
Here is a last reminder,
On Wednesday, September 16, 2020, Mickael Istria wrote:
> Hi fellow Committers!
> [Note: this is a 2nd iteration, for the 2020-09 to 2020-12 period]
>
> If you're seeking sponsorship via a service such as GitHub Sponsors or
Patreon, and would li
.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
>
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red
Awesome, 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
On Tue, Sep 1, 2020 at 7:53 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:
> Independent of this, according to my records, Eclipse Corrosion is overdue
> for a Release Review. Please initiate one immediately.
>
I've created
On Mon, Aug 31, 2020 at 1:38 PM Mickael Istria wrote:
> m2e *might* be 1.16.2 but that depends on a change upstream non-SimRel
> project (LemMinX) that not certain for 2020-09.
>
I confirm m2e will be 1.16.2, as important fix has been made available
upstream
https://projects.ec
On Tue, Sep 1, 2020 at 7:53 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:
> Somebody will correct me if I'm wrong, but AFAIK it a requirement for
> inclusion in an EPP package is participation in the simultaneous release.
> [...]
> Per EPP/How to create a package
>
On Mon, Aug 31, 2020 at 4:08 PM Frederic Gurr <
frederic.g...@eclipse-foundation.org> wrote:
> To clarify: in https://bugs.eclipse.org/bugs/show_bug.cgi?id=565263 you
> requested the move to JIRO since LSP4E requires newer versions of
> webkitgtk which we can't support in our old environment.
>
>
On Thu, Aug 27, 2020 at 8:51 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:
> *AFAICT, the corrosion.aggrcon file still exists and is not disabled.* Also,
> since CFT has dropped out, its aggrcon file should also be removed (not
> just disabled). Can somebody take care of that,
SWT Snippet195 contains an example of how to use LWJGL to draw on some SWT
Canvas. That's more than 3D plotting so it may be overkill for the desired
case though.
HTH
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To
PP package.
The reason behind that change is that SimRel was identified by its
contributors in mailing-list discussions as a non-profitable extra-step for
Corrosion, whose main target for downstream consumption are EPP packages.
Cheers,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/down
Hello Patrick,
The tycho-user mailing-list is the best place for such questions.
Please try Tycho 2.0.0-SNAPSHOT which decorrelates the Target Platform
execution environment from the compiler levels and should cover your case
better.
HTH
___
1 - 100 of 415 matches
Mail list logo
