On Sun, Jul 26, 2020 at 9:57 AM Eric Bresie <[email protected]> wrote:
> Before I go too far....is anyone actively working these activities? > > Okay so from the README.cnd I see: > > > There are many caveats currently, a possibly incomplete list: > > > >* not all license headers have been changed; many files are missing the > license >headers; > I'm working the license headers issue.. > binary files need licenseinfo.xml to be filled > Same as above.. > > >* building requires a number of files from the original repository - work > by >NetBeans C/C++ enthusiasts is needed to resolve this in one way or > another > > Is there a reason these files are not included? > > Is it as simple as pull these (maybe update licenses), and check them in to > the new cnd branch? > >From my perspective, I'm unsure at this point.. We will need to look into this.. > >* building requires a number of binaries to be added manually > > Would changing any build files (ant/maven?) to pull these directly from > applicable repositories instead of having to copy these resolve this? > > For example, I see reference to an antlr jar being needed. Could reference > to dependency to this which then gets pulled during prep for building? > Same as above.. But, I started giving this some thought as Antonio did mention this.. >* external libraries/dependencies need to be reviewed and put up to Apache > standard > > What is meant by “Apache standard”? > > What needs to be done here? > Not sure what needs to be done here.. But, if you have some comments, I think everyone would welcome that.. Just an FYI, but Antonio has been giving some effort recently. And that is a welcome addition! -brad w.
