dependency-management

I have many JS snippets and files shared across multiple projects. I have to either copy-past them into a single file for each project, or serve them as individual files on cdn. Both are bad ideas. Is there any dependency management and build tool like Maven for JavaScript? Ideally it would take a set of js dependencies and build a single js file which can be served on cdn. I can write a script to do that. But I'm looking to find if anything comparable to Maven exists for JS. Update 2014: Based on answers here and my research following are most popular tools: Bower, NPM, RequireJS, Browserify,

What are the advantages/disadvantages of using Cocoapods vs. Git Submodules? I am aware that there are several differences, but I would like to find out more about the advantages and disadvantages of using either system. Thanks! Git submodules shouldn't be used for dependancy management. I suggest you to use Cocoapods. Git Submodule Pros Basically a one liner to initiate it, no need for extra files / configuration. Cons You can't specify target directories, you always have to clone the whole repository. When the repository moves you have to manually update it. You have to check in the actual

I'm looking at the controllers in my website, and most of their constructors look like this: public SomeController( IServiceOne serviceOne, IServiceTwo serviceTwo, ILoggingService loggingService, IGeospatialService geoSpatialService) { // copy to class variables. } In other words, it's very hairy and makes refactoring difficult. Some controllers have around 8 dependencies. Is there any way i can somehow "group" these dependencies into one of more buckets? For example, ILoggingService is required in every controller, IGeospatialService is required by controllers who do spatial stuff, and

I have a maven project which I have say spring framework libraries as dependencies, I want to copy spring framework dependencies with there transitive dependencies to a location specified. I have gone through maven dependency plugin guides at apache, I have several options where non of them will solve the complete problem. copy dependencies option <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.8</version> <executions> <execution> <id>copy-dependencies</id> <phase>package</phase> <goals> <goal>copy-dependencies</goal> </goals>

I am depending on a few artifacts that I need to both compile and run my application. According to the Gradle docs, the runtime configuration extends the compile configuration, so surely adding a dependency using runtime implies an implicit compile dependency? At least that was my assumption, but it does not work. When just depending on the artifact using runtime , my project does not compile anymore. I literally have to: compile 'oauth.signpost:signpost-core:1.2.1.2' runtime 'oauth.signpost:signpost-core:1.2.1.2' for the application to both compile and see the Signpost classes at runtime. Am

The premise of my question, in plain english: A library named Foo depends on a library named Bar A class within Foo extends a class within Bar Foo defines properties/methods that simply pass-through to Bar An application, FooBar , depends only on Foo Consider the following sample: class Program { static void Main(string[] args) { Foo foo = Foo.Instance; int id = foo.Id; // Compiler is happy foo.DoWorkOnBar(); // Compiler is not happy } } Foo is defined as follows public class Foo : Bar { public new static Foo Instance { get => (Foo)Bar.Instance; } public new int Id { get => Bar.Id; } public