[GitHub] maven pull request: Support directories with spaces in mvn

Github user michael-o commented on the pull request: https://github.com/apache/maven/pull/63#issuecomment-136840652 Does this apply to Windows too? Can you please open a JIRA issue for that? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] maven pull request: Support directories with spaces in mvn

GitHub user skitt opened a pull request: https://github.com/apache/maven/pull/63 Support directories with spaces in mvn find_maven_basedir() doesn't handle a current working directory containing spaces; this patch fixes this behaviour. You can merge this pull request into a Git

Re: maven-scm-provider-gitexe > 1.8.1 behavior changed?

Hi Tobias, You're using an old maven-release-plugin version: did you try with latest version, which is currently 2.5.2? Seems MRELEASE-812, fixed in 2.5, a good candidate to an explanation to the issue you're facing Regards, Hervé Le mardi 1 septembre 2015 22:27:47 Tobias Hochgürtel a écrit

Re: Configuring Shared Mojo Components with DI

No, not possible to inject mojo parameters into plain components. With recent versions of Maven, it is possible to inject MavenSession, MavenProject and MojoExecution into components. Not example what you are asking, but maybe close enough. Be careful not to inject those into singleton components

Configuring Shared Mojo Components with DI

Hi there, just wondering whether it is possible to configure a component shared between different Mojos using DI instead of using inheritance over composition? Any ideas? @Mojo(name = mojo1) class Mojo1 { @Component(name = bla) } @Mojo(name = mojo2) class Mojo2 { @Component(name = bla)

Re: Another JIRA cleanup

ok for me: I didn't like it the first time, but with experience, this cause less trouble than manual dust cleaning in Jira issues Regards, Hervé Le dimanche 30 août 2015 21:31:43 Michael Osipov a écrit : > Hi folks, > > some of you might remember that I have closed a bunch of issues some >

Re: releasing Maven Project Info Report Plugin 2.8.1

MPIR-331 is not an issue with MPIR: should be closed as "not a bug" (at least not a bug in MPIR) Regards, Hervé Le lundi 31 août 2015 10:28:45 Michael Osipov a écrit : > Am 2015-08-30 um 22:40 schrieb Hervé BOUTEMY: > > I want to release MPIR 2.8.1 with MPIR-300 fixed, since it is required for

Testing that a plugin works in --offline

Is there a way in the invoker to test offline mode? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Wagon SSH 2.10

Hi Karl, Could you please release this? Very much appreciated -Dan On Wed, Aug 26, 2015 at 11:16 PM, Anthony Whitford wrote: > Any chance we could get a Maven Wagon SSH 2.10 release? (I’ve been > waiting for WAGON-413.) > >

Re: Testing that a plugin works in --offline

On Tue, Sep 1, 2015 at 5:30 PM, Karl Heinz Marbaise wrote: > Hi Benson, > > you can add the -o option in invoker.properties... > and then you are in a limited environment...the default is having the local > repository ${home}/.m2/ as remote repository ... > > The problem is

maven-scm-provider-gitexe > 1.8.1 behavior changed?

Dear Maven Developers, I had some troubles with Maven Release plugin in combination with Maven SCM Provider gitexe plugin as an dependency. I found the following Stackoverflow Question which helped me to get the known behavior back.

Re: Testing that a plugin works in --offline

Hi Benson, you can add the -o option in invoker.properties... and then you are in a limited environment...the default is having the local repository ${home}/.m2/ as remote repository ... The problem is that your machine might be connected to the internet...and a plugin which is inside can