Hi all, I would assume it should be possible to build both - the JavaIDE and a generic IDE at the same time.
If we can get the GenericStuff working faster than the JavaIDE - we could decide to release that first. Sven On Tue, Nov 21, 2017 at 10:18 PM, John McDonnell <mcdonnell.j...@gmail.com> wrote: > Is there a way that we could look at doing both? > > i.e. In parallel do the generic IDE and look at how we do the Plugin > Manager/Portal. > > Once those are completed we could branch off the Generic > Modules/Plugin Manager and then Release this branch. > > From there, we could work to get the Java and other clusters released > as plugins (hence the need to looking at the Plugin Manager/Portal > previously), so that we can release new plugins but also update the > Website with new versions of the IDE to download? > > Or does this take us away from the idea of an Apache Release, that's > voted on, etc...? > > Regards > > John > > On 21 November 2017 at 21:12, Geertjan Wielenga > <geertjan.wiele...@googlemail.com> wrote: > > Very valid points. Very hard to argue against this perspective. > > > > Though note that focusing on a neutral-IDE first doesn’t necessarily mean > > slowing the process down. Just a different approach to the same end and > > whether it would end up taking longer or not is not predetermined. > > > > Gj > > > > On Tue, 21 Nov 2017 at 22:03, John McDonnell <mcdonnell.j...@gmail.com> > > wrote: > > > >> From a personal standpoint, I'd like to see a Java IDE as soon as > >> possible. I know there's still a lot of work to get there, but to > >> release a generic IDE, after a Platform release means we'll have done > >> 2 releases (Ignoring the HTML releases that are happening) that still > >> isn't at the state that most users of NetBeans (I assume) can use... > >> > >> This process started in late 2016, the last Oracle supported > >> release(8.2) was late 2016 as well. We've gone nearly a year without > >> a Java IDE release in the NetBeans family (NetBeans/Apache NetBeans), > >> if we don't see an actual release that developers out there can use, > >> that supports Java 9 soon then I think this would hurt the NetBeans > >> userbase. As developers moving to Java 9, will move to IntelliJ and > >> Eclipse before considering NetBeans as there simply isn't an IDE > >> release capable to support Java 9 to use right now. Anyone looking > >> for the latest most up to date IDE just right now wouldn't be looking > >> at NetBeans, and we need to change this and get back into the > >> conversation, and a Java IDE release sooner rather than later imo will > >> help this... > >> > >> > >> Regards > >> > >> John > >> > >> > >> > >> On 21 November 2017 at 20:39, Dmitry Avtonomov > >> <dmitriy.avtono...@gmail.com> wrote: > >> > That is a very good idea, Gj! > >> > > >> > From: Geertjan Wielenga > >> > Sent: Tuesday, November 21, 2017 12:37 > >> > To: dev@netbeans.incubator.apache.org > >> > Subject: Re: IDE release > >> > > >> > A related question: maybe we should move to the “ide” cluster first > and > >> > forget about anything language-specific, including Java, until we have > >> > released the generic non-language specific IDE features? > >> > > >> > Or, as a counter argument, would that not be significant enough to > >> justify > >> > its own process? > >> > > >> > From the usage point of view, having a generic platform is great and > in > >> the > >> > same way a generic IDE could be great too, before looking at a > >> > Java-or-any-specific-language IDE? > >> > > >> > As a side effect, this would raise the profile of this part of Apache > >> > NetBeans. > >> > > >> > Just some thoughts on next steps, happy to back away from them if > others > >> > disagree or show that I misunderstood something. > >> > > >> > Gj > >> > > >> > On Tue, 21 Nov 2017 at 21:30, Jan Lahoda <lah...@gmail.com> wrote: > >> > > >> >> Hi, > >> >> > >> >> I assume we should work on getting the code into a state where we > could > >> >> release a (beta) of (Java) IDE. When the platform/alpha is released, > >> I'll > >> >> change the release job: > >> >> > >> >> > >> https://builds.apache.org/view/Incubator%20Projects/job/ > incubator-netbeans-release/ > >> >> > >> >> to build the IDE (I'll let it build platform separately as well) and > run > >> >> the appropriate tests, including "ant verify-libs-and-licenses" > (which > >> >> checks that every external binary has a license file, and that the > >> license > >> >> file passes some basic checks). I ran verify-libs-and-licenses > manually, > >> >> and there is (unsurprisingly) a lot of failures. I fixed a few here: > >> >> https://github.com/apache/incubator-netbeans/pull/285 > >> >> > >> >> Among other problems there are several (L)GPL libraries we will need > to > >> >> solve somehow besides javac: > >> >> db.drivers/external/mysql-connector-java-5.1.23-license.txt > >> >> hibernate4lib/external/hibernate-4.3.1-lib-license.txt > >> >> libs.jshell.compile/external/nb-jshell-license.txt > >> >> (presumably compile-time only at this time) > >> >> o.jdesktop.beansbinding/external/beansbinding-1.2.1-license.txt > >> >> > >> >> My question is whether someone would be willing to work on the GPL > >> >> libraries (I personally know very little about the db+hibernate > ones); > >> or > >> >> on cleaning up the verify-and-licenses (I don't think this is big > >> enough to > >> >> enter the violations into a wiki, but there's quite a few of them, > so it > >> >> will take some time to clean them up). > >> >> > >> >> (When verify-libs-and-licenses is clean, we need to look at > DEPENDENCIES > >> >> and fix any problems we spot, but I don't think it makes much sense > to > >> look > >> >> at that when there are significant verify-libs-and-licenses > failures.) > >> >> > >> >> Thanks, > >> >> Jan > >> >> > >> > > >> > -- Sven Reimers * Senior Expert Software Architect * Java Champion * NetBeans Dream Team Member: http://dreamteam.netbeans.org * Community Leader NetBeans: http://community.java.net/netbeans Desktop Java: http://community.java.net/javadesktop * JUG Leader JUG Bodensee: http://www.jug-bodensee.de * Duke's Choice Award Winner 2009 * XING: https://www.xing.com/profile/Sven_Reimers8 * LinkedIn: http://www.linkedin.com/in/svenreimers