Am 02/19/17 um 04:38 schrieb Hervé BOUTEMY:
> then I'm not sure checking rules on what is inside an artifact while
> publishing in Central is the right thing to do: we don't do it currently
> (checking that package names are consistent with groupId), then I feel we
> should not do it either for
After some digging I think the fix for MNG-6078 is incorrect. I have taken
an initial stab at what I believe to be a more correct approach:
https://github.com/apache/maven/tree/mng-6078-take-2
If the integration tests pass:
https://builds.apache.org/job/maven-3.x-jenkinsfile/job/mng-6078-take-2/
t
On Sat, 18 Feb 2017 12:46:32 +0100, Robert Scholte
wrote:
On Thu, 16 Feb 2017 19:11:33 +0100, Brian Fox wrote:
I generally agree the concerns were mostly ignored. Specifically the
dangers in not carefully approaching and setting best practices in the
names, thereby willfully ignoring what
On Mon, 20 Feb 2017 02:17:12 +0100, Christian Schulte
wrote:
Am 02/20/17 um 01:53 schrieb Christian Schulte:
Hi,
I cannot build 'maven-dependency-analyzer' trunk on Windows. Is there
some dependency I could upgrade to get this going? This is what I am
doing locally:
svn checkout /repos
GitHub user jodastephen opened a pull request:
https://github.com/apache/maven-release/pull/13
MRELEASE-980 Allow commit comments to be controlled
Provide the ability to override commit comments from configuration.
You can merge this pull request into a Git repository by running:
GitHub user hmemcpy opened a pull request:
https://github.com/apache/maven/pull/106
Fixing a typo in 'lifecycle'
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hmemcpy/maven patch-1
Alternatively you can review and apply these
