On 4/27/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I'll look at the issue created by Jim, but it was in my planning to implement
the branch creation in the next month.
Emmanuel
There is another, slightly related issue. From time to time, you want
to merge the bug fixes from the maintenance branch back to the trunk.
The problem is, that you get merge conflicts on all the POMs because
of the version fields that have changed on the trunk and on the
maintenance branch. This makes again some manual intervention
necessary. I don't have a good solution for that either. Ideas are
welcome.
I think part of the problem with branching and merging is that even if
you keep all the module versions in sync you have the version
information literally written in every POM in your project (as version
of the artifact or as version of the parent POM). It would be much
less painful if there was just one place to adapt. However, I don't
see how a central specification of the version could be achieved
without loosing the ability to build modules individually.
- Henry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
