This list is closed, nobody may subscribe to it.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
|
Oct
(61) |
Nov
(88) |
Dec
(27) |
| 2010 |
Jan
(55) |
Feb
(93) |
Mar
(133) |
Apr
(148) |
May
(92) |
Jun
(56) |
Jul
(110) |
Aug
(28) |
Sep
(229) |
Oct
(93) |
Nov
(137) |
Dec
(91) |
| 2011 |
Jan
(62) |
Feb
(207) |
Mar
(157) |
Apr
(59) |
May
(122) |
Jun
(56) |
Jul
(105) |
Aug
(154) |
Sep
(64) |
Oct
(232) |
Nov
(224) |
Dec
(60) |
| 2012 |
Jan
(93) |
Feb
(251) |
Mar
(571) |
Apr
(205) |
May
(82) |
Jun
(48) |
Jul
(49) |
Aug
(34) |
Sep
(69) |
Oct
(22) |
Nov
(85) |
Dec
(41) |
| 2013 |
Jan
(30) |
Feb
(50) |
Mar
(66) |
Apr
(37) |
May
(11) |
Jun
(36) |
Jul
(40) |
Aug
(20) |
Sep
(9) |
Oct
(9) |
Nov
(28) |
Dec
(38) |
| 2014 |
Jan
(19) |
Feb
(20) |
Mar
(11) |
Apr
(5) |
May
(16) |
Jun
(26) |
Jul
(50) |
Aug
(60) |
Sep
(75) |
Oct
(49) |
Nov
(37) |
Dec
(9) |
| 2015 |
Jan
(20) |
Feb
(51) |
Mar
(72) |
Apr
(33) |
May
(22) |
Jun
(35) |
Jul
(38) |
Aug
(47) |
Sep
(48) |
Oct
(21) |
Nov
(47) |
Dec
(31) |
| 2016 |
Jan
(57) |
Feb
(42) |
Mar
(23) |
Apr
(21) |
May
(27) |
Jun
(9) |
Jul
(10) |
Aug
(43) |
Sep
(69) |
Oct
(30) |
Nov
(27) |
Dec
(34) |
| 2017 |
Jan
(34) |
Feb
(38) |
Mar
(35) |
Apr
(35) |
May
(40) |
Jun
(10) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <je...@sa...> - 2017-04-13 04:36:40
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2084/> |
|
From: <je...@sa...> - 2017-04-12 04:36:34
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2083/> |
|
From: Zieris, F. <Fra...@fu...> - 2017-04-11 17:30:55
|
I just came across this bug [1]. For some reason SonarQube did not spot it right away when it was introduced in Feb 2016 [2]. It took six more months until Aug 2016. Anyone care to fix it? Franz [1] http://saros-build.imp.fu-berlin.de/sonarqube/issues/search#issues=AVa8Lu6o5nMZJVRbtadT [2] https://github.com/saros-project/saros/commit/aa90be7b0c334ceb397c912fb2751ae031687885#diff-37c625925db40c245b5b5244088fbdebR867 |
|
From: <je...@sa...> - 2017-04-11 04:36:36
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2082/> |
|
From: <je...@sa...> - 2017-04-10 04:37:29
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2081/> |
|
From: <je...@sa...> - 2017-04-09 04:35:48
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2080/> |
|
From: <je...@sa...> - 2017-04-08 04:36:24
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2079/> |
|
From: Stefan R. <sro...@ar...> - 2017-04-07 18:57:58
|
Hi Franz, I was talking about the FileSystem, so the implementation of the following interfaces: IResource, IProject, IFile, IFolder, IContainer. The current implementation in IntelliJ of these interfaces is really questionable and really complicated. The main problem in IntelliJ (as likely in Netbeans too) is the missing functionality of the API to create invalid file / folder handles. If I remember correctly this problem was never reported back. It seems that the authors tried to implement such a functionality. Looking at the core code, we do not really need the IProject#getFile and IProject#getFolder methods (which are just returning handles). The only problem is to rewrite the ProjectMapper to use IPath objects instead of IResource objects. So this leads up to 2 solutions: 1. Try to implement something in the FileSystem that the IDE API do NOT support by default 2. Get rid of the required methods (needs changes in the Core) to avoid (possible) complicated solution mentioned in point 1. BR, Stefan On 06.04.2017 17:48, Zieris, Franz wrote: > Hi everyone, > > I came across this post by Stefan [1], which calls for more attention: > >> I still highly recommend to copy some existing code >> (like accessing a file etc) and then hit the delete >> button for every file. >> It should be easier to rewrite the whole stuff after >> we know what we have to implement than trying to fix >> this broken stuff. > I'd like to clarify this: > - Do you (not only Stefan, but everyone else with an opinion on that > matter) actually think so, or is this more like a figure of speech? > - Is "the whole stuff" the _whole_ IntelliJ stuff, or just a few > packages? > > I mean, what we are doing is not supposed to be occupational therapy > for underutilized code monkeys. > We are actually trying to get stuff done! > And if we come to the conclusion that re-writing would clearly be a > more reasonable approach, then we should actually consider it. > > Cheers, > Franz > > [1] http://saros-build.imp.fu-berlin.de/gerrit/#/c/3251 @ Mar 30 6:15 PM |
|
From: <je...@sa...> - 2017-04-07 04:35:34
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2078/> |
|
From: Zieris, F. <Fra...@fu...> - 2017-04-06 15:49:05
|
Hi everyone, I came across this post by Stefan [1], which calls for more attention: > I still highly recommend to copy some existing code > (like accessing a file etc) and then hit the delete > button for every file. > It should be easier to rewrite the whole stuff after > we know what we have to implement than trying to fix > this broken stuff. I'd like to clarify this: - Do you (not only Stefan, but everyone else with an opinion on that matter) actually think so, or is this more like a figure of speech? - Is "the whole stuff" the _whole_ IntelliJ stuff, or just a few packages? I mean, what we are doing is not supposed to be occupational therapy for underutilized code monkeys. We are actually trying to get stuff done! And if we come to the conclusion that re-writing would clearly be a more reasonable approach, then we should actually consider it. Cheers, Franz [1] http://saros-build.imp.fu-berlin.de/gerrit/#/c/3251 @ Mar 30 6:15 PM |
|
From: <je...@sa...> - 2017-04-06 04:36:09
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2077/> |
|
From: <je...@sa...> - 2017-04-05 04:36:11
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2076/> |
|
From: <je...@sa...> - 2017-04-04 04:37:42
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2075/> |
|
From: <je...@sa...> - 2017-04-03 04:37:34
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2074/> |
|
From: <je...@sa...> - 2017-04-02 04:37:47
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2073/> |
|
From: <je...@sa...> - 2017-04-01 04:38:20
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2072/> |
|
From: <je...@sa...> - 2017-03-31 04:38:22
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2071/> |
|
From: <je...@sa...> - 2017-03-30 04:38:16
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2070/> |
|
From: <je...@sa...> - 2017-03-29 04:36:22
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2069/> |
|
From: <je...@sa...> - 2017-03-28 04:36:15
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2068/> |
|
From: <je...@sa...> - 2017-03-27 04:36:09
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2067/> |
|
From: <je...@sa...> - 2017-03-26 04:35:34
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2066/> |
|
From: <je...@sa...> - 2017-03-25 05:36:28
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2065/> |
|
From: <je...@sa...> - 2017-03-24 05:35:23
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2064/> |
|
From: <je...@sa...> - 2017-03-23 05:36:40
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2063/> |