Dne pondělí 19. října 2020 23:21:19 CEST, Jesse Glick napsal(a): > On Wed, Oct 14, 2020 at 2:38 AM Jaroslav Tulach > > <[email protected]> wrote: > > Non-kit module depending on a kit would be an error in such setup. > > I see. If this is a rule, there seem to be a number of violations: > > $ fgrep .kit */*/nbproject/project.xml | fgrep -v kit/ | fgrep -v friend > apisupport/timers/nbproject/project.xml: > <code-name-base>org.netbeans.modules.ide.kit</code-name-base> > enterprise/spring.webmvc/nbproject/project.xml: > <code-name-base>org.netbeans.modules.web.kit</code-name-base> > enterprise/web.jsf/nbproject/project.xml: > <code-name-base>org.netbeans.modules.web.kit</code-name-base> > enterprise/web.primefaces/nbproject/project.xml: > <code-name-base>org.netbeans.modules.web.jsf.kit</code-name-base> > enterprise/web.struts/nbproject/project.xml: > <code-name-base>org.netbeans.modules.web.kit</code-name-base> > java/debugger.jpda.jsui/nbproject/project.xml: > <code-name-base>org.netbeans.modules.java.kit</code-name-base> > java/debugger.jpda.visual/nbproject/project.xml: > <code-name-base>org.netbeans.modules.java.kit</code-name-base> > java/maven.search/nbproject/project.xml: > <code-name-base>org.netbeans.modules.maven.kit</code-name-base> > java/performance/nbproject/project.xml: > <code-name-base>org.netbeans.modules.ide.kit</code-name-base> > java/spring.beans/nbproject/project.xml: > <code-name-base>org.netbeans.modules.java.kit</code-name-base> > php/hudson.php/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.apigen/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.composer/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.doctrine2/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.latte/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.phpdoc/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.smarty/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.symfony2/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.symfony/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.twig/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > php/php.zend/nbproject/project.xml: > <code-name-base>org.netbeans.modules.php.kit</code-name-base> > > Anyway, this is getting off topic. The original problem I encountered > I have found a tolerable solution for.
OK. Just to finish the story. This kind of dependency usually gets created when a module is distributed separately (via AU?) first and then it becomes part of the distribution. When the module is installed on demand, it is comfortable to request the whole functionality - e.g. kit - to be around (true for php frameworks, JS extensions to debugger, timers(?), etc. When the module becomes part of distribution, nobody bothers to revert the dependency and make a kit (debugger, php, etc.) depend on that module instead. -jt --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
