Cool.
I think core-it is mandatory too for such new feature !
2012/9/9 Jason van Zyl :
> Here they are:
>
> https://jira.codehaus.org/browse/MNG-5343
> https://jira.codehaus.org/browse/MNG-5344
>
> On Sep 7, 2012, at 11:37 AM, Olivier Lamy wrote:
>
>> Maybe I miss something but we don't have any
Log4j2 have a nice impl of slf4j:
http://logging.apache.org/log4j/2.x/performance.html
Are people able to override with putting an other impl in $M2_HOME/lib/ext ?
2012/9/9 Jason van Zyl :
> To complete this work and unify all the logging under SLF4J can we pick an
> implementation?
>
> I have e
Here they are:
https://jira.codehaus.org/browse/MNG-5343
https://jira.codehaus.org/browse/MNG-5344
On Sep 7, 2012, at 11:37 AM, Olivier Lamy wrote:
> Maybe I miss something but we don't have any associated jira entry for
> reference in release notes neither core it test.
> Do you have a bit of t
To complete this work and unify all the logging under SLF4J can we pick an
implementation?
I have everything routing through SLF4J so everything using Plexus loggers or
SLF4J loggers use the same SLF4J implementation. Even if we pick the simple
implementation for now I can completely clean up t
Le samedi 8 septembre 2012 21:14:21 Olivier Lamy a écrit :
> I have removed use of .repository.
> Looks better
great!
Thank you: ITs are now ok with M2!!!
> except this one
> https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3/ws/ma
> ven-compiler-plugin/target/it/includes-exclu
I have removed use of .repository.
Looks better
except this one
https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3/ws/maven-compiler-plugin/target/it/includes-excludes/build.log
2012/9/8 Hervé BOUTEMY :
> it still doesn't work
> I can't understand why the failsafe IT doesn't fi
Hi,
The vote has passed with the following result.
+1 (binding): Mark Struberg, Emmanuel Venisse, Olivier Lamy
+1 (non binding): Tony Chemit
I will continue the release process.
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
it still doesn't work
I can't understand why the failsafe IT doesn't find actual SNAPSHOT [1]
when the artifact is in the local repo[2] then should be found
something strange: the output in [1] shows that local repo used is
-Dmaven.repo.local=/home/jenkins/jenkins-slave/workspace/maven-plugins-IT
+1 on bump to 3.1
On Friday, 7 September 2012, Anders Hammar wrote:
> I know. But there wasn't much visible change in v3.0 either. And I'm
> thinking that it would be easier to communicate a dependency on Maven
> 3.1+ than 3.0.5+ if some component utilizes the JSR330 support.
>
> Version numbers
