|Re: [cross-project-issues-dev] Versioning of artifacts in main and feature branches|
Am 06.02.2014 um 13:45 schrieb Ken Lee <Ken.Lee@xxxxxxxxx>:
Since some other project teams rely on the changes made in the feature branch, we had to set up another CI build that also deploys the build artifacts to the same Maven repository.
As you figured out already, maintaining different versions on feature branches is hard for merges and also prone to error. I think in the sentence above you describe the root cause of your problem. Artifacts from feature branches shouldn’t go into the master branch Maven repository. I suggest deploying them to separate, temp. repositories which you’ll throw away after merging the feature back into a branch. You could then work with profiles and local settings to make Maven using those repositories for look ups.
Description: Message signed with OpenPGP using GPGMail