Re: [cross-project-issues-dev] Non participating projects will be removed from the build

Hi Christopher, The Eclipse Subversive project committers are no longer able to support the project. I assume that the existing code base will work with the Eclipse Photon release since it's currently being included in builds. AFAICT, it's not included in any packages. You are correct that,

Re: [cross-project-issues-dev] Non participating projects will be removed from the build

Hi Wayne, Could you summarize the Subversion SVN Team Provider situation? I looked through my email logs and only found this, but I have a vague recollection of there being more about the topic. On 12/15, Wayne wrote: The *Eclipse Subversive* team has indicated that they can no longer

Re: [cross-project-issues-dev] HIPP2JIPP migration and cascaded jobs

Thanks Fred. I've converted the Mylyn jobs. Sam -- Sam Davis Senior Software Engineer, Tasktop Committer, Eclipse Mylyn http://tasktop.com On Thu, Jan 18, 2018 at 3:07 AM, Frederic Gurr < frederic.g...@eclipse-foundation.org> wrote: > Hi, > > Yes, I was referring to jobs that have "Cascading

Re: [cross-project-issues-dev] HTMLPrinter is Broken

I haven't read the whole thread. But I think it's fairly common sense that one should not use internal api by an external project. It's just one of life's axioms. It's like people who use reflection to get to private members of a java class and deploy that code into production. That's just a

[cross-project-issues-dev] Non participating projects will be removed from the build

Greetings folks. It's crunch time. At EOB tomorrow (Friday), we're going to disable the aggregation files for those projects that have not opted into Photon. Specifically, we're going to disable: - Eclipse EGerrit - Eclipse Sphinx - Eclipse Target Management - Eclipse Orion -

Re: [cross-project-issues-dev] HTMLPrinter is Broken

> I say that, as long as existing internals can be used, they are de facto API. That is incorrect and the current meaning is well defined. See x-internal description in the help https://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fbundle_manifest.html

Re: [cross-project-issues-dev] HTMLPrinter is Broken

Ed, My answers below > I think that this is the path paved with good intentions. Sure it is. I wish for the peace in world (even if it is the road to Hell) :) > We'll need to start at the bottom, in the Equinox runtime. For example, > we'll need to change a great many things in p2 before PDE

Re: [cross-project-issues-dev] HTMLPrinter is Broken

> Le 25 janv. 2018 à 10:22, Lars Vogel a écrit : > > > Should we change our policy and stop exporting new internal packages so > > that they really cannot be used? > > -2, we want to enable extenders to use and explore code before making it API. > IMHO a good way to

[cross-project-issues-dev] Building with Tycho against Platform M5 products requires some effort

Hi all, As you may have seen on some other thread, build with latest release of Tycho with Platform M5 product (sdk, ide...) in target-platform can result in the following error: [ERROR] Cannot resolve target definition: [ERROR] Software being installed: org.eclipse.platform.ide

Re: [cross-project-issues-dev] Latest platform I-builds requiring Java 9?

This should be announced to this list. Dani From: Mickael Istria To: Cross project issues Date: 25.01.2018 11:19 Subject:Re: [cross-project-issues-dev] Latest platform I-builds requiring Java 9? Sent by:

Re: [cross-project-issues-dev] Latest platform I-builds requiring Java 9?

On Thu, Jan 25, 2018 at 11:14 AM, Pierre-Charles David < pierre-charles.da...@obeo.fr> wrote: > Does this mean that the Photon M5 platform build of tomorrow can not be > consumed without switching to a development version of Tycho for our own M5 > contributions? Unless the platform's M5

Re: [cross-project-issues-dev] Latest platform I-builds requiring Java 9?

On 25/01/2018 10:24, Mickael Istria wrote: Hi, You'll need to use Tycho 1.1.0-SNAPSHOT to build against newer milestones of Eclipse Platform, . Version 1.1.0 should be released very soon with full Java 9 support. If you can't migrate to newer Tycho, you can try this workaround which

Re: [cross-project-issues-dev] Latest platform I-builds requiring Java 9?

On Thu, Jan 25, 2018 at 10:56 AM, Pierre-Charles David wrote: > Hi all, > > We have a canary build in Sirius which consumes nightly builds of all our > dependencies, including the platform. First of all, kudos for doing that. I wish every project does so! > It

Re: [cross-project-issues-dev] HTMLPrinter is Broken

Hi For 'stable' projects such as JDT deprecating+hiding/promoting internal may make sense, but it probably hides the code so that users in missding the opportunity to abuse users also miss the opportunity to exploit in other ways. For 'evolving' projects such as Xtext, internal has provided

Re: [cross-project-issues-dev] Latest platform I-builds requiring Java 9?

Hi, You'll need to use Tycho 1.1.0-SNAPSHOT to build against newer milestones of Eclipse Platform, . Version 1.1.0 should be released very soon with full Java 9 support. If you can't migrate to newer Tycho, you can try this workaround which consists in tweaking your .target file or

Re: [cross-project-issues-dev] HTMLPrinter is Broken

> Should we change our policy and stop exporting new internal packages so that they really cannot be used? -2, we want to enable extenders to use and explore code before making it API. IMHO a good way to provide new API is by having it already been explored by users. > And for existing internal

Re: [cross-project-issues-dev] HTMLPrinter is Broken

Mikaël, I think that this is the path paved with good intentions. We'll need to start at the bottom, in the Equinox runtime.  For example, we'll need to change a *great many *things in p2 before PDE works again; we'll also need to change many things in p2 so that Oomph works again, we'll

[cross-project-issues-dev] Latest platform I-builds requiring Java 9?

Hi all, We have a canary build in Sirius which consumes nightly builds of all our dependencies, including the platform. It started failing 2 days ago [1] with: [ERROR] Cannot resolve target definition: [ERROR]   Software being installed: org.eclipse.platform.ide 4.8.0.I20180122-2000 [ERROR] 

Re: [cross-project-issues-dev] HTMLPrinter is Broken

Very interesting thread, thanks to all for sharing your opinion. Changing existing internals could break clients because so far, they can use it. Should we change our policy and stop exporting new internal packages so that they really cannot be used? And for existing internal that one wants to