is right proceed structuring codebase?
we have java codebase now web-based netbeans project. the method codebase grows seems apparent should assign several individualist pieces the component sole jars. jar library information opening layer, whole lib, specialized trust access, etc. following we'd have removed digest web application, have management line collection app, another web app eventually, etc.
what permitted use doing handling this? maven? effectively finished only netbeans alone simply formulating sole projects sourroundings dependecies digest jar files others?
Comments
Post a Comment