Re: Git Commit log with wrong encoding

Am 2016-08-06 um 20:35 schrieb Karl Heinz Marbaise: On 8/6/16 8:29 PM, Michael Osipov wrote: Am 2016-08-06 um 20:24 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 8:20 PM, Michael Osipov wrote: Am 2016-08-06 um 20:01 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 7:46 PM, Michael

Re: Git Commit log with wrong encoding

On 8/6/16 8:29 PM, Michael Osipov wrote: Am 2016-08-06 um 20:24 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 8:20 PM, Michael Osipov wrote: Am 2016-08-06 um 20:01 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 7:46 PM, Michael Osipov wrote: Am 2016-08-06 um 19:38 schrieb Karl

Re: Git Commit log with wrong encoding

Am 2016-08-06 um 20:24 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 8:20 PM, Michael Osipov wrote: Am 2016-08-06 um 20:01 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 7:46 PM, Michael Osipov wrote: Am 2016-08-06 um 19:38 schrieb Karl Heinz Marbaise: Hi, I have accidently

Re: Git Commit log with wrong encoding

Hi Michael, On 8/6/16 8:20 PM, Michael Osipov wrote: Am 2016-08-06 um 20:01 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 7:46 PM, Michael Osipov wrote: Am 2016-08-06 um 19:38 schrieb Karl Heinz Marbaise: Hi, I have accidently committed a change in Git with a log message which

Re: Git Commit log with wrong encoding

Am 2016-08-06 um 20:01 schrieb Karl Heinz Marbaise: Hi Michael, On 8/6/16 7:46 PM, Michael Osipov wrote: Am 2016-08-06 um 19:38 schrieb Karl Heinz Marbaise: Hi, I have accidently committed a change in Git with a log message which contains wrongly encoded characters... What is the best to

Re: Git Commit log with wrong encoding

Hi Michael, On 8/6/16 7:46 PM, Michael Osipov wrote: Am 2016-08-06 um 19:38 schrieb Karl Heinz Marbaise: Hi, I have accidently committed a change in Git with a log message which contains wrongly encoded characters... What is the best to handle this? git commit --amend .. and git push -f

Re: Git Commit log with wrong encoding

Am 2016-08-06 um 19:38 schrieb Karl Heinz Marbaise: Hi, I have accidently committed a change in Git with a log message which contains wrongly encoded characters... What is the best to handle this? git commit --amend .. and git push -f The ASF server will probably block history rewrite.

Git Commit log with wrong encoding

Hi, I have accidently committed a change in Git with a log message which contains wrongly encoded characters... What is the best to handle this? git commit --amend .. and git push -f ? Kind regards Karl Heinz - To

Re: Maven Core Command Line

+1 Sorry I missed this in my original implementation. I should have added a test too. -- Regards, Igor On Sat, Aug 6, 2016, at 10:15 AM, Christian Schulte wrote: > Am 08/06/16 um 16:08 schrieb Karl Heinz Marbaise: > > So the question is WDYT ? > > +1 > > Consistency. Almost all properties

Re: opinions on MJAVADOC-451

Hi all - the request for the skip-parameter started as a requirement to break an infinite loop. When I discovered how the plugin was used and told that binding the plugin to a different phase, the loop was gone. Even though, the request for the skip parameter stayed. Untrue. I opened

Re: opinions on MJAVADOC-451

Am 06.08.2016 um 11:35 schrieb Robert Scholte: fooled. So it must be javadoc:fix + compiler:compile + scm:commit. The Maven-way would be a lifecycle for things like that, right? Like the clean or site lifecycle. A general purpose "manage source code" lifecycle with phases like

Re: Maven Core Command Line

Am 08/06/16 um 16:08 schrieb Karl Heinz Marbaise: > So the question is WDYT ? +1 Consistency. Almost all properties can be overridden from the command line. I see no reason why 'maven.config' should not be overridable from the command line as well. Regards, -- Christian

Maven Core Command Line

Hi, I have a question concerning the .mvn/maven.config file..and the command line options. Currently the order is that the .mvn/maven.config file is analyzed first and afterwards the options from commandline so I thought I could do something like this: .mvn/maven.config:

Re: Question Artifacts in local cache

Hi Robert, On 8/6/16 3:42 PM, Robert Scholte wrote: Hi Karl Heinz, I think what you should do is add -am and maybe even -amd to the arguments. There should be no reason to run mvn install, even when using the incremental module builder. The more I'm thinking about this I come to the

Re: Question Artifacts in local cache

Hi Karl Heinz, I think what you should do is add -am and maybe even -amd to the arguments. There should be no reason to run mvn install, even when using the incremental module builder. Robert On Sat, 06 Aug 2016 15:38:44 +0200, Karl Heinz Marbaise wrote: Hi

Re: CI of Components...

Hi Robert, On 8/6/16 3:27 PM, Robert Scholte wrote: Hi Karl Heinz, the interface and implementation of the logger are separated. It should pick up the logger implementation as defined for the Maven runtime. If that's not the case, then we have an issue here. It works as you describe it..no

Re: opinions on MJAVADOC-451

Am 08/06/16 um 11:35 schrieb Robert Scholte: > I consider the javadoc:fix goal in the same range as the release:prepare > release:perform combination (why as is everything executed twice) and > cobertura-maven-plugin (why are the tests executed twice) and the fix-goal > is probably even

[GitHub] maven-surefire issue #110: SUREFIRE-1216: TEST-*.xml files generated by Sure...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/110 I will start release 2.19.2 with this fix. --- 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 not have this

Re: Question Artifacts in local cache

Hi Robert, On 8/6/16 3:22 PM, Robert Scholte wrote: Hi Karl Heinz, This all sounds like repository policies[1], so something that should be part of Aether. Disabling such repositories should prevent them from downloading. (assuming --offline is not an option) From a plugin of MavenProject

Re: CI of Components...

Hi Karl Heinz, the interface and implementation of the logger are separated. It should pick up the logger implementation as defined for the Maven runtime. If that's not the case, then we have an issue here. thanks, Robert On Sat, 06 Aug 2016 13:01:55 +0200, Karl Heinz Marbaise

Re: Question Artifacts in local cache

Hi Karl Heinz, This all sounds like repository policies[1], so something that should be part of Aether. Disabling such repositories should prevent them from downloading. (assuming --offline is not an option) From a plugin of MavenProject point of view I'm not interested in the logic behind

Re: PoC: Life Cycle Range

Hi, On 7/31/16 1:03 PM, Karl Heinz Marbaise wrote: Hi Robert, e.g. I still like your scm-extension idea which detects the changed files and only executes those projects + "-am -amd". Yes...this is true... So first working PoC is now there..

Re: CI of Components...

Of course the subject should be "DI of Components" .. Kind regards Karl Heinz On 8/6/16 1:01 PM, Karl Heinz Marbaise wrote: Hi, i have a question concerning DI If I have the following code: public class XX { @Inject private ScmManager scmManager; During the run in Maven this will

Question Artifacts in local cache

Hi, If I do a mvn install with a project all artifacts are being installed into my local cache.. The question I have: Can I somehow identify if an artifact is already been in my local cache or not (within a Maven plugin or extension)? Something like: if (artifact is in local cache) {

CI of Components...

Hi, i have a question concerning DI If I have the following code: public class XX { @Inject private ScmManager scmManager; During the run in Maven this will automatically looked up and injected into this attribute...so fine so far... But is it possible to provide a different

Re: opinions on MJAVADOC-451

Hi all, the request for the skip-parameter started as a requirement to break an infinite loop. When I discovered how the plugin was used and told that binding the plugin to a different phase, the loop was gone. Even though, the request for the skip parameter stayed. I consider the