But we've been through that already, I did use the repo you're pointing to, I changed the version to RELEASE1234, it did build fine and I see all the stuff in my local m2 repo. Then I go to Netbeans IDE, create new maven nbp project, but the wizard only shows me the RELEASExxx that are found on Central. I tried creating an app with one of those versions available on Central (e.g. RELEASE111) and then changing all occurrences of RELEASE111 to RELEASE1234, but that didn't work. It doesn't want to check the local m2 repo at all.
On Sat, Nov 16, 2019 at 8:29 PM Tim Boudreau <niftin...@gmail.com> wrote: > Use this. It will build NBMs of all NetBeans modules from a source > checkout and populate your local repo with them. Just set the version > number to something unique and use that in your dependencies (hopefully as > a property set in one place). See the readme for details: > > https://github.com/timboudreau/netbeans-local-maven-repo-populator > > -Tim > > On Sat, Nov 16, 2019 at 7:35 PM Dmitry Avtonomov < > dmitriy.avtono...@gmail.com> wrote: > > > I want to not be dependent on the platform nbms published to Central or > any > > other online repository. I want to be able to clone NB sources from > Github, > > disconnect from the internet, and create a maven-based platform app with > > just that. If the platform I build the app against ever becomes > unavailable > > online, I want to still be able to build the app. > > > > Like exactly the same as what Geertjan is showing in the first video from > > [1]: https://youtu.be/VC8gQJknPaU. He builds netbeans from sources, > > registers the built platform using the UI for that in Netbeans IDE (Tools > > -> Netbeans Platforms) and creates a NBP app that uses that platform. I > > wanted to do the same, but the maven way. > > > > [1] > https://netbeans.apache.org/participate/build-run-debug-tutorials.html > > > > > > > > On Fri, Nov 15, 2019 at 1:06 PM Tim Boudreau <niftin...@gmail.com> > wrote: > > > > > If you mean, have a multi-module parent pom, and some way to run a > module > > > and have all its dependencies be found and included... as far as I > know, > > > there is simply no good way to do that with the nbm-maven-plugin - it > is > > a > > > glaring feature gap. > > > > > > The (painful) workaround is to create an nbm-application project, that > > > depends on everything you need, and build and run that (which means > > > rebuilding the entire application structure every time you want to run, > > > which can take several minutes). Here's an example of that (see the > pom > > > and the shell scripts in this dir): > > > > > > > > > > > > https://github.com/timboudreau/ANTLR4-Plugins-for-NetBeans/tree/master/antlr-suite > > > > > > I've thought about writing a patch for the nbm plugin to do the right > > thing > > > - build the application structure in the project's target/ dir, find > all > > > dependencies that can be resolved as projects in the reactor and only > > > update those that have changed - but I've only got about 2000 other > > things > > > I need to get done in front of that :-/ > > > > > > -Tim > > > > > > > > -- > http://timboudreau.com >
