Agree, NB 9.0 is a complete headache and probably should not be considered
an *upgrade* from 8.2. Even upcoming NB 10.0 does not seem to solve
all the migration issues.
Maybe Apache Netbeans (9.0 and higher) has to be distributed as a different
package ("apache-netbeans"), conflicting with old "netbeans" package?
This way would allow manual upgrade (by installing "apache-netbeans")
from old good NB 8.0 to Apache NB when it will be good enough to replace it.
Regards,
Danila Kiver.
>Monday, November 12, 2018 1:38 PM +03:00 from Leandro Papi via arch-general <arch-general@xxxxxxxxxxxxx>:
>
>Hello,
>I'm not sure if this has to be brought up here, please advise.
>
>I have had many problems with netbeans package from community, it
>"upgraded" my old version of the package (was version 8.2), but it is
>not an adequate replacement.
>
>I'm aware of the bugs open in the tracker, and I thank everyone that
>provided workarounds to get the IDE working at first, then finally
>installing plugins correctly.
>
>However, the "new" version isn't complete yet, it lacks many of the
>"core" plugins that were available for 8.2, for example PHP (postponed
>to netbeans 10), JavaScript and C++ language support.
>
>I'm wondering what the correct procedure is in this case, if it were a
>commercial product,it would have reverted to 8.2 until it was ready.
>I don't have issues using it, I'm keeping it downgraded to 8.2,
>ignored in pacman.conf, I'm only asking if this is the correct
>approach for a repository package, since this is not AUR.
>
>Thanks,
>Leandro
>--
>L'ignoranza è un male curabile, è sufficiente la volontà.
>
>Please don't print this e-mail if you don't need to!
