maven-resources-plugin fails to create folders error

[David Hoffer]

I get the following error on occasion when building on my laptop.  Any
ideas why?  I can create those folders manually.  Also it doesn't always
fail.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-resources-plugin:2
.6:resources (default-resources) on project satcat-admin-analyst-war:
Cannot create resource output directory:
C:\svn\SP\JMS\branches\SP9-Patch7\satcat\satcat-admin-analyst-war\target\classes
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-resources-plugin:2.6:resources
(default-resources)
 on project satcat-admin-analyst-war: Cannot create resource output
directory:
C:\svn\SP\JMS\branches\SP9-Patch7\satcat\satcat-admin-analyst-war\target\classes
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot create
resource output directory:
C:\svn\SP\JMS\branches\SP9-Patch7\satcat\satcat-admin-analyst-war\target\classes
at
org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:307)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.jav:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.shared.filtering.MavenFilteringException:
Cannot create resource output directory:
C:\svn\SP\JMS\branches\SP9-Patch7\satcat\satcat-admin-analyst-war\target\classes
at
org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(DefaultMavenResourcesFiltering.java:215)
at
org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:301)
... 21 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Re: Graph of lifecycle and plugin executions

[Thomas Meyer]

Hi,

okay thanks.

Another question:

What does it mean when a mojo execution is forked?

I tried to find some documentation about it, but I failed.

The maven CLI execution event logger class seems to give some hint:
>>> fork started and so on.

Given the following pom 
https://github.com/thomasmey/einkaufsliste-server/blob/master/pom.xml

The wildfly-swarm-plugin has two executions, but the compiler step and the 
annotation preprocessor plugin seems to be executed for both mojo executions? 
Why is that? I had the idea that each mojo execution happens only once without 
all predecessors for each defined execution step, but that doesn't seem to be 
the case.

So who can bring some light in this and/or point me in the right direction and 
some documentation?

With kind regards
Thomas


Am 16.11.2015 4:04 nachm. schrieb Jason van Zyl :
>
> If you use Eclipse you can go to the project properties and from there Maven 
> > Lifecycle Mapping and you’ll see something like this:
>
>
>
> If you don’t use Eclipse you can probably use this:
>
> https://github.com/takari/maven-profiler
>
> It was made for profiling but will show you the executions. There is another 
> more recent tool that shows the lifecycle but I can’t recall at the moment 
> what that is. I will try to remember and post when I do.
>
>> On Nov 16, 2015, at 9:55 AM, Thomas Meyer  wrote:
>>
>> Hi,
>>
>> How can I print a graph of a given maven invocation with the lifecycle
>> and for each lifecycle step which plugins are executed?
>>
>> E.g.
>>
>> lifecycle:
>>  step 3: generate-sources
>>    plugin 1 - maven-processor-plugin
>>    plugin 2 - ...
>>  step 4: process-sources
>>    plugin 1 - xxx
>>
>> because in my pom, a plugin is executed several times but it shouldn't!
>> So i want to find out why. I tried with mvn -X but I couldn't see why a
>> plugin was executed twice.
>>
>> with kind regards
>> thomas
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> -
>
> First, the taking in of scattered particulars under one Idea,
> so that everyone understands what is being talked about ... Second,
> the separation of the Idea into parts, by dividing it at the joints,
> as nature directs, not breaking any limb in half as a bad carver might.
>
>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>
>
>
>
>
>
>
>
>
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Graph of lifecycle and plugin executions

[Jason van Zyl]

> On Nov 17, 2015, at 11:02 AM, Thomas Meyer  wrote:
> 
> Hi,
> 
> okay thanks.
> 
> Another question:
> 
> What does it mean when a mojo execution is forked?
> 

It corresponds to the execute annotation[1] where if you execute a goal and 
need to make sure the prerequisite lifecycle has run prior to said goal then 
Maven will “fork” a lifecycle to make sure this requirement is met. Before the 
goal is executed the lifecycle is run up to the phase you specify your goal 
needs. So your Mojo might have something like:

@Execute(phase=“LifecyclePhase.COMPILE”)

As your mojo needs to operate on compiled classes this will make sure the 
compiled classes are there.

[1]: 
https://github.com/apache/maven-plugin-tools/blob/trunk/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/Execute.java

> I tried to find some documentation about it, but I failed.
> 
> The maven CLI execution event logger class seems to give some hint:
 fork started and so on.
> 
> Given the following pom 
> https://github.com/thomasmey/einkaufsliste-server/blob/master/pom.xml
> 
> The wildfly-swarm-plugin has two executions, but the compiler step and the 
> annotation preprocessor plugin seems to be executed for both mojo executions? 
> Why is that? I had the idea that each mojo execution happens only once 
> without all predecessors for each defined execution step, but that doesn't 
> seem to be the case.
> 
> So who can bring some light in this and/or point me in the right direction 
> and some documentation?
> 
> With kind regards
> Thomas
> 
> 
> Am 16.11.2015 4:04 nachm. schrieb Jason van Zyl :
>> 
>> If you use Eclipse you can go to the project properties and from there Maven 
>> > Lifecycle Mapping and you’ll see something like this:
>> 
>> 
>> 
>> If you don’t use Eclipse you can probably use this:
>> 
>> https://github.com/takari/maven-profiler
>> 
>> It was made for profiling but will show you the executions. There is another 
>> more recent tool that shows the lifecycle but I can’t recall at the moment 
>> what that is. I will try to remember and post when I do.
>> 
>>> On Nov 16, 2015, at 9:55 AM, Thomas Meyer  wrote:
>>> 
>>> Hi,
>>> 
>>> How can I print a graph of a given maven invocation with the lifecycle
>>> and for each lifecycle step which plugins are executed?
>>> 
>>> E.g.
>>> 
>>> lifecycle:
>>>  step 3: generate-sources
>>>plugin 1 - maven-processor-plugin
>>>plugin 2 - ...
>>>  step 4: process-sources
>>>plugin 1 - xxx
>>> 
>>> because in my pom, a plugin is executed several times but it shouldn't!
>>> So i want to find out why. I tried with mvn -X but I couldn't see why a
>>> plugin was executed twice.
>>> 
>>> with kind regards
>>> thomas
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> --
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> -
>> 
>> First, the taking in of scattered particulars under one Idea,
>> so that everyone understands what is being talked about ... Second,
>> the separation of the Idea into parts, by dividing it at the joints,
>> as nature directs, not breaking any limb in half as a bad carver might.
>> 
>>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

Be not afraid of growing slowly, be only afraid of standing still.

 -- Chinese Proverb













-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Graph of lifecycle and plugin executions

[Thomas Meyer]

Am 17.11.2015 5:22 nachm. schrieb Jason van Zyl :
>
>
> > On Nov 17, 2015, at 11:02 AM, Thomas Meyer  wrote: 
> > 
> > Hi, 
> > 
> > okay thanks. 
> > 
> > Another question: 
> > 
> > What does it mean when a mojo execution is forked? 
> > 
>
> It corresponds to the execute annotation[1] where if you execute a goal and 
> need to make sure the prerequisite lifecycle has run prior to said goal then 
> Maven will “fork” a lifecycle to make sure this requirement is met. Before 
> the goal is executed the lifecycle is run up to the phase you specify your 
> goal needs. So your Mojo might have something like: 
>
> @Execute(phase=“LifecyclePhase.COMPILE”) 
>
> As your mojo needs to operate on compiled classes this will make sure the 
> compiled classes are there. 
>
> [1]: 
> https://github.com/apache/maven-plugin-tools/blob/trunk/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/Execute.java
>  

Hi,

many thanks for the hint! I understand it now. So basically every mojo callable 
from command line somehow need to set this annotation and all mojos only usable 
in the pom doesn't!

Thank you!

>
> > I tried to find some documentation about it, but I failed. 
> > 
> > The maven CLI execution event logger class seems to give some hint: 
>  fork started and so on. 
> > 
> > Given the following pom 
> > https://github.com/thomasmey/einkaufsliste-server/blob/master/pom.xml 
> > 
> > The wildfly-swarm-plugin has two executions, but the compiler step and the 
> > annotation preprocessor plugin seems to be executed for both mojo 
> > executions? Why is that? I had the idea that each mojo execution happens 
> > only once without all predecessors for each defined execution step, but 
> > that doesn't seem to be the case. 
> > 
> > So who can bring some light in this and/or point me in the right direction 
> > and some documentation? 
> > 
> > With kind regards 
> > Thomas 
> > 
> > 
> > Am 16.11.2015 4:04 nachm. schrieb Jason van Zyl : 
> >> 
> >> If you use Eclipse you can go to the project properties and from there 
> >> Maven > Lifecycle Mapping and you’ll see something like this: 
> >> 
> >> 
> >> 
> >> If you don’t use Eclipse you can probably use this: 
> >> 
> >> https://github.com/takari/maven-profiler 
> >> 
> >> It was made for profiling but will show you the executions. There is 
> >> another more recent tool that shows the lifecycle but I can’t recall at 
> >> the moment what that is. I will try to remember and post when I do. 
> >> 
> >>> On Nov 16, 2015, at 9:55 AM, Thomas Meyer  wrote: 
> >>> 
> >>> Hi, 
> >>> 
> >>> How can I print a graph of a given maven invocation with the lifecycle 
> >>> and for each lifecycle step which plugins are executed? 
> >>> 
> >>> E.g. 
> >>> 
> >>> lifecycle: 
> >>>  step 3: generate-sources 
> >>>    plugin 1 - maven-processor-plugin 
> >>>    plugin 2 - ... 
> >>>  step 4: process-sources 
> >>>    plugin 1 - xxx 
> >>> 
> >>> because in my pom, a plugin is executed several times but it shouldn't! 
> >>> So i want to find out why. I tried with mvn -X but I couldn't see why a 
> >>> plugin was executed twice. 
> >>> 
> >>> with kind regards 
> >>> thomas 
> >>> 
> >>> 
> >>> 
> >>> - 
> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org 
> >>> For additional commands, e-mail: users-h...@maven.apache.org 
> >>> 
> >> 
> >> Thanks, 
> >> 
> >> Jason 
> >> 
> >> -- 
> >> Jason van Zyl 
> >> Founder, Takari and Apache Maven 
> >> http://twitter.com/jvanzyl 
> >> http://twitter.com/takari_io 
> >> - 
> >> 
> >> First, the taking in of scattered particulars under one Idea, 
> >> so that everyone understands what is being talked about ... Second, 
> >> the separation of the Idea into parts, by dividing it at the joints, 
> >> as nature directs, not breaking any limb in half as a bad carver might. 
> >> 
> >>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> > 
> > - 
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org 
> > For additional commands, e-mail: users-h...@maven.apache.org 
>
> Thanks, 
>
> Jason 
>
> -- 
> Jason van Zyl 
> Founder, Takari and Apache Maven 
> http://twitter.com/jvanzyl 
> http://twitter.com/takari_io 
> - 
>
> Be not afraid of growing slowly, be only afraid of standing still. 
>
> -- Chinese Proverb 
>
>
>
>
>
>
>
>
>
>
>
>
>
> - 
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org 
> For additional commands, 

Re: regex-property goal of build-helper-maven-plugin documentation is incorrect

[Alexander Kriegisch]

> The site just hasn't been regenerated and uploaded, I guess?

Then I figure it is not really fixed. An unpublished documentation fix is not 
worth a lot. Someone is lacking a Definition of Done here. ;-) Sorry for being 
such a smart-ass, but I could not resist.
-- 
Alexander Kriegisch
http://scrum-master.de


> Am 17.11.2015 um 04:54 schrieb Curtis Rueden :
> 
> Hi Steve,
> 
>> Can someone fix it?
> 
> I was going to respond with "You can!" But it seems it was already fixed
> almost a year ago:
> 
> https://github.com/mojohaus/build-helper-maven-plugin/commit/cdaa047253fdcb64f94e81a6e8575191b5919ab0
> 
> The site just hasn't been regenerated and uploaded, I guess?
> 
> -Curtis
> 
>> On Mon, Nov 16, 2015 at 5:41 PM, Steve Cohen  wrote:
>> 
>> Documentation on the regex-property goal of build-helper-maven-plugin at
>> http://www.mojohaus.org/build-helper-maven-plugin/usage.html has an
>> error.  This error has persisted for some time and has proliferated around
>> the Internet, for example in several Stack Overflow posts.
>> 
>> The error is this:
>> 
>> In the section marked "Set a property by applying a regex replacement to a
>> value",
>> under , we see the  element exampled as
>> 
>> $\{project.version}
>> 
>> This is incorrect.  The goal will fail if the backslash is included and
>> succeed if it is omitted.  From my basic understanding of regex and of
>> Maven, it seemed wrong and I have verified that it is.
>> 
>> It's probably a typo, one that has confused some people, for example, on
>> Stack Overflow:
>> 
>> 
>> http://stackoverflow.com/questions/17516313/possible-bug-when-parsing-properties-with-goal-regex-property-of-build-helper
>> 
>> Can someone fix it?
>> 
>> Steve Cohen
>> 


smime.p7s
Description: S/MIME cryptographic signature

Re: Graph of lifecycle and plugin executions

[Jason van Zyl]

> On Nov 17, 2015, at 12:06 PM, Thomas Meyer  wrote:
> 
> Am 17.11.2015 5:22 nachm. schrieb Jason van Zyl :
>> 
>> 
>>> On Nov 17, 2015, at 11:02 AM, Thomas Meyer  wrote: 
>>> 
>>> Hi, 
>>> 
>>> okay thanks. 
>>> 
>>> Another question: 
>>> 
>>> What does it mean when a mojo execution is forked? 
>>> 
>> 
>> It corresponds to the execute annotation[1] where if you execute a goal and 
>> need to make sure the prerequisite lifecycle has run prior to said goal then 
>> Maven will “fork” a lifecycle to make sure this requirement is met. Before 
>> the goal is executed the lifecycle is run up to the phase you specify your 
>> goal needs. So your Mojo might have something like: 
>> 
>> @Execute(phase=“LifecyclePhase.COMPILE”) 
>> 
>> As your mojo needs to operate on compiled classes this will make sure the 
>> compiled classes are there. 
>> 
>> [1]: 
>> https://github.com/apache/maven-plugin-tools/blob/trunk/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/Execute.java
>>  
> 
> Hi,
> 
> many thanks for the hint! I understand it now. So basically every mojo 
> callable from command line somehow need to set this annotation and all mojos 
> only usable in the pom doesn’t!
> 

Not necessarily. A mojo is not required to fork, only if it has prerequisites 
from the lifecycle. Many mojos invoked from the CLI are fully independent and 
don’t specify a phase or fork phase at all. I personally don’t recommend this 
type of setup, it’s either part of the lifecycle so run it from the lifecycle 
or it’s not.

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

A master in the art of living draws no sharp distinction between his work and 
his play; his labor and his leisure; his mind and his body; his education and 
his recreation. He hardly knows which is which. He simply pursues his vision of 
excellence through whatever he is doing, and leaves others to determine whether 
he is working or playing. To himself, he always appears to be doing both. 

  -- François-René de Chateaubriand












-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: regex-property goal of build-helper-maven-plugin documentation is incorrect

[Dan Tran]

I will either push a new release out this weekend or update the site

Thanks

-Dan

On Tue, Nov 17, 2015 at 10:21 AM, Alexander Kriegisch <
alexan...@kriegisch.name> wrote:

> The site just hasn't been regenerated and uploaded, I guess?
>
>
> Then I figure it is not really fixed. An unpublished documentation fix is
> not worth a lot. Someone is lacking a Definition of Done here. ;-) Sorry
> for being such a smart-ass, but I could not resist.
> --
> Alexander Kriegisch
> http://scrum-master.de
>
>
> Am 17.11.2015 um 04:54 schrieb Curtis Rueden :
>
> Hi Steve,
>
> Can someone fix it?
>
>
> I was going to respond with "You can!" But it seems it was already fixed
> almost a year ago:
>
>
> https://github.com/mojohaus/build-helper-maven-plugin/commit/cdaa047253fdcb64f94e81a6e8575191b5919ab0
>
> The site just hasn't been regenerated and uploaded, I guess?
>
> -Curtis
>
> On Mon, Nov 16, 2015 at 5:41 PM, Steve Cohen 
> wrote:
>
> Documentation on the regex-property goal of build-helper-maven-plugin at
>
> http://www.mojohaus.org/build-helper-maven-plugin/usage.html has an
>
> error.  This error has persisted for some time and has proliferated around
>
> the Internet, for example in several Stack Overflow posts.
>
>
> The error is this:
>
>
> In the section marked "Set a property by applying a regex replacement to a
>
> value",
>
> under , we see the  element exampled as
>
>
> $\{project.version}
>
>
> This is incorrect.  The goal will fail if the backslash is included and
>
> succeed if it is omitted.  From my basic understanding of regex and of
>
> Maven, it seemed wrong and I have verified that it is.
>
>
> It's probably a typo, one that has confused some people, for example, on
>
> Stack Overflow:
>
>
>
>
> http://stackoverflow.com/questions/17516313/possible-bug-when-parsing-properties-with-goal-regex-property-of-build-helper
>
>
> Can someone fix it?
>
>
> Steve Cohen
>
>
>

[ANN] Apache Maven Version 3.3.9 Released

[Karl Heinz Marbaise]

The Apache Maven team is pleased to announce the release of 
Apache Maven 3.3.9.

http://maven.apache.org/

You can download the appropriate sources etc. from the download page

http://maven.apache.org/download.cgi

Release Notes - Apache Maven Version 3.3.9

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12333074

Code Contributors of this release:

 * Martin Schäf
 * Stuart McCulloch
 * sugartxy
 * Robert Stern 
 * Florencia Tarditti 
 * tssp
 * Dave Syer
 * Joseph Walton
 * Stephen Kitt
 * Anton Tanasenko
 * Tang Xinye
 * Ben Caradoc-Davies

Issue Reporters of this release:

 * Brandon Enochs
 * Martin Schäf
 * Stephan Schroevers
 * Christian Schlichtherle
 * Brandon Enochs
 * Anders Forsell
 * Shubham Chaurasia
 * Keith Turner
 * Jonathan Radon
 * Ben Caradoc-Davies

Many thanks to contributors and reporters for the support and time.

Participants to VOTE of the Maven 3.3.4 till the Maven 3.3.9 Release:

 * Francisco Collao Gárate
 * Anton Tanasenko
 * Mark Derricut
 * Eric Barboni
 * Jieren
 * Jörg Schaible
 * Gary Gregory
 * Mark Derricut

Many thanks to those who tested the Maven releases 
and thanks for their support as well.


Bugs:

 * [MNG-5297] - Mark  as deprecated for compile-time 
enforcement. (Contributor: Joseph Walton)
 * [MNG-5649] - Use Commons Lang's Validate to intercept invalid input
 * [MNG-5681] - Properties on command line with leading or trailing quotes are 
stripped
 * [MNG-5721] - Possible NullPointerException in 
org.apache.maven.repository.MetadataResolutionResult (reporter/contributor 
Martin Schäf ).
 * [MNG-5786] - Variable maven.multiModuleProjectDirectory may be set 
incorrectly (reporter Stephan Schroevers).
 * [MNG-5787] - Moving from Maven 3.0.5 to 3.3.3 breaks plugins with some 
dependencies on the class path (reporter Christian Schlichtherle).
 * [MNG-5796] - mvn fails when the current directory is a root drive on Windows 
(reporter Brandon Enochs).
 * [MNG-5812] - Project base dir not fully working in Cygwin (contributor tssp).
 * [MNG-5813] - Make MAVEN_OPTS env variable with mvnDebug correctly
 * [MNG-5816] - Empty maven.config cause Maven to exit with failure 
(contributor tssp)
 * [MNG-5840] -  is used if the groupId and artifactId match 
irrespective of the version
 * [MNG-5858] - mvn script fails to locate .mvn in current directory 
(contributor Dave Syer).
 * [MNG-5877] - maven-aether-provider/maven-compat does not always generate 
snapshot versions using Gregorian calendar year (contributor Joseph Walton; 
reporter Anders Forsell).
 * [MNG-5882] - Nonportable shell constructs cause bin/mvn errors on Debian 
(contributor Ben Caradoc-Davies)
 * [MNG-5884] - mvn script doesn't handle directories containing spaces 
(contributor Stephen Kitt).
 * [MNG-5886] - Broken link of 'Building Maven' in README.md on Github 
(reporter Shubham Chaurasia).
 * [MNG-5891] - Log file command line option description contains an extra word 
(reporter Keith Turner).
 * [MNG-5898] - Multi-module build with ear fails to resolve war in 3.3.3 
(reporter Jonathan Radon).
 * [MNG-5907] - org.apache.maven.repository.internal.RemoteSnapshotMetadataTest 
fails to start at midnight

Improvements:

 * [MNG-5780] - upgrade Java minimum version prerequisite from Java 6 to Java 7
 * [MNG-5805] - Custom packaging types: configuring DefaultLifecycleMapping 
mojo executions (contributor Anton Tanasenko).
 * [MNG-5818] - Disallow the programmatic injection of project dependencies
 * [MNG-5844] - Close IO Streams in finally or try-with-resource statement 
(contributor Tang Xinye)
 * [MNG-5871] - make url inheritance algorithm more visible
 * [MNG-5888] - Update used modello version from 1.8.1 to 1.8.3
 * [MNG-5892] - Removing par lifecycle from default life cycle bindings
 * [MNG-5893] - Make used plugin version for maven-resources-plugin in 
default-bindings.xml consistent
 * [MNG-5894] - Removed binding for maven-ejb3-plugin from default binding
 * [MNG-5905] - Maven build does not work with Maven 2.2.1
 * [MNG-5906] - Use canonical name for UTC timezone
 * [MNG-5911] - Upgrade maven-parent to version 27
 * [MNG-5915] - Upgrade Wagon version to 2.10
 * [MNG-5921] - Upgraded to plexus-components 1.6 that uses asm 5.x
 * [MNG-5922] - Upgrade plexus-utils to 3.0.22 to support combine.id as 
configuration attribute for Map merging
 * [MNG-5923] - Switch to official Guice 4.0 (reporter/contributor: Stuart 
McCulloch)
 * [MNG-5924] - Upgrade to Eclipse/Sisu 0.3.2 (reporter/contributor: Stuart 
McCulloch).
 * [MNG-5925] - Update animal-sniffer-maven-plugin to 1.14. MANIMALSNIFFER-49 
required when building with JDK9

Task:

 * [MNG-5887] - update Modello site url


Enjoy,

- The Apache Maven team

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org