Re: IntelliJ vs Eclipse
On 02/06/2019 20:39, Vincent Privat wrote: but that's more because I'm so used to use Eclipse I didn't find the time to "learn" IntelliJ rather than a personal preference. Much the same here ... ALL my development work goes through Eclipse, and only a small part is Java based ... -- Lester Caine - G8HFL - Contact - https://lsces.uk/wiki/Contact L.S.Caine Electronic Services - https://lsces.uk Model Engineers Digital Workshop - https://medw.co.uk Rainbow Digital Media - https://rainbowdigitalmedia.co.uk
Re: IntelliJ vs Eclipse
Am 02.06.2019 um 21:28 schrieb Simon Poole: > .. > The canonical solution would be to move to gradle as the underlying > build system, which works for both, potentially with a little bit of Naturally it works without an IDE too. so it would cover all three use cases. Simon > work on the eclipse side (and I use that setup with a tiny weeny company > trying to make it impossible). > > signature.asc Description: OpenPGP digital signature
Re: IntelliJ vs Eclipse
You won't find consensus between those who prefer Eclipse and those who prefer IntelliJ. Either we support both of them of none. Personally I still use Eclipse even if I have a an IJ license but that's more because I'm so used to use Eclipse I didn't find the time to "learn" IntelliJ rather than a personal preference. Cheers, Vincent Le dim. 2 juin 2019 à 21:29, Simon Poole a écrit : > As a non-JOSM dev, but forced to use IntelliJ now and then, and somebody > who really doesn't particularly like Eclipse: IntelliJ sucks so badly > that it makes eclipse look like the pinnacle of UI design. Just try > using IntelliJ with less than perfect eyesight, that is just one aspect > of many. > > The canonical solution would be to move to gradle as the underlying > build system, which works for both, potentially with a little bit of > work on the eclipse side (and I use that setup with a tiny weeny company > trying to make it impossible). > > Simon > > * the involvement of the tiny weeny company with IntelliJ would be a > reason on its own not to move without an alternative. > > Am 02.06.2019 um 20:59 schrieb Michael Zangl: > > I noticed that a lot of devs have changed from Eclipse to IntelliJ > > > > The free community edition is fine for working on JOSM and we have > > some ultimate licenses available if any core dev needs them. > > > > We currently have those build systems checked into our svn repository: > > * ant > > * Eclipse > > In #17218 [1] I added a first patch to support IntelliJ as well. > > The problem is: If we add support for IntelliJ, we have to update 3 > > build systems every time we change something. So it would be best to > > drop Eclipse then. Eclipse was not developed that much in the last > > view years and lacks behind IntelliJ a lot, especially when it comes > > to debugging. > > > > Therefore, I would like to get a short heads up from JOSM core devs, > > if you are using (or want to be using) IntelliJ or Eclipse (or if you > > don't care). > > > > It is probably best if we continue the discussion in the ticket. > > > > Michael > > > > [1] https://josm.openstreetmap.de/ticket/17218 > > > >
Re: IntelliJ vs Eclipse
As a non-JOSM dev, but forced to use IntelliJ now and then, and somebody who really doesn't particularly like Eclipse: IntelliJ sucks so badly that it makes eclipse look like the pinnacle of UI design. Just try using IntelliJ with less than perfect eyesight, that is just one aspect of many. The canonical solution would be to move to gradle as the underlying build system, which works for both, potentially with a little bit of work on the eclipse side (and I use that setup with a tiny weeny company trying to make it impossible). Simon * the involvement of the tiny weeny company with IntelliJ would be a reason on its own not to move without an alternative. Am 02.06.2019 um 20:59 schrieb Michael Zangl: > I noticed that a lot of devs have changed from Eclipse to IntelliJ > > The free community edition is fine for working on JOSM and we have > some ultimate licenses available if any core dev needs them. > > We currently have those build systems checked into our svn repository: > * ant > * Eclipse > In #17218 [1] I added a first patch to support IntelliJ as well. > The problem is: If we add support for IntelliJ, we have to update 3 > build systems every time we change something. So it would be best to > drop Eclipse then. Eclipse was not developed that much in the last > view years and lacks behind IntelliJ a lot, especially when it comes > to debugging. > > Therefore, I would like to get a short heads up from JOSM core devs, > if you are using (or want to be using) IntelliJ or Eclipse (or if you > don't care). > > It is probably best if we continue the discussion in the ticket. > > Michael > > [1] https://josm.openstreetmap.de/ticket/17218 > signature.asc Description: OpenPGP digital signature
IntelliJ vs Eclipse
I noticed that a lot of devs have changed from Eclipse to IntelliJ The free community edition is fine for working on JOSM and we have some ultimate licenses available if any core dev needs them. We currently have those build systems checked into our svn repository: * ant * Eclipse In #17218 [1] I added a first patch to support IntelliJ as well. The problem is: If we add support for IntelliJ, we have to update 3 build systems every time we change something. So it would be best to drop Eclipse then. Eclipse was not developed that much in the last view years and lacks behind IntelliJ a lot, especially when it comes to debugging. Therefore, I would like to get a short heads up from JOSM core devs, if you are using (or want to be using) IntelliJ or Eclipse (or if you don't care). It is probably best if we continue the discussion in the ticket. Michael [1] https://josm.openstreetmap.de/ticket/17218
