Quoting Rafal Krzewski <[EMAIL PROTECTED]>: > Christian Clausen wrote: > > > Sorry for not being explicit. I disagree with the statement "you need to > put the > > name of the branch into the artifact name". In my example, the artifactId > is the > > same in all branches. > > With current maven, you can have only one snapshot version per artifact. > If you project has two branches that need separate snapshots, it must > deliver two distinct artifacts. There is no way around this, that I know > of. Therefore the easiest way of achieving the objective of having > distinct snaphost versions for both branches of your codebase is > delivering two artifacts named in <artifact>-<branch> fashion. > > R. >
I suddenly realize that we use the two different styles of snapshot versions: You're talking about timestamped jars created with jar:deploy-snapshot while I'm talking about jars of a project with version x.y-SNAPSHOT (in project.xml) and deployed with jar:deploy. When using the style of snapshot version that I use, it's (of course) possible to have multiple multiple "snapshot versions" (one for each branch). In your case, there is another option for allowing multiple snapshots, if you don't like to change the artifact names to <artifact>-<branch>: Use different groups for different branches. So if <group> is your group, then your branched group could be named <group>-<branch>. > > --------------------------------------------------------------------- > 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]
