IntelliJ vs Eclipse

[Simon Poole]

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
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/josm-dev/attachments/20190602/818cb4e1/attachment.sig>