My point was that a cluster reorganization would help us release in 2017. --emi
>-------- Original Message -------- >Subject: Re: IDE release >Local Time: November 23, 2017 7:50 AM >UTC Time: November 23, 2017 5:50 AM >From: anto...@vieiro.net >To: dev@netbeans.incubator.apache.org > >Hi all, > > Some comments inlined below > > El 22/11/17 a las 23:26, Emilian Bold escribió: >>A NetBeans release supporting Java 9 seems of utmost importance in 2017. >> >Fully agree. I'm not sure 2017 is feasible, though. >>Initially we could just carve-out the pieces we can't ship. It's unfortunate >>but not a roadblock for a Java developer not to have Hibernate tooling or a >>MySQL connector in NetBeans. In time we can move those to separate community >>(ie. non-Apache) plugins. >> >Definitely: I'd prefer starting as small as possible, and grow upon that > (and see how strong we are now during the process). > > Regarding IDE modules, and as a wise man once said: "Either use an > Apache compatible license, adopt it, or get out of the way as a plugin > module(s) somewhere at github". > >>I remember we had an open discussion with the Hibernate folks about >>relicensing some DTDs. Are we also using JARs from Hibernate? >>Maybe we should look into the way our clusters are grouped. I don't see why >>the Java editor would have any kind of dependency on db.drivers. >>We could make a tinyide cluster and put less modules in there and have the >>java cluster depend on tinyide and extide. >> >> I'm not sure cluster reorganization is feasible if we want to release in >>2017. If cluster reorganization is the way to go then maybe the sooner > the better. > > But we may want to do that later on, and try to take JDK modules into > account. Clusters could be organized to require as less JDK modules as > possible. I'd love to see a "tiny platform cluster" run on top of > java.base only. > > Un abrazo, > Antonio > >>--emi >> >>>-------- Original Message -------- >>> Subject: IDE release >>> Local Time: November 21, 2017 10:30 PM >>> UTC Time: November 21, 2017 8:30 PM >>> From: lah...@gmail.com >>> To: dev@netbeans.incubator.apache.org >>>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 >>>Projects/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 >
