This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | inheriting project library dependencies | ||
---|---|---|---|
Product: | projects | Reporter: | fommil <fommil> |
Component: | Generic Infrastructure | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | pjiricka, wadechandler |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.nabble.com/inheriting-project-library-dependencies-to13124472.html | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
fommil
2008-01-07 21:33:54 UTC
It could be non-trivial to do in ant. The UI/IDE part should be easier, but still a non trivial addition. Not for 6.1. On a general level dependency transitivity has both pros and cons. Apache Maven has transitive dependencies and users get a different set of problems. 1. how to exclude a certain dependency from transitivity? 2. how to synchronize the dependency tree if a single dependency comes from 2 sources but with different versions? etc. BTW why do you need it on runtime classpath only? what if the project A exposes some classes from X.jar? > BTW why do you need it on runtime classpath only? what if the project A exposes some classes from X.jar?
If A exposes classes from X.jar and B makes use of those classes, then X.jar should be on the compile-time dependency list. In Eclipse there is the possibility
to "export" dependencies which means to make them compile-time dependencies to anything higher in the chain. I would welcome such a feature in
NetBeans! (Although, getting basic inheritance working is the priority for me).
*** This issue has been marked as a duplicate of 47507 *** |