On 24/01/2011 6:28 PM, Guo Du wrote:
On Mon, Jan 24, 2011 at 5:41 AM, Anders Hammar<[email protected]> 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 Development Repository[1] is closest to
support the flow.
It could works for a very limited number of new dependency to be added
before #2. For the use case of a new project setup, lots of dependency
could be added and developer may even don't know which library is need
as there are transitive dependencies.
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.
This gives us simple projects and central control over libraries used.
If procurement could store all the new dependencies to a staging area
like a normal release staging repository and reusing existing
approval/release functionality, will make the flow more operational.
We just put our aggregated libraries in our repo with our webapps,
webservices, batch jobs, etc.
Also, One thing that you might want to have in mind is two have separate
repositories for dependencies and plugins. For Maven to be useful, you will
This does not work in Maven 2.x.
A very good practice, this is main reason to choose 3.X. We will leave
the plugins in a different world and have less restriction :)
Thanks all for the thoughts!
-Guo
[1]
http://www.sonatype.com/books/nexus-book/reference/procure.html#procure-sect-dev
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
