Re: [m2e-users] More questions about dependency resolution

["KARR, DAVID" <dk068x@xxxxxxx>]

> -----Original Message-----
> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-
> bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
> Sent: Tuesday, September 04, 2012 12:44 PM
> To: m2e-users@xxxxxxxxxxx
> Subject: Re: [m2e-users] More questions about dependency resolution
> 
> I may have misunderstood your original question. Can you describe what
> kind of changes each of the branches will have? Are they "feature"
> branches, that are relatively short-lived and get merged to a "release"
> branch after feature work is complete? Or they are "release" branches
> that include changes towards a particular release.

Our current strategy is to create a branch for a release when we start work on the changes and only merge those changes back after the release is complete.

We're still evaluating whether we will change our branching strategy, but I think we'll likely stay with the current strategy unless I can come up with overwhelming arguments against it.  I had argued for a "branch for release" strategy (most work goes to trunk, branches created for release candidates only, with some exceptions using "branch for feature"), but I met too much resistance to this strategy.

> On 12-09-04 3:02 PM, KARR, DAVID wrote:
> >> -----Original Message-----
> >> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-
> >> bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
> >> Sent: Tuesday, September 04, 2012 11:53 AM
> >> To: m2e-users@xxxxxxxxxxx
> >> Subject: Re: [m2e-users] More questions about dependency resolution
> >>
> >> Normally, each branch has it's own version, so artifacts built from
> >> different branches have different maven coordinates and can be
> >> referenced both during command line build and from m2e workspace.
> >
> > Ok, that's pretty clear, but is it typical to allocate version ranges
> to each branch, or some other numbering strategy?
> >
> >> On 12-09-04 2:23 PM, KARR, DAVID wrote:
> >>>> -----Original Message-----
> >>>> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-
> >>>> bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
> >>>> Sent: Tuesday, September 04, 2012 3:30 AM
> >>>> To: m2e-users@xxxxxxxxxxx
> >>>> Subject: Re: [m2e-users] More questions about dependency
> resolution
> >>>>
> >>>> On 12-09-03 9:50 PM, KARR, DAVID wrote:
> >>>>> Each project will have a unique coordinate, and when built will
> be
> >>>>> installed in the user's local repository.  However, I obviously
> >> have
> >>>>> to figure out how to deal with the fact that the same project
> could
> >>>>> be built on different branches, resulting in actually different
> >>>>> artifacts, but with essentially the same Maven coordinate.
> >>>>
> >>>> Are you using the same version on multiple branches?
> >>>
> >>> I'm not doing anything yet.  This build is still based on Ant.  I'm
> >> trying to see what obstacles we will run into if/when we transition
> >> this build to Maven.
> >>>
> >>> I imagine I would use different versions on each branch, but I need
> >> to understand the options, and the ramifications of each.
> >>>
> >>> _______________________________________________
> >>> m2e-users mailing list
> >>> m2e-users@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/m2e-users
> >>>
> >> _______________________________________________
> >> m2e-users mailing list
> >> m2e-users@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/m2e-users
> > _______________________________________________
> > m2e-users mailing list
> > m2e-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/m2e-users
> >
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users