On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammarand...@hammar.net wrote:
We do this by building jars that aggregate our 3rd party dependencies once
per release so we know exactly what transitive dependencies are going to be
used by the developers.
If you are running maven for some time, I won't
On 24/01/2011 6:28 PM, Guo Du wrote:
On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammarand...@hammar.net wrote:
You could be somewhat aided by the procurement feature of Nexus Pro (the
commercial edition of the Nexus repo manager):
http://www.sonatype.com/books/nexus-book/reference/procure.html
On Mon, Jan 24, 2011 at 2:31 AM, Ron Wheeler
rwhee...@artifact-software.com wrote:
1. Developer enables the access to internal repository(Nexus or other).
Internal repository is isolated from external even with nexus. This is
the main point of this work flow. Imaging with transparent proxy to
On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammar and...@hammar.net wrote:
You could be somewhat aided by the procurement feature of Nexus Pro (the
commercial edition of the Nexus repo manager):
http://www.sonatype.com/books/nexus-book/reference/procure.html
Looked at the link, Procured
In a commercial software development environment, production code will
rely on artifacts which may come from public domain such as maven
central repository. For those artifacts from external, would be
validated with some process such as
checksum/javadoc/sources/license/lawyer, once passed those
1. Developer enables the access to internal repository(Nexus or other).
2. Developer add new dependencies as artifacts/plugins which available
from external repository.
3. Developer test the new pom setup and it works on local machine
4. Maven and Nexus will automatically load new dependencies
You could be somewhat aided by the procurement feature of Nexus Pro (the
commercial edition of the Nexus repo manager):
http://www.sonatype.com/books/nexus-book/reference/procure.html
Also, One thing that you might want to have in mind is two have separate
repositories for dependencies and
