Re: [cross-project-issues-dev] Critical projects?

Another thought https://www.zdnet.com/article/for-security-alone-we-could-try-paying-open-source-projects-properly/ ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit

[cross-project-issues-dev] Critical projects?

Hi Simrel folks, As the lead of long-time participant project (ECF), I've personally experienced (as well as watched in horror) the problem of diminishing maintenance resources that now seems endemic to simrel projects and to the simrel itself. I heard that yesterday there was a meeting at

Re: [cross-project-issues-dev] jarsigner/build.eclipse.org

Thanks Thomas. On 9/24/2021 12:44 PM, Thomas Wolf wrote: On 24.09.21 21:39 , Scott Lewis wrote: Howdy, I'm sure this is just me not paying attention to recent cbi/infra changes, so my apologies in advance. See https://www.eclipse.org/lists/cross-project-issues-dev/msg18545.html . [INFO

[cross-project-issues-dev] jarsigner/build.eclipse.org

Howdy, I'm sure this is just me not paying attention to recent cbi/infra changes, so my apologies in advance. Our long-standing build has begun failing in jarsigner with these errors (no comm with build.eclipse.org): [INFO] [INFO] --- tycho-source-feature-plugin:1.7.0:source-feature

Re: [cross-project-issues-dev] 2021-06 Participating Projects List

Hi, ECF is going to release 3.14.21 rather than 3.14.20. Scott On 5/26/2021 7:07 AM, Wayne Beaton wrote: I believe that I've made all of the updates requested to the 2021-06 Release page. Please let me know if I've missed anything. Wayne On

Re: [cross-project-issues-dev] httpclient5/jna5 vs. httpclient45/jna45 in Eclipse and Simrel

/show_bug.cgi?id=566100#c27 On 5/13/2021 5:22 PM, Scott Lewis wrote: Howdy, Some time ago, ECF was requested to update to use httpclient/httpcomponents 5 rather than 4.5 [1], so that JNA 5 could be used rather than JNA 4.5. For context, ECF filetransfer depends on 3 apache bundles from Orbit

[cross-project-issues-dev] httpclient5/jna5 vs. httpclient45/jna45 in Eclipse and Simrel

Howdy, Some time ago, ECF was requested to update to use httpclient/httpcomponents 5 rather than 4.5 [1], so that JNA 5 could be used rather than JNA 4.5. For context, ECF filetransfer depends on 3 apache bundles from Orbit:   org.apache.httpcomponents.httpclient 4.5.10,

[cross-project-issues-dev] httpclient update to 4.5.13

Howdy, FYI:  There's been a request for ECF to update to httpclient version 4.5.13, newly added to Orbit (currently at 4.5.12) [1] This will very likely be the version in 2021-06 (Eclipse and simrel). If any objections or concerns please note on [1]. Scott [1]

[cross-project-issues-dev] Removal of JNA dependency

Howdy, Some time ago Jonah opened this issue [1].   After some analysis a fix has been proposed here [2]. The fix removes the dependency completely...which seems to me a reasonable thing to do.   However, Carsten Reckford contributed this code and he doesn't seem to be responding to

Re: [cross-project-issues-dev] updating httpcomponents to 5.0.2 for JGit/EGit

I haven't worked with httpcomponents 5 yet, but the major segment change from 4-5 could of course signal some non-backward-compatible changes. It's going to take some resources allocation to check for and fix any such required changes...and test of course...in ECF filetransfer/p2. It may

Re: [cross-project-issues-dev] org.apache.commons.codec

ontent and valid licenses" phase; we're darned close though!  Coordinating the common components will be much more challenging, and I expect it will not actually happen until the problems it causes rears its ugly head to the end-users. Regards, Ed On 26.02.2020 00:54, Scott Lewis w

Re: [cross-project-issues-dev] org.apache.commons.codec

ECF updates httpclient/httpcomponents and deps (e.g. codec) in response to explicit requests from platform...e.g. [1] in this case. I'm not sure how to effect in terms of process, but it might be good for other release train projects that consume httpclient (e.g. egit) if somehow the platform

Re: [cross-project-issues-dev] Downstream Projects of platform to take note - ECF Upgrade in platform

Filetransfer providers may be disabled at start time via a system property [1]. [1] https://wiki.eclipse.org/Disabling_Apache_Httpclient45 On 5/28/2019 12:54 AM, Daniel Megert wrote: But wouldn't that mean that (affected) clients have to change their code? Dani From: Scott Lewis

Re: [cross-project-issues-dev] Downstream Projects of platform to take note - ECF Upgrade in platform

On 5/27/2019 6:52 AM, Daniel Megert wrote: Hi Scott I assume that shipping the older httpClient version in addition, would not resolve those issues and that it is something that would have to be changed/fixed in ECF. Correct? I believe that the older provider (httpclient4) would resolve

Re: [cross-project-issues-dev] Simultaneous Release 2019-06 opt-in

Hi Wayne, ECF expects to contribute a version 3.14.5 [1] next week. Scott [1] https://projects.eclipse.org/projects/rt.ecf/releases/3.14.5 On 5/8/2019 1:04 PM, Wayne Beaton wrote: Greetings Simultaneous Release 2019-06 participants. Per our process, I have started to assemble the

[cross-project-issues-dev] httpclient version for SR

Folks, A new provider has been offered to ECF [1] that solves several of the proxy issues experienced with the apache httpclient provider [2] in some environments. This provider is dependent upon at least versions 4.5.6 of httpclient and 4.4.10 of httpcore.    Consequently, ECF is preparing

Re: [cross-project-issues-dev] Update to httpclient/httpcore in ECF/Platform

ECF has contributed httpclient/httpcore 4.5.5/4.4.9 for the 2018-09 release as per [1]. Because of past problems with multiple versions of these bundles, all SR projects that depend upon httpclient/httpcore directly will need to use Orbit version 4.5.5/4.4.9 as well. Scott [1]

Re: [cross-project-issues-dev] Fwd: Re: Update to httpclient/httpcore in ECF/Platform

On 7/17/2018 10:28 PM, Ed Willink wrote: Hi (Your message does not seem to have been sent out from the mailing list; just the forum/archive.) You refer to Photon.1 SR. Presumably you mean 2018-09 since maintenance releases have now been abandoned. Please forgive me.   I have name

Re: [cross-project-issues-dev] Update to httpclient/httpcore in ECF/Platform

On 7/13/2018 9:56 AM, Scott Lewis wrote: The versions Mat proposes: org.apache.httpcomponents.httpclient  4.5.5     org.apache.httpcomponents.httpcore   4.4.9 Are the most recent versions in Orbit [1].   This bug [2] was opened for ECF and then subsequent Platform adoption

Re: [cross-project-issues-dev] Update to httpclient/httpcore in ECF/Platform

On 7/13/2018 2:19 AM, Ed Willink wrote: Hi My recollection is that there is a very strong expectation that all SimRel projects build against the latest available version in Orbit. Surely this correspondence should therefore just be a notification that new Orbit versions are available and

[cross-project-issues-dev] ECF participation in 2018-09 simrel

ECF will participate in 2018-09 release with offset -1 for filetransfer and +1 for remote services and etc. Not certain yet what the new version will be, but anticipate 3.14.1 (Photon was 3.14.0). Scott ___ cross-project-issues-dev mailing list

Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

Hi Aleksandar, >It is recommended that projects update the Orbit repo they use to build for each milestone. That would have catched the issue > and it would be nice if ECF does so from now on. Perhaps it would be nice, but I'm not going to do it.   Since this is a free service provided by

Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

On 6/13/2018 7:48 AM, Aleksandar Kurtakov wrote: On Wed, Jun 13, 2018 at 10:00 AM, Matthias Sohn mailto:matthias.s...@gmail.com>> wrote: Are 2 months not enough to validate a new version ? From my chair it's plenty...but as I suspect all are aware there's more to it than that.

Re: [cross-project-issues-dev] Heads up: multiple HttpClient versions in simrel

WRT ECF: For Photon, the Platform folks chose to stick with the Oxygen versions of httpclient/httpcomponents (4.5.2/4.4.6).  One reason was that the new Orbit bundles were added fairly late in the release cycle...leaving little time...and no milestone releases...for thorough testing of the

Re: [cross-project-issues-dev] Intent to update HttpComponents bundles

On 9/25/2017 9:16 AM, Aleksandar Kurtakov wrote: No component can go in Orbit before a project opens a CQ to get it in. Please do so for ECF and once legal approval is there, Mat will provide patches against Orbit. Aleksandr:   I'm going to ask that the projects that have been submitting CQs

Re: [cross-project-issues-dev] Intent to update HttpComponents bundles

On 9/25/2017 8:57 AM, Daniel Megert wrote: Hi Mat Two questions: 1. Can you confirm that there is no breakage and we can move to the new version without doing any work/investigation? Answering for ECF here.   Although historically Apache httpcomponents is generally pretty good about no

Re: [cross-project-issues-dev] Make sure you are committing to the right SimRel aggregation branch

On 9/4/2017 6:27 PM, Greg Watson wrote: Yes, I committed to the Oxygen_update branch when I discovered it wasn't included in RC2. me too Scott ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery

Re: [cross-project-issues-dev] Neon.3 Update Problems: To Fix and How to Fix?

I am not on planning council, and so have not been able to follow all the discussion, but just to be clear ECF has this open bug for Oxygen M7: https://bugs.eclipse.org/bugs/show_bug.cgi?id=513888 To meet this we have modified our own build to include these versions from Orbit:

[cross-project-issues-dev] ECF participation in Oxygen

ECF will be participating in Oxygen simultaneous release with offset -1 for filetransfer and +1 for remote services. Our planned release will be 3.15.0 Scott ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change

[cross-project-issues-dev] signing problems

Howdy, I have been trying to do a ECF 3.13.1 release build this weekend and it's been failing on signing. Here are parts of the logs for the last three attempts...first failed with End of IO Stream Read and the other two with timeouts. ant] [INFO] You can check signing status by tailing

[cross-project-issues-dev] ECF participation in Neon

ECF intends to participate in Neon. Best guess it that will be with ECF 3.13. Offset ECF filetransfer: -1 The rest of ECF (remote services, etc): +1 Scott ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change

[cross-project-issues-dev] usage data collection for RCP apps

Hi, My apologies for not paying attention, but is there anything of the Usage data collection work that could be used within an RCP app? (As opposed to Eclipse) If so, is there any experiences and/or documentation that could be shared? Thanksinadvance, Scott

[cross-project-issues-dev] question about moving up release date

Wayne appears to be inaccessible so I'll ask this list: Is it possible to edit/change (e.g. move up) a scheduled release in the meta-data editor? If so, how? Alternatively, I could delete the existing release and create a new one with the correct date, but I can't see a way to delete a

Re: [cross-project-issues-dev] Proxy Testing Tool?

On 6/9/2015 9:49 AM, Andreas Sewe wrote: stuff deleted Code Recommenders and the Automated Error Reporting use HttpComponents internally, either directly or through Eclipse Aether (in Code Recommenders' case). We use ECF *only* for our communication test, as we got the impression that ECF is

Re: [cross-project-issues-dev] Proxy Testing Tool?

For everyone's info, there's been a long discussion of what appear to be HttpComponents-based proxy difficulties on this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=422665 ECF (used for p2) has the ability to disable the default HttpComponents-based provider and use an JRE

Re: [cross-project-issues-dev] Fw: Proposed schedule for JDK 9

Mike, Could you or someone comment on Java 9 modularity (jsr 376) and it's compatibility with OSGi? Wayne appears to be on the experts group so maybe he knows what's happening there? Thanks, Scott [1] https://jcp.org/en/jsr/detail?id=376 On 5/5/2015 2:51 PM, Mike Milinkovich wrote:

[cross-project-issues-dev] ECF participation in Mars

ECF will be participating in the Mars Simultaneous Release. ECF Filetransfer is -1 (Platform dependency) and the rest of ECF (e.g. remote services) is +1 We plan to contribute version 3.10.0 [1]. Scott [1] https://projects.eclipse.org/projects/rt.ecf/releases/3.10.0;

Re: [cross-project-issues-dev] Luna marketing bullets

On 5/26/2014 12:49 PM, Wayne Beaton wrote: stuff deleted We've already had the discussion with the press regarding Java 8. I still think that it belongs on the list. While I'd like to keep ECF on this short list, I'm not sure how much hay we can make from it at marketing level. Ian is the

Re: [cross-project-issues-dev] Luna RC1 staging repo is complete.

Hi Stephan, For historical/releng reasons, part of ECF (core and filetransfer) could not be directly updated in Eclipse. Prior to Luna, it was necessary to patch Eclipse in order update these bundles. Over the past year, this problem has been dealt with through changes to the feature

Re: [cross-project-issues-dev] Luna RC1 staging repo is complete.

sorry [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=409787 On 5/22/2014 7:01 AM, Scott Lewis wrote: Hi Stephan, For historical/releng reasons, part of ECF (core and filetransfer) could not be directly updated in Eclipse. Prior to Luna, it was necessary to patch Eclipse in order update

Re: [cross-project-issues-dev] Luna RC1 staging repo is complete.

On 5/22/2014 10:33 AM, Stephan Herrmann wrote: Hi Scott, thanks for explaining. On 05/22/2014 04:01 PM, Scott Lewis wrote: ECF would like to continue supporting Kepler, however, and so we need to continue distributing the patch so that Kepler users can install ECF from the Luna repo

Re: [cross-project-issues-dev] Inconsistency between ECF bundle in Luna M7

It appears to me that this Equinox server feature: org.eclipse.equinox.server.p2.feature.group is defined to depend upon an older version of org.eclipse.ecf.identity bundle than the o.e.ecf.core.feature (which is in Luna). I think that the fix would be to have the more recent version of the

Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna

Hi, Sorry in advance if this is covered ground somewhere...but I can't seem to find it. For those projects that are still using the 'old way'...and therefore need to update the files by hand...I want to clarify what actually needs to be updated to meet these requirements...please correct if

Re: [cross-project-issues-dev] EF plans to raise awareness of Java 8 support

On 3/27/2014 12:37 PM, Mike Milinkovich wrote: On 27/03/2014 2:31 PM, Scott Lewis wrote: Would you include links (or other page) to j8-enabled features from other EF projects?...In my case it will be ECFs use of j8 with OSGi remote services [1]...but there are possibly other EF projects

Re: [cross-project-issues-dev] Question on Kepler SR1 release review

On 8/14/2013 3:15 PM, Doug Schaefer wrote: I don't remember that being the decision. Another thing that doesn't work with projects that want to ship more often and want to update the corresponding EPP package with that release. At the risk of overstating things, I don't think the Planning

Re: [cross-project-issues-dev] Source code in simrel aggregate repo

On 8/8/2013 9:53 AM, Konstantin Komissarchik wrote: I think this illustrates quite well the trouble of leaving such decisions to projects, without even providing guidance as to what's recommended. I agree, but I think it also highlights a) SR projects have different consumers...meaning

Re: [cross-project-issues-dev] Kepler is GO!

On 6/26/2013 6:53 AM, Tom Schindl wrote: Now this repo misses at least org.eclipse.ecf.provider.filetransfer.httpclient which was in the repo at this location at least until yesterday! I don't understand how that would be possible. ECF's own repo/aggregator contribution didn't change...and

Re: [cross-project-issues-dev] Kepler is GO!

On 6/26/2013 7:48 AM, David M Williams wrote: stuff deleted But, if ecf.core was supposed to include this too ... then ... not sure why that wasn't working. No, ecf.core is not supposed to include httpclient (or httpclient4). In fact, it would create a problem for us and our consumers if

Re: [cross-project-issues-dev] RC3 and Final Daze ...

ECF has fixed the about.html problems with bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=409989 I've updated the Kepler meta-data...too late for RC3 but fixed for RC4 obviously. Scott On 6/5/2013 11:58 AM, David M Williams wrote: Here we are, nearly at the end of RC3 (remember, staging

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

[1] http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=0a6bd70f1ee6d160dd3317f931e2c568c1247d61 On 3/20/2013 3:33 PM, Scott Lewis wrote: Hi David, For first time today I was just able to update the ECF b2aggrcon file (with ECF 3.6.0) [1]. Hopefully I didn't miss

[cross-project-issues-dev] signing question

Hi Folks, Until recently, (ECF) has been signing our plugins by 'pushing' our plugins to eclipse.org (built on our own builder machine...which is *not* running at eclipse.org). Apparently this is not the appropriate way now...rather what Denis indicated was appropriate was to have an