J
jankeir
Guest
Regarding package management, this is typically taken care of as part of a build pipeline. Almost all pipelines that are likely to adopt whatever package management any one offers at this point uses ant with PCT. PCT has Apache Ivy to take care of this. We have implemented this locally and it works fine (we use Sonartype's nexus as repository which is basically a maven repo, but it contains zip files with abl r files in our case). The build pipeline pulls in a zip file for each dependency and flattens the various dependencies into a single tree for the actual run time. Basically all that's needed is adding and xmlns:ivy="antlib
rg.apache.ivy.ant" to build.xml and create an ivy.xml file that lists the dependencies: No coding is needed for this, no changes to .pl files, no significant change in the way people work with building,... If someone were to set up/host a public repo and write some tutorials it could be a problem from the past. I must admin though that it is not something I am volunteering to do.
Continue reading...
rg.apache.ivy.ant" to build.xml and create an ivy.xml file that lists the dependencies: No coding is needed for this, no changes to .pl files, no significant change in the way people work with building,... If someone were to set up/host a public repo and write some tutorials it could be a problem from the past. I must admin though that it is not something I am volunteering to do.Continue reading...