How do you manage shared software in a large project?

I’m working on a project too large to live in the same Visual Studio / Eclipse / NetBeans project, and we have a “common software” team responsible for developing and maintaining the software libraries used by other teams.

I struggle for how to manage the development and change of general software. When signatures and method classes change, keep old versions and mark them obsolete? The current plan is to distribute a new assembly of shared libraries every two weeks.

+3
source share
3 answers

. Maven-hater Gradle, Ivy. Maven , . IDE Maven , , , , , .

Ivy, Maven , . ( pom.xml Maven), .

+1

. . API , : , .

0

, .

A:

Java Ant + Ivy Maven .

B: Classpath , eclipse classpath .

classpath\
  docs\
  sources\
  jars\

, , script, pathpath, , , - classpath .

B, , , , A.

, , , , , , . , IDE . , , eclipse , .

, , , . , , , , , , , , , DVCS, mercurial git, .

0

All Articles