> I am trying to find about the best practices related to > SNAPSHOT dependencies. More and more I think about them I > find that some things are rather not clear and quite inconsistent. > > There is one misleading thing: We often find in POMs (maven, > maven plugins do that): > > <project> > <pomVersion>3</pomVersion> > <id>maven</id> > <name>Maven</name> > <currentVersion>1.1-SNAPSHOT</currentVersion> > ^^^^^^^^^^^^^^^^^^^^ > > (I understand that > <currentVersion>1.1-SNAPSHOT</currentVersion> denotes that > next release will be 1.1.) > > It is possible to do > > maven jar:install (will put maven-1.1-SNAPSHOT to repository) > maven jar:install-snapshot (will put maven-SNAPSHOT to repository) > > Do we really intend to have two different types of snapshots? > > <dependency> > .. > <version>1.1-SNAPSHOT</version> (latest version of 1.1 branch) > </dependency> > > and > > <dependency> > .. > <version>SNAPSHOT</version> (latest version which can > come from any of the branches) > </dependency> > > > If not maybe we can just have one single "install" goal > instead of "install and "install-snapshot"? "jar:install" > goal executed on project which current version is > 1.1-SNAPSHOT will deploy a snapshot version of jar. > > Maybe indeed it is reasonable to lock usage of snapshot to > one branch (like 1.0-SNAPSHOT, 1.1-SNAPSHOT)?
It was explained sometime back that there are usually not multiple (active) branches of Apache projects, there is only one branch. Thus doing something like maven-SNAPSHOT instead of maven-1.1-SNAPSHOT is ok because there is only one branch. While this might be acceptable for Apache (and apparently it is because that is the way it's used) non-OSS, commercial projects typically have multiple branches for the same project. This is actually the main reason why I can't use Maven at my current company. We are branch happy here (which is annoying) and have multiple active branches for all of our projects in support of our release points and customers. Locking usage of SNAPSHOT to one branch should be easy to add to the codebase. The effects of it might be more complicated though. > AFAIR there were some discussions about introducing something > which denotes latest released version (something like > maven-RELEASE). Maybe we should use those things together? > > Any ideas? > > Michal > > > > > --------------------------------------------------------------------- > 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]
