Re: [cross-project-issues-dev] [eclipse.org-planning-council] Neon.3 Update Problems

to detect multiple versions. Regards Ed Willink On 31/03/2017 08:14, Alexander Nyßen wrote: Let's enforce that then. Looks like that would solve a lot of problems... Cheers, Alexander Am 31.03.2017 um 08:30 schrieb Mickael Istria <mailto:mist...@redhat.com>>: Th

Re: [cross-project-issues-dev] Oxygen M6 is available

Hi Frederic IIRC in previous years the composite was much smaller, at most 3 milestones. This reduces the hazards of projects not tracking major version changes in dependencies. Is the change intentional? Are some project's contributions too intermittent? Regards Ed Wi

[cross-project-issues-dev] ASM for Java 9 (was Re: Java 9 Readiness)

;& !hasOpcodes_V1_9 && (readShort > Opcodes.V1_8)) { return Opcodes.V1_8; } return readShort; } }; I can keep the above code unchanged till Java 10 at which point I can assess whether Java 8 is dead.

Re: [cross-project-issues-dev] Java 9 Readiness

Hi Evgeny Thanks. Workaround added to wiki. Regards Ed Willink On 16/03/2017 00:16, Evgeny Mandrikov wrote: Hi, On Tue, Mar 14, 2017 at 10:08 PM Ed Willink <mailto:e...@willink.me.uk>> wrote: @Dani: I've clarified my confusions in the wiki and added a new

Re: [cross-project-issues-dev] Java 9 Readiness

Dani: I've clarified my confusions in the wiki and added a new table for Orbit utility; ASM bombs on Java 9 classes. Exercising OCL fairly successfully provides encouraging indications for EMF, UML2, Xtext. Do you want provisional entries for these projects? Regards Ed Willink ---

Re: [cross-project-issues-dev] Guava 15/21 warning

Hi Andreas Great, you sound like an expert who has demonstrated a solution. Can you contribute a wiki page on how you do it? Can you identify what checks a SimRel report should do to detect projects that are doing it wrong? Regards Ed Willink On 14/03/2017 14:21, Andreas Sewe

Re: [cross-project-issues-dev] Guava 15/21 warning

ange. I started this thread to highlight the risk that the nightmare we had between Luna RC1 to RC3 could recur. For Luna RC4, everyone tolerated Guava 15.) Regards Ed Willink On 14/03/2017 14:37, Gunnar Wagenknecht wrote: Ed, I think a single global bug as well as cross-project

Re: [cross-project-issues-dev] Guava 15/21 warning

have a demonstrable solution with associated tooling, I feel we need to stick with the Luna 'solution'; all project's Guava dependency bounds include at least an agreed version and only that version is bundled, so only that version is used in practice. Regards Ed Wi

Re: [cross-project-issues-dev] Guava 15/21 warning

o distinct component projects with Guava in the APIs. So Mylyn only is no problem, but something that integrates Mylyn and Xtext can encounter obscure failures when the wrong class is re-used on a code path in which both are used. Regards Ed Willink On 14/03/2017 13:08, Andreas Sewe wro

[cross-project-issues-dev] Guava 15/21 warning

?id=437107 is open to identify a policy for non-singleton plugins, but no resolution has been found. We can probably avoid problems if we all move to Guava 21 for M7 and if Mylyn refrains from contributing its change at M6. Regards Ed Willink --- This email has been checked for

Re: [cross-project-issues-dev] Java 9 Readiness

se of Java 9 as Java 8 today seems unreasonably hard. Regards Ed Willink On 14/03/2017 08:20, Ed Merks wrote: Ed, This just seems downright rude to me. There's simply no need to be snarky. I suspect you're not actually confused, you're just being deli

Re: [cross-project-issues-dev] Java 9 Readiness

invoking Eclipse JVM. So no Java 9 in Eclipse => no testing. Regards Ed Willink On 13/03/2017 20:06, Daniel Megert wrote: Hi Ed It depends whether you want to run the tests from the command line or out of the IDE. From the command line you only need a Java 9 VM (e.g. the

Re: [cross-project-issues-dev] Java 9 Readiness

Hi I'm confused again. You previously replied that it was necessary to install a special JDT so that a Java 9 JDK was available within Eclipse. I see no mention of this in the wiki. Without doing this how can tests be run using Java 9? Regards Ed Willink On 13/03/2017

Re: [cross-project-issues-dev] Problems with Simrel contributionre: org.eclipse.e4.ui.model.workbench

e to fix rather than ripple the major version bug. To accommodate the wrong M6 version, consumers may need to widen to a [1.0.0,3.0.0) dependency bound for M6 and possibly M7 reverting back to [1.0.0,2.0.0) at RC1. Or just no bound at all as I suspect a few projects have done. Regards

Re: [cross-project-issues-dev] Bugzilla seem to be down again

ote/factory.php line: 239 function: create_committer_vote_objects Regards Ed Willink On 12/03/2017 14:46, Andrey Loskutov wrote: Yep. Now even www.eclipse.org reports "Unable to connect to the database server at this time." Am 12.03.2017 um 15:10 schrieb Pierre-Charles David:

Re: [cross-project-issues-dev] Problems with Simrel contributionre: org.eclipse.e4.ui.model.workbench

revise your code to avoid the major version, not just throw a major version to make the irritating error go away. Note also again that major version chnages should be announced so that consumers and experts have an opportunity to comment in a more timely fashion. Regards Ed Willink

Re: [cross-project-issues-dev] Problems with Simrel contribution

Hi Correction. I misread the icons in the Plugin dependency view. Nothing in my workspace re-exports org.eclipse.e4.ui.model.workbench, so a major version change should be a simple MANIFEST.MF update for consumers. Regards Ed Willink On 11/03/2017 08:58, Ed Willink wrote: Hi

Re: [cross-project-issues-dev] Problems with Simrel contribution

. Regards Ed Willink On 11/03/2017 08:19, Eike Stepper wrote: Hi, It appears that https://git.eclipse.org/r/#/c/88492/ incremented the major version of the org.eclipse.e4.ui.model.workbench plugin. There are some other commits in the context of https://bugs.eclipse.org/bugs/show_bug.cgi

Re: [cross-project-issues-dev] Will Your Project Work When Running on Java 9?

ithin Eclipse. Regards Ed Willink On 08/03/2017 10:18, Ed Merks wrote: Dani, Yes, though you definitely need that if you want to use Window -> Preferences -> Java -> Installed JREs to be able to point to a Java 9 JDK; as you know that just doesn't work without JDT's Java 9 supp

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

g repos or GIT, presumably the network, crawls. Regards Ed Willink On 05/02/2017 14:24, Stephan Herrmann wrote: Could this be a general issue? The factor of 4 looks similar to what I see in hipp10 (Object Teams). Some figures: Two individual test suites A and B as part of the Ob

[cross-project-issues-dev] Are secondary update sites harmful?

ify their update sites? Regards Ed Willink --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change

Re: [cross-project-issues-dev] Projects that have not (AFAICT) declared participation in Oxygen

procedues, merging EMFq into a composite EMFt/EMFv (? EMF Tools) project should incur very little extra effort. Regards Ed Willink On 15/12/2016 13:00, Cédric Brun wrote: Hi, We are currently looking for future proof solutions to secure EMF Transaction, Validation, GMF Notation

Re: [cross-project-issues-dev] Are restrictions on Bugzilla worse thanspam?

lack of response at weekends. Maybe even an RSS feed. Regards Ed Willink On 14/11/2016 15:51, Matthew Ward(Bt. Kt. SSA.) wrote: With all due respect (and you know I do :) ), I have counter examples on how effective it is, at least lately, where a CDT committer still

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

Hi Intermittent from near London too. Regards Ed Wilink On 14/11/2016 08:16, Christian Campo wrote: Interesting enough the downforeveryoneorjustme changes its status nearly each and every time I call the page from UP to DOWN Von: > o

Re: [cross-project-issues-dev] Papyrus contribution to Oxygen M3

t the major version ripples could be resolved. Generally any major version change breaks the build until consumers update. It is also worth making a lot of noise on cross-project-dev so that consumers are awake and react before there is a problem. Regards Ed Willink On 02/11/20

Re: [cross-project-issues-dev] Git servers not working well?

Hi Yes. Seems ok now. Do we have any idea what caused the failures? Unless you have fixed something, the need for multiple restarts suggests a hostile attack. Regards Ed Willink On 31/10/2016 10:49, Frederic Gurr wrote: It seems to have stabilized now. On 29.10.2016 20:07

Re: [cross-project-issues-dev] Git servers not working well?

Hi With the OCL HIPP, I can usually (75% success) get one build after restarting before the GIT connection fails again. Regards Ed Willink On 29/10/2016 00:04, Matthias Sohn wrote: EGit HIPP is again broken, restarting it didn't help to regain access to git.eclipse.org

Re: [cross-project-issues-dev] Upgrading HIPPs to SLES12 (Part 2 - reloaded)

Hi See https://bugs.eclipse.org/bugs/show_bug.cgi?id=501853#c12 Regards Ed Willink On 24/10/2016 14:36, Matthias Sohn wrote: It seems the upgrade broke EGit UI tests since the window manager metacity which we used so far can't be found anymore and UI tests can't run

[cross-project-issues-dev] GLIBC_2.14 not found by org.eclipse.pde.core

promotion perhaps urgent action is required. Regards Ed Willink --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ cross-project-issues-dev mailing list cross-project-issues-dev@ecli

Re: [cross-project-issues-dev] Must all changes be tracked by a bug?

Hi Your checker could allow some reserved non Bug id prefixes such as: [typo] [releng] [unrelated] ... Regards Ed Willink On 02/09/2016 08:39, Daniel Megert wrote: Having a bug for trivial things, like e.g. fixing a typo, is just overkill. I would rather not fix it than waste

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

mptly. Regards Ed Willink On 10/08/2016 14:38, Marc Khouzam wrote: Then what we can do is enable both CDT and PTP in the same contribution. I'll push a path to Gerrit to see how that goes. *From:* cro

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

your initiative. Regards Ed Willink On 10/08/2016 10:08, Wenz, Michael wrote: Hi, Ed, thanks for enabling EMF Validation, that brings me one step closer to being able to enable Graphiti as well. Can anybody shed any light on the status of EMF Transaction? That is my last

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

Hi I had to use my initiative to enable EMF Validation. Aggregation build now looks promising. With EMF, EMFv, GEF, OCL, UML2, Xpand, Xtext contributed, perhaps the worst dependency cycles are now broken. Regards Ed Willink On 10/08/2016 09:23, Ed Willink wrote: HI I have

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

HI I have authority to enable UML2 with its Neon.0 contribution, so UML2 is now enabled. OCL coming as soon as the aggreagtion build status clarifies. Regards Ed Willink On 10/08/2016 08:42, Dennis Hübner wrote: Hello Alex, I’ve enabled EMF, Xpand and Xtext in Oxyden. There are

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

hould notify dependencies that we are waiting. Are you joking? Why should I waste my time and EMF's time by suggesting that it is about time for them to contribute. EMF is a -1/+1 contribution. Of course it should know that it should contribute. Regards Ed Willink On 09/08/

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

Xtext. Regards Ed Willink On 09/08/2016 14:55, Kaloyan Raev wrote: I really miss the root cause of the issue... I don't understand how does it help breaking the SimRel build now and hoping everything will be fine by the end of tomorrow. As far as I understand, there

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

Ed Willink On 09/08/2016 13:27, Kaloyan Raev wrote: Hi Ed, Can't all these projects coordinate and make the necessary contributions within a short time frame without leaving master broken for a long time? It's already M1 +2 date and the rest of the projects should be a

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

the missing contributions are highlighted. AFAIAA all OCL's dependencies have declared intent so OCL can be enabled and that is what I have done. Regards Ed Willink On 09/08/2016 13:09, Kaloyan Raev wrote: Hi folks, I don't want to break the party, but your rece

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

27;ll enable OCL so that things improve as soon as XText and friends appear. Regards Ed Willink On 08/08/2016 18:27, David M Williams wrote: > Can we have the Neon contributions available as in previous years? Projects can do that, if they want -- as long as it is still "fit

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

features with the required granularity, so the multiple contributions should be just a matter of different feature selections from a single build repo. However the extra modularity would show in the P2 catalog. Perhaps that would be an improvement too. Regards Ed Willink On 08/08

Re: [cross-project-issues-dev] GEF Oxygen M1 contribution only partially today

announced participation, surely it would be better to apply it just after M2 to all projects that have made no SimRel commit since Neon? Regards Ed Willink On 08/08/2016 16:34, Alexander Nyßen wrote: Hi all, I have just re-enabled the GEF repository for Oxygen and made available the Ne

Re: [cross-project-issues-dev] Graphiti participating in Oxygen

Hi Comments inline. Regards Ed Willink On 18/07/2016 16:42, Doug Schaefer wrote: The +# days thing has never made sense, really. If you really chain dependencies I’m sure you’d get into double digits. In fact, CDT cycles on itself with a couple of other projects. It'

[cross-project-issues-dev] OCL and QVTd participation in Oxygen

+3: https://projects.eclipse.org/projects/modeling.mmt.qvtd/releases/1.0.0-oxygen Regards Ed Willink --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ cross-project-issues-dev mailing list cro

Re: [cross-project-issues-dev] Respin of SimRel Repository required

pdate from ZIP needed to resolve this preferring to report a plethora of ambiguities from stale update sites contributed by projects. But for a SimRel upgrade, all the replacements should be there, so surely replace and evict should just work? Regards Ed Willink On 16/06/201

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

Thanks Ed On 05/06/2016 14:48, Ian Skerrett wrote: Markus and everyone else, I hear you and agree we need to remove the UUID in Neon. I will put a statement to this effect on the bug you opened. It is obvious there is a lot more discussion needed around this issue. My apologies to Pas

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

have the UUID facility removed pending a more acceptable realization? Regards Ed Willink On 03/06/2016 16:13, Ian Skerrett wrote: All, I wanted to make everyone aware that a UUID has been added to the Eclipse Platform [1] and is available in the current Neon RC. This

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

an opt-out since the opt-out cannot easily be made till after an opt-in has been in place for minutes if not days. (I cannot edit a file to be uuid=0 until Eclipse startup has created the file and no doubt done an initial communication with some server.) Regards

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

g with an opt-in for anything that even slightly impinges on privacy. If this cannot be done at a platform-only RC5, then I feel that it should wait till Neon.1. I hope the EF will learn from this and treat committers and users with more respect in future. Regards Ed Willink On 0

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

default opted in? Regards Ed Willink On 04/06/2016 06:50, Christian Campo wrote: hi is that a last minute idea that came up recently or why is it only revealed now that is pretty much too late for any change ? Gruß Christian Am 03.06.2016 um 17:13 schrieb Ian Skerrett

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

Hi What is to stop some HTML malware farming user-name/Eclipse-UUID pairs for alternative purposes? The user may be anonymous to Eclipse but not to others. Regards Ed Willink On 03/06/2016 16:13, Ian Skerrett wrote: All, I wanted to make everyone aware that a UUID has been

Re: [cross-project-issues-dev] Fwd: Change 73676 insimrel/org.eclipse.simrel.build[master]: Update PTP to RC2

pled to an RC1/RC2 Mylyn change.) Regards Ed Willink On 26/05/2016 10:03, Mickael Istria wrote: On 05/26/2016 10:53 AM, Ed Willink wrote: We have perhaps 30 projects that depend on EMF. If - each project specifies a precise 4-part EMF version dependency Project should simply not do t

Re: [cross-project-issues-dev] Fwd: Change 73676 insimrel/org.eclipse.simrel.build[master]: Update PTP to RC2

- EMF's consumers trust that EMF will be well-behaved API-wise and so have a weaker than 4-part dependency Just imagine a 4-part dependency on the platform, and perish the thought that the platform might respin with an "a" contribution... Regards Ed Willink On 2

Re: [cross-project-issues-dev] Fwd: Change 73676 insimrel/org.eclipse.simrel.build[master]: Update PTP to RC2

not suggestion, for SimRel participation. Regards Ed Willink On 26/05/2016 01:12, David M Williams wrote: > ... Does anyone know why, or how to fix it? My EGit contacts have not responded to my mail. Or a classic case of "committing, then going home" :) Or at least a cla

[cross-project-issues-dev] QVTd 0.13.0 rather than 1.0.0

propose to revert to 0.13.0RC1 tomorrow despite a 1.0.0M7 contribution a couple of weeks ago. Is this a problem for anyone? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your

Re: [cross-project-issues-dev] On the issue of building with thelatest Orbit repository

bundles Orbit facilities avoiding the need for users to learn how to include Orbit in the available sites. Regards Ed Willink On 05/02/2016 17:33, Konstantin Komissarchik wrote: I would advise strongly against using the feature includes directive for Orbit bundles. While doing so

Re: [cross-project-issues-dev] On the issue of building with the latest Orbit repository

useful and could help you enforce limited usage. Regards Ed Willink On 04/02/2016 21:35, David M Williams wrote: Off the top of my head, I think features are suppose to 'include' them, since that is the only way to have a reproducible build or install. If it was left u

Re: [cross-project-issues-dev] On the issue of building with the latest Orbit repository

HI "commons.collections" doesn't seem that well used. No version of it is my workspaces, so QVTd, (Xtext, EGIT, UML, QVTo, OCL) cannot have a dependency on it. No re-contribution needed. Regards Ed Willink On 04/02/2016 20:19, David M Williams wrote: Ed, Than

Re: [cross-project-issues-dev] Ready for Mars.2 ?

n of Orbit (R20151221205849). But if a project has no maintenance to contribute, I thought no rebuild/contribution was required and so of course an old Orbit would be in use. (I don't think that QVTd imposes tight bounds on Orbit contributions.) Regards

Re: [cross-project-issues-dev] Enforce Gerrit for Simrel?

Hi Or just cache the checksum. Regards Ed Willink On 11/01/2016 18:55, Sam Davis wrote: Even if fully-qualified versions are used, is there anything to stop someone from rebuilding bundles with changed content but reusing the same version and qualifier? This is bad practice but

Re: [cross-project-issues-dev] Enforce Gerrit for Simrel?

Hudson is down. IMHO given build-specific repos, the version range is redundant clutter and arguably the source of much of this trouble. Regards Ed Willink On 08/01/2016 21:44, Mickael Istria wrote: On 01/08/2016 07:13 PM, Eike Stepper wrote: Am 08.01.2016 um 17:29 schrieb Marc Khouzam: I

Re: [cross-project-issues-dev] Enforce Gerrit for Simrel?

build. Regards Ed Willink On 08/01/2016 16:29, Marc Khouzam wrote: I also would not like to have to change versions. Changing the URL only allows me to change one line quickly. Changing each version of each feature group is more work and more error prone. And when speaking about

Re: [cross-project-issues-dev] Partially signed OCL M4 contribution

Hi Two days later, the signer seems ok again. OCL M4a contribution contributed. Regards Ed Willink On 15/12/2015 11:03, Ed Willink wrote: Hi https://bugs.eclipse.org/bugs/show_bug.cgi?id=484379 The OCL M4 contribution is only partially signed. I tried another build and it is

[cross-project-issues-dev] Partially signed OCL M4 contribution

Hi https://bugs.eclipse.org/bugs/show_bug.cgi?id=484379 The OCL M4 contribution is only partially signed. I tried another build and it is differently partially signed. Is anyone else seeing similar problems? Has anyone got a solution? Regards Ed Willink

Re: [cross-project-issues-dev] 1000 line limit for contributions

Hi Presumably you put tests in a separate plugin, so splitting off the tests as a separate contribution gets you twice the limit with minimal effort. Perhaps a 1 line limit might be appropriate for non-deliverable code such as tests and build tools. Regards Ed Willink

Re: [cross-project-issues-dev] EMF 2.11 milestones update site problem?

Hi See https://bugs.eclipse.org/bugs/show_bug.cgi?id=481766 2.11 was Mars. 2.12 is Neon, so the 2.11 milestone repo is obsolete. Regards Ed Willink On 18/11/2015 09:03, Andrey Loskutov wrote: Hi, my platfrom UI gerrit builds [1, 2] fail due: [INFO

Re: [cross-project-issues-dev] JDK 9 Early Access with Project Jigsaw

Hi It worked for me just specifying path/*.jar in my Eclipse installation folder. It showed the expected SWT_AWT anomally, and also 5 suspect calls from com.google.guava 18. Regards Ed Willink On 17/11/2015 17:13, Eike Stepper wrote: Hi Wayne, I downloaded that JDK and tried

Re: [cross-project-issues-dev] DTP major version bump for Neon

them.) Regards Ed Willink On 28/10/2015 15:24, Konstantin Komissarchik wrote: > potentially no impact on most consumers of your API And here lies the crux of our disagreement. I take an absolute position on this issue. Potentially not breaking a consumer with an exis

Re: [cross-project-issues-dev] DTP major version bump for Neon

have minimal maintenance teams. In some cases useful but unmaintained tools, such as UML2 Tools, are killed by the major version change. Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To c

[cross-project-issues-dev] QVTd in Neon

Hi QVTd will contribute 1.0.0 to Neon at offset +3. https://projects.eclipse.org/projects/modeling.mmt.qvtd/releases/1.0.0-neon Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change

[cross-project-issues-dev] OCL in Neon

Hi OCL will contribute 6.1.0 at offset +1 to Neon. https://projects.eclipse.org/projects/modeling.mdt.ocl/releases/6.1.0-neon Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change

Re: [cross-project-issues-dev] AERI conclusions after 3 weeks of Mars.1

, but you could normalize to the number of reporting users. Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this

Re: [cross-project-issues-dev] Java 7 is dead:

Hi I see no real problem. I was just highlighting that Java 8 time had finally come, hopefully saving others time in debugging new failures. Regards Ed Willink On 07/10/2015 16:34, Daniel Megert wrote: Hi Ed As mentioned in my announcement, the appendix with the BREEs will

Re: [cross-project-issues-dev] Git doesn't work with IOException: End of IO Stream Read

Hi I suspect that your upgrade, like mine, resulted in com.jcraft.jsch 0.1.51 and 0.1.53 'co-existing'. They don't. You might try forcibly eliminating 0.1.51. Much safer to start with a clean new Eclipse installation. Regards Ed Willink On 04/10/2015 12:57,

Re: [cross-project-issues-dev] Java 7 is dead:

Hi Lars As of a couple of minutes ago that plan [1] lists only the anomalous jdt.annotation as a Java 8 minimum version. Since that was the case six weeks ago too, I assumed that Java 8 BREE would not actually occur for most plugins. Regards Ed Willink [1] https

[cross-project-issues-dev] Java 7 is dead: (was: jdt.core move to Java 7 BREE)

Hi I didn't see any announcement, but there was little dissent in earlier discussions. In M2, org.eclipse.core.jobs has moved to Java 8 BREE so to all intents and purposes Java 7 support is dead. Regards Ed Willink On 07/03/2015 22:54, Lars Vogel wrote: On Wed, Mar 4,

Re: [cross-project-issues-dev] Git outage?

HI I'm seeing the problem on a Neon M1 with EGit 4.0.1 installation, jsch 0.1.51 Some GIT repos have stopped working on or after 27-Sep. Others continue to work fine. The problem must be at the Eclipse GIT server end. Regards Ed Willink On 29/09/2015 18:08, Matthias

Re: [cross-project-issues-dev] Git outage?

Hi Ah! I thought it was just my magic fingers. I consistently see this on ssh://ewill...@git.eclipse.org/gitroot/www.eclipse.org/modeling/mdt.git ssh://ewill...@git.eclipse.org/gitroot/www.eclipse.org/mmt.git but other repos are ok. Regards Ed Willink On 29/09/2015 15:25

Re: [cross-project-issues-dev] Maintenance builds (was Announcing a one week slip in the Mars.1 release (from 9/25 to 10/2))

rather than the full RC* run-down. Regards Ed Willink On 24/09/2015 19:09, Doug Schaefer wrote: No, maintenance releases are still necessary. But you have to ask yourself, why are we synchronizing them. I think on another thread here we have the solution. Projects need to be

[cross-project-issues-dev] Maintenance builds (was Announcing a one week slip in the Mars.1 release (from 9/25 to 10/2))

have observed maintenance discipline suffer. Regards Ed Willink On 24/09/2015 15:35, Ian Bull wrote: Ed, The reason for the change from Mars SR1 to Mars 1 is because this is how we've been doing it for years. Many people (EGit / JGit, Mylyn, CDT -- to name a few) had been pu

Re: [cross-project-issues-dev] Announcing a one week slip in the Mars.1 release (from 9/25 to 10/2)

.1 pulls in B.1, but C uses B, users of C are in a mess until they get C.1. Regards Ed Willink On 24/09/2015 05:26, Gunnar Wagenknecht wrote: David, Am 23.09.2015 um 23:37 schrieb David M Williams : If not obvious, this means all participants in "coordinated release

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

ill find rumor-based usage instructions such as: Make sure you pick up EGIT from Mars.1 Make sure you do not pick Buildship Nobody will know what they're doing and as committers we will have much greater difficulty discovering user's configurations. Regards Ed Willi

Re: [cross-project-issues-dev] Eclipse Mars 1 RC4 issue with Buildship / workspace prompt

risk, and conversely the non-fix has high reputational impact. +1 for a respin. Regards Ed Willink On 23/09/2015 11:08, Martin Lippert wrote: Hey! Strong +1 for a re-spin. Cheers, -Martin Am 23.09.2015 um 12:04 schrieb Simon Scholz : Hi, the steps to reproduce the issue a

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

ature changes with the first plugin. If different plugins change every milestone, you maximize difficulties for consumers. Much better to go for 5.x outright and we all take the hit just once. Regards Ed Willink On 14/09/2015 16:02, Ian Bull wrote: I may be wrong, but I don't

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

three years allowing API clean up. Other projects will be more or less forced to synchronize which will be a nuisance, but also a benefit, since they too can clean up their APIs. Let Neon be versioned as 5.0.0 and we can all clean up. Regards Ed Willink On 14/09/2015 08:31, Ed Merks

Re: [cross-project-issues-dev] Unannounced Changes Have Unforeseen Consequences

%2Fporting%2Fremovals.html so the discussed removal in https://bugs.eclipse.org/bugs/show_bug.cgi?id=475944 seems premature. Regards Ed Willink On 12/09/2015 09:05, Ed Merks wrote: Hi, It was brought to my attention that org.eclipse.jface.viewers.TableTreeViewer has been deleted. Yes

[cross-project-issues-dev] QVTd in Neon

Hi QVTd will contribute 1.0.0 to Neon at offset +3. Regards Ed Willink ___ 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

[cross-project-issues-dev] OCL in Neon

Hi OCL will contribute 7.0.0 at offset +1 to Neon. (The Classic Ecore OCL plugins will only have a minor version increment.) Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your

[cross-project-issues-dev] Guava for Mars and Neon (was What are the rules for Mars SR1 contributions)

Milestones and Releases. Regards Ed Willink On 13/08/2015 12:22, Tom Schindl wrote: Hi, Are there any rules regarding what version a project can contribute to SR1. In SR0 e(fx)clipse contributed 2.0.0 and now we'd like to contribute 2.1.0 to SR1. Is this allowed? Another thin

Re: [cross-project-issues-dev] Error reporter and third-party code

Hi I agree. I think that the Eclipse-is-buggy hazard can be mitigated by ensuring that any pop-up on behalf of a third party has a prominent logo for that third party in the dialog. It may be a good idea for Eclipse project logos to have similar prominence. Regards Ed Willink

Re: [cross-project-issues-dev] Error reporter and third-party code

one accidental answer and Eclipse becomes leaky. Persisting only until the next Eclipse restart seems like a good idea. Regards Ed Willink On 22/07/2015 22:39, Marcel Bruch wrote: My proposal:… Sounds okay to me. I wonder if the short cut „not to enable 3rd party class names in

Re: [cross-project-issues-dev] Remote debug on a HIPP

Hi It's awkward. We have a Wiki page, in which some of the obscure problems we encountered are identified and where some relevant log files are. http://wiki.eclipse.org/OCL/Dev/Releng/Issues_Documentation Regards Ed Willink On 08/07/2015 09:09, Axel RICHARD wrote: Hi, I

Re: [cross-project-issues-dev] Signer failure - OCL RC4 late

Hi OCL RC4 built and signed. Contribution imminent. Thanks Mikael. Regards Ed Willink On 09/06/2015 06:32, Ed Willink wrote: Hi https://bugs.eclipse.org/bugs/show_bug.cgi?id=469672 Regards Ed Willink On 08/06/2015 22:53, Ed Willink wrote: Hi The signer appears

Re: [cross-project-issues-dev] Signer failure - OCL RC4 late

Hi https://bugs.eclipse.org/bugs/show_bug.cgi?id=469672 Regards Ed Willink On 08/06/2015 22:53, Ed Willink wrote: Hi The signer appears to have failed. Its log file claims that it cannot access the jarprocessor. Consequently I cannot get OCL's RC4 contrbution s

[cross-project-issues-dev] Signer failure - OCL RC4 late

Hi The signer appears to have failed. Its log file claims that it cannot access the jarprocessor. Consequently I cannot get OCL's RC4 contrbution signed. Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-i

Re: [cross-project-issues-dev] Is it time to update to Guava 18?

Hi If you think Guava 18 is a good idea for Neon, I suggest starting to make a lot of noise at M1 so that most projects migrate for M2. Regards Ed Willink On 25/05/2015 18:10, Sam Davis wrote: Hi, Looking in releases/mars/201505221000/plugins/ I see only Guava 15. If I

[cross-project-issues-dev] QVTd 1.0.0 / 0.12.0

be delayed. QVTd has so far contributed 0.12.0M1,M2,M3,M4 then 1.0.0M5,M6 to the Mars SimRel. In the absence of adverse comments, M7 will revert to 0.12.0 again. Since QVTd is a 'leaf' project, I don't expect this negative version change will affect anyone. Re

Re: [cross-project-issues-dev] Notice of change to batch "signing service"

Hi Given David's comment, I presume that Buckminster is an example of a build system that does use the batch signing service. So even if Buckminster was changed today, the batch signing service is needed for another couple of years. Regards Ed Willink On 17/04/2015

Re: [cross-project-issues-dev] Notice of change to batch "signing service"

Hi See https://bugs.eclipse.org/bugs/show_bug.cgi?id=464594 It looks as if some inconsistently hashed/signed bundles are working their way through magic caches. Try a maximal clean. Regards Ed Willink On 15/04/2015 08:58, Tom Schindl wrote: Hi, And now the build is completely

Re: [cross-project-issues-dev] Notice of change to batch "signing service"

ng by unpack200 xxx.pack.gz xxx.jar jarsigner -verify xxx.jar Bad files report a SHA1 digest failure. Regards Ed Willink On 11/04/2015 08:58, Alexander Nyßen wrote: David, I admit I am not very acquainted with the internals of signing and pack200. However, we are using Tycho for our b

Re: [cross-project-issues-dev] Status and Outlook for M6

acked. Regards Ed Willink On 25/03/2015 17:36, David M Williams wrote: Well, we finally got a green build a few hours ago so that I was able to promote a new 'staging' repository. Those of you who are "done" should verify it is as you expect. And, still 5 hou

<    1   2   3   4   5   >