Re: svn commit: r1711655 - /maven/shared/trunk/maven-shared-components/src/site/site.xml

uh, a m-site-p regression? I'll have to investigate... Regards, Hervé Le dimanche 1 novembre 2015 13:58:02 Karl Heinz Marbaise a écrit : > On 11/1/15 9:52 AM, Hervé BOUTEMY wrote: > > why copy/paste? isn't it inherited? > > It is not inherited... > > That's the reason why i change the maven-sh

Re: [VOTE] Maven 3.3.8

+1 using it without any issue notice I updated LATEST site http://maven.apache.org/ref/3-LATEST/ (just using deploySite.sh script) Regards, Hervé Le vendredi 30 octobre 2015 09:58:11 Jason van Zyl a écrit : > Hi, > > Time to release Maven 3.3.8! > > Here is a link to the issues resolved: > ht

[GitHub] maven-plugins pull request: Cleanning log

GitHub user luanpotter opened a pull request: https://github.com/apache/maven-plugins/pull/68 Cleanning log Removed `System.out.println` call that was cluttering the maven log. If it was crucial or important, I'm glad to change to another solution, like a conditional or somethin

[GitHub] maven pull request: MNG-3525-maven-settings - settings.xml allowin...

Github user nitram509 commented on the pull request: https://github.com/apache/maven/pull/71#issuecomment-152829442 Thank you for this fast feedback. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does n

[GitHub] maven pull request: MNG-3525-maven-settings - settings.xml allowin...

Github user jvanzyl commented on the pull request: https://github.com/apache/maven/pull/71#issuecomment-152828665 Looking through the changes, definitely useful. Just a suggestion for your for your Git commit messages: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.ht

Re: easing Maven parent poms management

+1. I had infra set up a staging group for us some time ago to make this easier; you can stage all of them and test by using the repo URL for the staging group. On Sun, Nov 1, 2015 at 8:00 AM, Karl Heinz Marbaise wrote: > Hi, > > +1 for releasing them in one go... > > > On 11/1/15 10:03 AM, Hervé

Re: easing Maven parent poms management

Hi, +1 for releasing them in one go... On 11/1/15 10:03 AM, Hervé BOUTEMY wrote: Currently, we have 5 Maven parent POMs [1] (not counting Doxia), each with its own release cycle. Releasing each separately is a pain. And knowing which pom is at which version is a pain also. Unfortunately true.

Re: svn commit: r1711655 - /maven/shared/trunk/maven-shared-components/src/site/site.xml

On 11/1/15 9:52 AM, Hervé BOUTEMY wrote: why copy/paste? isn't it inherited? It is not inherited... That's the reason why i change the maven-shared-components pom to use it in other shared components... Regards, Hervé Le samedi 31 octobre 2015 17:47:33 khmarba...@apache.org a écrit : Au

[GitHub] maven pull request: MNG-3525-maven-settings - settings.xml allowin...

GitHub user nitram509 opened a pull request: https://github.com/apache/maven/pull/71 MNG-3525-maven-settings - settings.xml allowing mirror definitions inside profiles This improves user settings to have a mirrors list switched on/off via Maven profile. See commit messages for

aggregation and dependency resolution

I have been struggling with creating an aggregate goal that successfully works and I was hoping someone on this list could help. The plugin is dependency-check-maven ; it performs identification (CPE

Re: easing Maven parent poms management

+1 for releasing them at the same time where that makes sense The only case I can see against is if we want to aggregate more into the release scope, eg Say we just take all the skins and the skins parent and move them all into a guy repo and release the lot of them every time? In other news, on

Re: Maven Release Version Policy

The whole point of this (to my mind) is when running with -B when you can't ask the user On Sunday 1 November 2015, Hervé BOUTEMY wrote: > ok, then what could be done is only a check afterwards that the version > chosen > by the user is consistent with measures on code evolutions > > another ide

Re: svn commit: r1711655 - /maven/shared/trunk/maven-shared-components/src/site/site.xml

why copy/paste? isn't it inherited? Regards, Hervé Le samedi 31 octobre 2015 17:47:33 khmarba...@apache.org a écrit : > Author: khmarbaise > Date: Sat Oct 31 17:47:33 2015 > New Revision: 1711655 > > URL: http://svn.apache.org/viewvc?rev=1711655&view=rev > Log: > [MPOM-91] Use fluido skin. > >

Re: [VOTE] Maven 3.3.8

On 31 Oct 2015, at 5:58, Jason van Zyl wrote: > Vote open for 72 hours. +1 here. Looking good from my builds... -- Mark Derricutt http://www.theoryinpractice.net http://www.chaliceofblood.net http://plus.google.com/+MarkDerricutt http://twitter.com/talios http://facebook.com/mderricutt sign

Re: Maven Release Version Policy

ok, then what could be done is only a check afterwards that the version chosen by the user is consistent with measures on code evolutions another idea: perhaps we should have the API propose multiple versions instead of only one. This would help people understand that the API is only about gues

easing Maven parent poms management

Currently, we have 5 Maven parent POMs [1] (not counting Doxia), each with its own release cycle. Releasing each separately is a pain. And knowing which pom is at which version is a pain also. What would you think of: 1. setting the same version to every Maven parent POM: next would be version