Delivering artifacts and distributions

In a project life, you are led to release your artifacts, either independently of any other binary, or included in a wider archive.


A good practice is to implement a simple rule; as stated earlier, team members can build any SNAPSHOT versions, but the task of delivering a release version should be reserved exclusively to the continuous integration system. Actually, theoretically, the same code on any platform should produce the same bytecode and hence be archived. Anyway, on loading them from the local repository, Maven does not discriminate artifacts that have been locally built from those that have been downloaded from a remote repository, provided they have the same designation. Therefore, to ...

Get Apache Maven Dependency Management now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.