Improving Distributed Artifact Distribution for Developers

Developers are relying on the use of distributed repository tools like maven, and repository managers like Nexus and Artifactory. Microsoft has a similar approach built into Visual Studio.   This approach makes it very easy for one to use many different pieces of software without knowing what the dependency tree is.  When using these services one is making the following assumptions.

  1. The code from the repository is the actual code intended to be there from non malicious developers.
  2. One is using code that abides by other constraints for example licensing.

There are a number of assumptions and questions one can question and or improve about Maven type systems. Maven is a general term for specification of dependencies using some formal declarative language and a system of hosting these artifacts in a large distributed network. Add additional attributes to the maven process so one can ask additional questions. Some hypothetical questions.

  1. How was it tested
  2. What are the licensing policies
  3. What is the quality of the source code management
  4. who are the developers and committers
  5. What are the reported bugs against the source code base
  6. Additional features that are not implemented.

Ideally a general approach allowing one to ask arbitrary questions would be ideal. Perhaps some of the approaches with Semantic Technologies would be useful

Leave a Reply

Your email address will not be published. Required fields are marked *

*