I think something went wrong here.
This project use to be the aggregator project in subversion.
In the early days there were read-only repos in github of our subversion repos.
However, when we moved everything to gitbox every module should have gotten
their own repository.
OK, let me know when the repo situation is sorted out. I don't think
this is on anyone's critical path just yet.
On Tue, Dec 24, 2019 at 6:01 AM Robert Scholte wrote:
>
> I think something went wrong here.
> This project use to be the aggregator project in subversion.
> In the early days there
On Mon 23 Dec 2019 at 15:44, Benjamin Marwell wrote:
> Furthermore,
>
> if we do not drop using that method, maven will throw an exception. Maven
> will, not checkstyle.
>
> I do not think that should be happening (from a user perspective).
>
> It's an easy fix for maven. As soon as the
Elliotte,
It is better that you create branches on the shared repository following
these best practices:
- name it with the jira id MNGM-123
- include the jira id in the commit msg (at least for the first one)
When you merge the branch to the master branch you have to squash all of
the commits
