In a pinch, you can always use the Maven antrun plugin, overriding the run target to build all the NBMs and unpack them into some directory *$YOUR_CLUSTER* - which can be anywhere on your disk you want. Then, using a *copy* of NetBeans, not the IDE you're running, or strange things will happen, add $YOUR_CLUSTER to the list in netbeans.conf's netbeans_extracluster variable; in ~/.m2/settings.xml set netbeans.installation to the copy you're using. Then just launch $NB_COPY/bin/netbeans. Ain't pretty, but ought to work, and is a little closer to what the Ant suite run task does.
Basically, if you're developing modules to integrate into the IDE, the workflow is a little smoother using Ant once you get beyond developing single modules. The Maven stuff - and suites - make some tacit assumptions that you're building a platform application, and in the case of Maven, that you want to work against a known version of the platform/IDE available from a Maven repo. -Tim On Tue, Jun 5, 2018 at 5:08 PM, Peter Nabbefeld <peter.nabbef...@gmx.de> wrote: > Hi Geertjan, > > the Maven "NetBeans Application" project type states: "The platform is > loaded entirely from a Maven repository." - that's not what I want. Also, I > don't want to modify anything of the IDE. I'll try the tutorial probably > some time later. > > The "nbm-suite-root" plugin is working in general, but it refuses to load > external dependencies if OSGi modules are allowed as dependencies; I've > filed an issue. However, this is not a problem in my case. > > Kind regards > Peter > > > > Am 05.06.2018 um 12:09 schrieb Peter Nabbefeld: > >> >> The archetype is working, but only without "useOSGiDependencies". >> >> When adding new modules to some POM project (like the one generated by >> "nbm-suite-root"), usually "Allow OSGi modules as dependencies" is selected >> by default, adding a configuration parameter entry >> "<useOSGiDependencies>true</useOSGiDependencies>" to the created POM for >> the new module. >> >> But if those are enabled, they seem to be also expected, as external >> dependencies (like antlr4-runtime) aren't resolved then, so I had to remove >> the flag. I'll go to check if this is also the case for other situations, >> like "normal" POM projects containing NB modules etc. >> >> Kind regards >> Peter >> >> >> >> Am 05.06.2018 um 11:24 schrieb Peter Nabbefeld: >> >>> >>> Hi Geertjan, thank You! >>> >>> At the beginning of the tutorial I found a little mistake: >>> While the "sticker" says, "Requires NetBeans 8.1", there's a "Note: >>> **This document uses NetBeans Platform 7.2 and NetBeans IDE 7.2. If you are >>> using an earlier version, see the previous version of this document < >>> https://platform.netbeans.org/tutorials/71/nbm-maven-quickstart.html>." >>> >>> The other problem for me is: If I create a NetBeans application, will I >>> still have my IDE, or will it just be NetBeans platform + my modules? I'd >>> just want to extend NB IDE, like a usual suite project. >>> >>> However, just when I looked around and tried to create a Maven project >>> from artifact, I also found the archetype "nbm-suite-root", which I >>> couldn't find anything about at NB site - I'll try that. >>> >>> Kind regards >>> Peter >>> >>> >>> >>> Am 05.06.2018 um 08:17 schrieb Geertjan Wielenga: >>> >>>> Tutorial: https://platform.netbeans.org/tutorials/nbm-maven-quickstart >>>> .html >>>> >>>> Gj >>>> >>>> On Tue, Jun 5, 2018 at 8:09 AM, Peter Nabbefeld <peter.nabbef...@gmx.de >>>> > >>>> wrote: >>>> >>>> Thank You, Tim! What does an application project make so special? I >>>>> guess, >>>>> it's not "only" the branding? BTW, can I drop it, to turn the >>>>> application >>>>> project into a suite? >>>>> >>>>> Regards >>>>> Peter >>>>> >>>>> >>>>> >>>>> Am 05.06.2018 um 07:59 schrieb Tim Boudreau: >>>>> >>>>> Suites were really invented for Ant projects, and just happen to >>>>>> output a >>>>>> cluster because a suite is usually a group of interdependent modules, >>>>>> so >>>>>> most of the time mapping that to a cluster makes sense. >>>>>> >>>>>> http://wiki.netbeans.org/DevFaqSuitesVsClusters >>>>>> >>>>>> For Maven projects, if one is an "application" project (with branding, >>>>>> etc.), you can start that and it should load the dependencies (that >>>>>> one >>>>>> will have dependencies on all your other modules). You could also >>>>>> create >>>>>> a >>>>>> dummy one for testing purposes. >>>>>> >>>>>> -Tim >>>>>> >>>>>> >>>>>> On Tue, Jun 5, 2018 at 1:53 AM, Peter Nabbefeld < >>>>>> peter.nabbef...@gmx.de> >>>>>> wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>>> using Maven, there's a project type for NetBeans Applications, but >>>>>>> not >>>>>>> for >>>>>>> a NetBeans Module Suites. >>>>>>> >>>>>>> So I created a POM project and added some NetBeans Modules. But I >>>>>>> cannot >>>>>>> start it. >>>>>>> >>>>>>> The POM project cannot be started with NetBeans, and the single >>>>>>> modules >>>>>>> aren't required (though dependent), so starting the "main module" >>>>>>> doesn't >>>>>>> load its dependencies. >>>>>>> >>>>>>> What am I missing? >>>>>>> >>>>>>> Kind regards >>>>>>> Peter >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incub >>>>>>> ator.apache.org >>>>>>> For additional commands, e-mail: dev-h...@netbeans.incubator.ap >>>>>>> ache.org >>>>>>> >>>>>>> For further information about the NetBeans mailing lists, visit: >>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------ >>>>> --------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org >>>>> For additional commands, e-mail: dev-h...@netbeans.incubator.ap >>>>> ache.org >>>>> >>>>> For further information about the NetBeans mailing lists, visit: >>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >>>>> >>>>> >>>>> >>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org >>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org >>> >>> For further information about the NetBeans mailing lists, visit: >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >>> >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org >> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- http://timboudreau.com
