Correct process for creating builds reliant on 3rd party packages
I work on a Symfony 2 codebase.
Correct process for creating builds reliant on 3rd party packages
I work on a Symfony 2 codebase.
Correct process for creating builds reliant on 3rd party packages
I work on a Symfony 2 codebase.
Correct process for creating builds reliant on 3rd party packages
I work on a Symfony 2 codebase.
To depend on source code or on binary?
We have two in-house projects, A and B, developed by different teams with B dependent on A. Since source code for both projects is stored in git, I’ve included project A as a submodule into project B and configured the build system to build both in right order. An alternative solution would be to consume A via a binary repository manager such as Artifactory or Nexus.
If a dependency is not in the maven repository should I add it to source control?
One of the jar files that I use in my code is not in the maven repository(and yes I tried to avoid using it). I have installed it locally so when I build the project it gets picked up by maven. I also put instructions in my README so anyone who wants to build my code can see how to add the jar to their local repository.
Has anyone nailed dependency management? [closed]
Closed 9 years ago.
Cobol programs and copybooks versioning
in java we have ivy, maven and others for handling library dependencies. For example I tell ivy that my program uses a framework-jar version 1.0 and ivy makes sure, that my program gets this jar when being compiled. When there comes an update and the framework-jar is now available in version 1.1, then my program still gets the version 1.0. I can however tell ivy that another program of mine should take the newer version 1.1.
Cobol programs and copybooks versioning
in java we have ivy, maven and others for handling library dependencies. For example I tell ivy that my program uses a framework-jar version 1.0 and ivy makes sure, that my program gets this jar when being compiled. When there comes an update and the framework-jar is now available in version 1.1, then my program still gets the version 1.0. I can however tell ivy that another program of mine should take the newer version 1.1.
Cobol programs and copybooks versioning
in java we have ivy, maven and others for handling library dependencies. For example I tell ivy that my program uses a framework-jar version 1.0 and ivy makes sure, that my program gets this jar when being compiled. When there comes an update and the framework-jar is now available in version 1.1, then my program still gets the version 1.0. I can however tell ivy that another program of mine should take the newer version 1.1.