How team should work with maven

Could somebody to explain how the team should work with maven.

For example.

10 developers and 1 team lead are working together.

Everyones has the own module in development.

Next, one made the changes in his module and marked it like

<version>1.3</version>? And say to neighbor whous modul is depend on his: "will be make your modul to point version 1.3 for my

<artifactId>his-app</artifactId>

<version>1.3</version> ? Or how?

If he to point the unexisting version the maven will swear.

And next. There's something pom.xml for team lead on top level of another modules of developers which team lead to use for assebling?

Help please to understand how to use this framework

[780 byte] By [Lesyka] at [2007-10-2 5:33:14]
# 1
It sounds like the functionality you are looking for is what maven calls snapshots. This allows developers to build and deploy the latest code base on the fly and maven can grab the latest releases without having to continually update the pom.
j@Va_GuYa at 2007-7-16 1:44:03 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 2
Have you configured Maven in your current project?Rgds,Seetesh
seteshhindlea at 2007-7-16 1:44:03 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...
# 3
I have configured maven for projects... not my current and not maven 2.
j@Va_GuYa at 2007-7-16 1:44:03 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...