Hi Eirik, Eirik Bakke <eba...@ultorg.com> writes:
> There are usually two kinds of modules you will need to add: "API" > modules (typically groupId org.netbeans.api), and implementation > modules (typically groupId org.netbeans.modules). The API modules you > can find by typing the name of the class you need to use into the Add > Dependency UI. The implementation modules are added with " > <scope>runtime</scope> ", and you usually find them by running your > app and getting an error that some implementation module is not > available. This is very useful to know. >> By the way, I notice that by default, a new Maven-based NetBeans >> Platform application will declare a dependency on the artifact >> org.netbeans.cluster:platform, which in turn depends on many, many >> other artifacts (including >> org.netbeans.modules:org-netbeans-modules.favorites). If I DON'T >> want to include one of these things (e.g., the Favorites feature), >> what's the right way to remove it from my application? > > Looking at my own NetBeans Platform application, it does indeed depend > on org.netbeans.cluster:platform. I think for things that are included > in this cluster, the best way to get rid of them is to remove the > relevant actions/menu items etc. from the branding module's layer.xml > . Once you have a layer.xml file added to a module, you can expand it > in the NetBeans IDE, expand "<this layer in context>", and then start > deleting things you don't want. This will generate the required > ".instance_hidden" XML configuration lines. > > Alternatively it might be possible to not include the platform cluster > and instead enumerate the relevant modules manually. I haven't tried > this myself, though. I figured I could whittle down the Maven dependencies to a smaller set, provided I know what "the right" set is. However, I didn't realize you could customize the layers like you mentioned. Nice idea! I still have much to learn. Thank you for your help, -- Chris
signature.asc
Description: PGP signature
