Re: svn commit: r1067545 - in /maven/scm/trunk/maven-scm-providers: maven-scm-providers-git/maven-scm-provider-gitexe/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/info/ maven-scm-pro

2011-02-07 Thread Olivier Lamy
Hello, Yes I know (I wanted to revert but didn't have enough time this morning). That's weird in fact because it fail here. Are you using git svn for working with maven scm ? 2011/2/7 Mark Struberg strub...@yahoo.de: Hi olivier! what was the reason for the following change? -        

Frederic Mura is out of the office.

2011-02-07 Thread Frederic . Mura
I will be out of the office starting 06/02/2011 and will not return until 14/02/2011. If your request is urgent, please contact Sebastian Jacobi or Björn Domschke.

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Mark Struberg
Fair enough, there are already lots of plugins which provide a skip logic. Most times this is even split into two options 1.) a general skip 2.) skip if executed on a parent pom I pretty often need this if I have large builds. In this case, I e.g. create a backend-parent.pom which contains all

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Kalyan Akella
Yes. Indeed the right way to accomplish this is to use profiles. But using profiles this way led me to troubles. There were times when I had to control whether or not rollbacks should happen at all after a DB update (like in production environments). To accomplish this, I had to create an other

Re: [VOTE] Relase Maven Stylus Skin 1.3

2011-02-07 Thread Emmanuel Venisse
+1 Emmanuel On Fri, Feb 4, 2011 at 11:18 PM, Olivier Lamy ol...@apache.org wrote: Hello, I'd like to release Apache Maven Stylus Skin 1.3 The staging repo is here : https://repository.apache.org/content/repositories/maven-035/ One issue fixed : http://jira.codehaus.org/browse/MSKINS-9

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Mark Struberg
we might even go 1 step further and allow skipping of plugins or even skipping single plugin-mojos. Of course this should be further investigated/designed before we start any work in maven-3.1 LieGrue, strub --- On Mon, 2/7/11, Kalyan Akella kalyan.ake...@gmail.com wrote: From: Kalyan

Re: [VOTE] Relase Maven Stylus Skin 1.3

2011-02-07 Thread Evgeny Mandrikov
+1 On Sat, Feb 5, 2011 at 01:18, Olivier Lamy ol...@apache.org wrote: Hello, I'd like to release Apache Maven Stylus Skin 1.3 The staging repo is here : https://repository.apache.org/content/repositories/maven-035/ One issue fixed : http://jira.codehaus.org/browse/MSKINS-9 And some

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Jason van Zyl
I think a declarative way to skip a plugin execution which the core can then deal with is more scalable then trying to implement this in every plugin. With some declarative nomenclature the execution plan could easily be modified to skip certain executions. On Feb 7, 2011, at 3:56 AM, Mark

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Jason van Zyl
Thanks for the writeup, these kinds of explanations are extremely helpful. On Feb 6, 2011, at 10:46 PM, Kalyan Akella wrote: A few days back, I was working with the Liquibase Maven Pluginhttp://www.liquibase.org/manual/mavenfor doing DB upgrades in my project. This plugin has 2 specific

Where to list all @threadSafe plugins and components?

2011-02-07 Thread Dennis Lundberg
Hi I'd like to start a list of which versions of plugins and components are @threadSafe. Where should we have such a list? -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands,

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Mark Struberg
yes, I just tried to explain that we have this already in lots of plugins. Btw, there are 2 basically different way to implement this: a.) extending the maven-plugin-plugin to automatically generate skip properties (similar to what we do already with the 'help' mojo) b.) extending the plugin

Re: Regarding MNG-3321 - Support for Skipping Plugin Execution

2011-02-07 Thread Jason van Zyl
On Feb 7, 2011, at 1:18 PM, Mark Struberg wrote: yes, I just tried to explain that we have this already in lots of plugins. Btw, there are 2 basically different way to implement this: a.) extending the maven-plugin-plugin to automatically generate skip properties (similar to what we

Re: Going to release Assembly Plugin 2.2.1

2011-02-07 Thread Kristian Rosenvold
to., 03.02.2011 kl. 21.39 +0100, skrev Dennis Lundberg: MASSEMBLY-522 Thread safety - It would be great if someone (Kristian?) could have a look at this one. Fixed in r1068087, based on manual code inspection and version check of dependencies. There were quite a few deprecated plugins in

Re: Where to list all @threadSafe plugins and components?

2011-02-07 Thread Kristian Rosenvold
find . -name *Mojo.java | xargs grep threadSafe I suppose that may not be good enough ;) I was hoping to get all the non-deprecated core plugins @threadSafe, and by the looks of it it's not that far off. If I subtract the retirement-candidates there only seem to be a few left. I'm not

Re: [VOTE] Release Maven Plugin Tools version 2.7

2011-02-07 Thread Hervé BOUTEMY
+1 Hervé Le dimanche 6 février 2011, Dennis Lundberg a écrit : Hi, We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139styleName= Htmlversion=16439 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Maven Plugin Tools version 2.7

2011-02-07 Thread Olivier Lamy
+1 2011/2/6 Dennis Lundberg denn...@apache.org: Hi, We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139styleName=Htmlversion=16439 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Maven Plugin Tools version 2.7

2011-02-07 Thread Kristian Rosenvold
+1 Kristian sø., 06.02.2011 kl. 00.51 +0100, skrev Dennis Lundberg: Hi, We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139styleName=Htmlversion=16439 There are still a couple of issues left in JIRA: