dependencies

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed last year . I want to write documentation on my pet project. I have 30 tables and almost 50 views and about 30 functions (stored procedures) in my PostgreSQL database. I would like to see where tables ( which views and which functions ) are used. I would like to see where views ( which views

问题 I wonder if there is a way to prevent all files in a certain scope from importing any file from a different second scope. Example: Given this project structure: project/ ├── node_modules/ ├── test/ ├── src/ │ ├── domain/ │ │ ├── SomeModelClass.ts │ ├── application/ │ │ ├── SomeApplicationConcern.ts │ ├── database/ │ │ ├── SomeRepository.ts ├── tsconfig.json └── tslint.json I would like to enforce at least some of these rules: SomeApplicationConcern can import code from anywhere.

问题 i have created a stateless session bean like this : @WebServlet(name = "ProductController", urlPatterns = {"/ProductController"}) public class ProductController extends HttpServlet { @EJB private ProductFacadeBean productBean; } @Stateless public class ProductFacadeBean extends AbstractFacade<Product> implements ProductFacadeLocalInterface { @PersistenceContext(unitName = "OnlineStorePU") private EntityManager em; protected EntityManager getEntityManager() { return em; } public

问题 I am using libcurl in my project and it depends on openssl and bunch of other .so in runtime. This dependency is kind of pain in the ass, since different distributives/versions may contain different openssl versions. For example I am experiencing problems running on Ubuntu 11.10 if I compiled my app on Ubuntu 9.10. I am seeing two options how to solve this but none of them aren't good enough for my case: package my app and let package manager solve this sort of stuff link all deps statically

问题 I am trying to install Eclipse Git Team Provider and JGit in my version of Eclipse ADT via Help > Install New Software > "EGit - http://download.eclipse.org/egit/updates" but the installation fails with this error... Cannot complete the install because one or more required items could not be found. Software being installed: Java implementation of Git - optional Http support using Apache httpclient 3.3.1.201403241930-r (org.eclipse.jgit.http.apache.feature.group 3.3.1.201403241930-r) Missing

问题 I have projects that need to be build with a specific version of the JDK. The problem isn't in the source and target parameters but in the jars of the runtime used during compilation. In some cases I get a compilation error if I try to compile with the wrong JDK, but sometimes the build is successful and I get runtime errors when using the jars. For example in eclipse I have the ability to establish the execution enviroment for the project in the .classpath file. Is there a way to handle such

问题 I'm trying to figure it out what is the difference between api and implementation configuration while building my dependencies. In the documentation, it says that implementation has better build time, but, seeing this comment in a similar question I got to wonder if is it true. Since I'm no expert in gradle, I hope someone can help. I've read the documentation already but I was wondering about a easy-to-understand explanation. 回答1: Gradle compile keyword was deprecated in favor of the api and

问题 I'm intrigued to test new frameworks in the Java world, and decided to create a new project that takes advantage of Maven and db4o. I'm starting to get a hang of Maven, but I have a hard time adding db4o as a dependency to the project. First problem is that db4o doesn't exist in the official Maven repositories. Next up comes the problem that db4o seem to have recently restructured their whole site's URI:s, so I'm getting 'site not found' messages all the time when I try to navigate their site

问题 Say I have a complex project with lots of dependencies. The versions of the dependencies are managed by lots of import scope poms. My project has a dependency on artifact group:artifact , which has a dependency on artifact group:transitive-dependency . When I run dependency:tree I see something like this: +- group:artifact:jar:1.3 +- group:transitive-dependency:jar:1.1 (version managed from 1.3) The problem is group:artifact:1.3 requires group:transitive-dependency version 1.3 or higher. Sure

问题 I was reading Wikipedia's definition of Dependency inversion principle, and it uses two terms High-level modules and low-level modules , which I wasn't able to figure out. What are they and what does Dependency inversion principle have to do with them? 回答1: The definition of those are given in the introductory sentence: high level: policy setting low level: dependency modules. In laymen's terms: high level modules depend on low level modules, but shouldn't depend on their implementation. This