You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benjamin Bentmann <be...@apache.org> on 2010/04/23 15:05:57 UTC
[ANN] Apache Maven 3.0-beta-1 Released
The Maven team is pleased to announce the release of Apache Maven
3.0-beta-1.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source and binary distributions are listed in our download
section:
http://maven.apache.org/download.html
A major goal of Maven 3.0 is to be compatible, to the extent possible,
with existing plugins and projects designed for Maven 2.x. Users
interested in testing this beta release should have a glance at the
compatibility notes for known differences between Maven 3.0 and Maven 2.x:
http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
If you encounter unexpected problems while using Maven 3.0-beta-1,
please feel free to contact us via the Maven developer list:
http://maven.apache.org/mail-lists.html
Release Notes - Maven 2 & 3 - Version 3.0-beta-1
** Bug
* [MNG-1751] - merging metadata doesn't fail when timestamp is in
the future
* [MNG-2103] - Inheritance of <plugin> overrides that of <execution>
* [MNG-2222] - dependency to dependency without source code fails
* [MNG-2276] - profile activation by property doesn't work with
properties defined in settings.
* [MNG-2994] - Snapshot repositories are not checked when using ranges
* [MNG-3092] - Version ranges with non-snapshot bounds can contain
snapshot versions
* [MNG-3133] - DefaultModelInheritence::appendPath assumes it is
operating on interpolated/literal paths
* [MNG-3470] - Build does not fail on corrupted POM even with
checksumPolicy=fail
* [MNG-3477] - Authentication failures on dependency download
aren't reported
* [MNG-3529] - mvn -Da=" " throws an excepltion
* [MNG-3616] - Null Pointer Exception when mirrorOf missing from
mirror in settings.xml
* [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where
inherited == false
* [MNG-4022] - Incorrect merge behavior using profile driven plugin
configuration
* [MNG-4326] - Maven should not check snapshot repositories for
dependencies in the reactor
* [MNG-4418] - Dependency resolution appears to misbehave if a
remote repository uses the id "local"
* [MNG-4453] - [regression] Plugin versions defined in a lifecycle
mapping are not respected
* [MNG-4555] - mvn archetype:generate -o (offline) still results in
a "checking updates from central"
* [MNG-4580] - Plugin dependencies for module ignored when building
from aggregator project using direct plugin invocation
* [MNG-4586] - Plugin prefix can't be resolved from plugin
management if management entry is missing plugin version
* [MNG-4590] - [regression] System properties are no longer
interpolated in imported POMs
* [MNG-4600] - [regression] Optional flag from dependency
management applied to dependencies
* [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3
and multiple modules
* [MNG-4625] - Interpolation of settings.xml fails if an
expression's value contains XML markup
* [MNG-4629] - [regression] POM validation fails upon non-existing
system-scope dependency
* [MNG-4632] - Class loading is not thread-safe
** Improvement
* [MNG-1701] - Validate that a plugin is not configured twice in
the pom
* [MNG-2187] - Improve error message when the pom is encoded in the
wrong charset
* [MNG-2741] - [regression] Meaningless error message: "Error
transferring file"
* [MNG-3004] - Allow build lifecycle to execute projects in parallel
* [MNG-3779] - Improve error message when trying to execute mojo
with no pom.xml
* [MNG-4162] - Removal of all reporting logic from the core of Maven
* [MNG-4194] - API to safely release of plugin realms
* [MNG-4591] - Enhance the download rate output to include
downloaded file name
* [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM
* [MNG-4619] - Issue warning in case parent.relativePath points at
POM with different groupId/artifactId
* [MNG-4623] - model parsing errors can be less helpful in Maven 3
* [MNG-4628] - ReactorArtifactRepository is not setup soon enough
for AbstractMavenLifecycleParticipant#afterProjectsRead
* [MNG-4634] - Allow custom lifecycles
** Task
* [MNG-3917] - Complete the POM construction tests which will be
the validation for the specification
Enjoy,
-The Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re : [ANN] Apache Maven 3.0-beta-1 Released
Posted by Stephen Connolly <st...@gmail.com>.
Known issue...
On 26 April 2010 13:38, Julien HENRY <he...@yahoo.fr> wrote:
> Hi,
>
> I have the following error using Maven 3.0-beta-1. Before trying to
> reproduce on a smaller project, could you please have a look and tell me if
> this is a known issue. The only similar issue I have found is: MENFORCER-55
>
> $ mvn versions:display-plugin-updates -X
> [...]
> [DEBUG] final aggregate version map
> org.apache.maven.plugins:maven-clean-plugin:2.3
> org.apache.maven.plugins:maven-surefire-plugin:2.4.3
> org.codehaus.mojo:exec-maven-plugin:1.1
> org.apache.maven.plugins:maven-ear-plugin:2.3.2
> org.apache.maven.plugins:maven-war-plugin:2.1-beta-1
> org.apache.maven.plugins:maven-jar-plugin:2.3
> org.apache.maven.plugins:maven-source-plugin:2.1.1
> org.apache.maven.plugins:maven-dependency-plugin:2.1
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4
> org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2
> org.apache.maven.plugins:maven-install-plugin:2.3
> org.apache.maven.plugins:maven-site-plugin:2.0.1
> org.apache.maven.plugins:maven-release-plugin:2.0-beta-8
> [DEBUG] after adding local pluginManagement
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2.250s
> [INFO] Finished at: Mon Apr 26 14:18:46 CEST 2010
> [INFO] Final Memory: 6M/19M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates
> (default-cli) on project myproject: Execution default-cli of goal
> org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates
> (default-cli) on project myproject: Execution default-cli of goal
> org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:149)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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.PluginExecutionException: Execution
> default-cli of goal
> org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133)
> ... 19 more
> Caused by: java.lang.NullPointerException
> at
> org.codehaus.plexus.util.ReflectionUtils.getValueIncludingSuperclasses(ReflectionUtils.java:179)
> at
> org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getBoundPlugins(DisplayPluginUpdatesMojo.java:660)
> at
> org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getLifecyclePlugins(DisplayPluginUpdatesMojo.java:619)
> at
> org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getProjectPlugins(DisplayPluginUpdatesMojo.java:1096)
> at
> org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.execute(DisplayPluginUpdatesMojo.java:277)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
> ... 20 more
>
>
>
> It seems to works fine with Maven 2.2.1 (in fact it is taking a very long
> time to check update of each plugin so the execution with Maven 2 is still
> not completed, but with Maven 3 the NPE occurs after few seconds only).
>
> Regards,
>
> Julien
>
>
> ----- Message d'origine ----
> > De : Benjamin Bentmann <be...@apache.org>
> > À : announce@maven.apache.org; users@maven.apache.org
> > Cc : Maven Developers List <de...@maven.apache.org>
> > Envoyé le : Ven 23 avril 2010, 15 h 05 min 57 s
> > Objet : [ANN] Apache Maven 3.0-beta-1 Released
> >
> > The Maven team is pleased to announce the release of Apache Maven
> > 3.0-beta-1.
>
> Maven is a project comprehension and build tool, designed to
> > simplify the process of maintaining a healthy development lifecycle for
> your
> > project. You can read more here:
>
>
> > href="http://maven.apache.org/" target=_blank
> > >http://maven.apache.org/
>
> Downloads of source and binary
> > distributions are listed in our download section:
>
>
> > href="http://maven.apache.org/download.html" target=_blank
> > >http://maven.apache.org/download.html
>
> A major goal of Maven 3.0 is
> > to be compatible, to the extent possible, with existing plugins and
> projects
> > designed for Maven 2.x. Users interested in testing this beta release
> should
> > have a glance at the compatibility notes for known differences between
> Maven 3.0
> > and Maven 2.x:
>
>
> > href="http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html"
> > target=_blank
> > >http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
> If
> > you encounter unexpected problems while using Maven 3.0-beta-1, please
> feel free
> > to contact us via the Maven developer list:
>
>
> > href="http://maven.apache.org/mail-lists.html" target=_blank
> > >http://maven.apache.org/mail-lists.html
>
> Release Notes - Maven 2
> > & 3 - Version 3.0-beta-1
>
> ** Bug
> * [MNG-1751] -
> > merging metadata doesn't fail when timestamp is in the future
> *
> > [MNG-2103] - Inheritance of <plugin> overrides that of
> > <execution>
> * [MNG-2222] - dependency to dependency
> > without source code fails
> * [MNG-2276] - profile activation by
> > property doesn't work with properties defined in settings.
> *
> > [MNG-2994] - Snapshot repositories are not checked when using ranges
>
> > * [MNG-3092] - Version ranges with non-snapshot bounds can contain
> > snapshot versions
> * [MNG-3133] -
> > DefaultModelInheritence::appendPath assumes it is operating on
> > interpolated/literal paths
> * [MNG-3470] - Build does not fail
> > on corrupted POM even with checksumPolicy=fail
> * [MNG-3477] -
> > Authentication failures on dependency download aren't reported
>
> > * [MNG-3529] - mvn -Da=" " throws an excepltion
> * [MNG-3616] -
> > Null Pointer Exception when mirrorOf missing from mirror in
> > settings.xml
> * [MNG-3700] - ModelUtils.clone doesn't clone
> > plugin entries where inherited == false
> * [MNG-4022] -
> > Incorrect merge behavior using profile driven plugin configuration
>
> > * [MNG-4326] - Maven should not check snapshot repositories for
> > dependencies in the reactor
> * [MNG-4418] - Dependency
> > resolution appears to misbehave if a remote repository uses the id
> > "local"
> * [MNG-4453] - [regression] Plugin versions defined in
> > a lifecycle mapping are not respected
> * [MNG-4555] - mvn
> > archetype:generate -o (offline) still results in a "checking updates from
> > central"
> * [MNG-4580] - Plugin dependencies for module ignored
> > when building from aggregator project using direct plugin invocation
>
> > * [MNG-4586] - Plugin prefix can't be resolved from plugin management
> if
> > management entry is missing plugin version
> * [MNG-4590] -
> > [regression] System properties are no longer interpolated in imported
> > POMs
> * [MNG-4600] - [regression] Optional flag from dependency
> > management applied to dependencies
> * [MNG-4618] -
> > maven-javadoc-plugin aggregate-jar fails with maven3 and multiple
> > modules
> * [MNG-4625] - Interpolation of settings.xml fails if
> > an expression's value contains XML markup
> * [MNG-4629] -
> > [regression] POM validation fails upon non-existing system-scope
> > dependency
> * [MNG-4632] - Class loading is not
> > thread-safe
>
> ** Improvement
> * [MNG-1701] - Validate that
> > a plugin is not configured twice in the pom
> * [MNG-2187] -
> > Improve error message when the pom is encoded in the wrong charset
>
> > * [MNG-2741] - [regression] Meaningless error message: "Error
> > transferring file"
> * [MNG-3004] - Allow build lifecycle to
> > execute projects in parallel
> * [MNG-3779] - Improve error
> > message when trying to execute mojo with no pom.xml
> *
> > [MNG-4162] - Removal of all reporting logic from the core of Maven
>
> > * [MNG-4194] - API to safely release of plugin realms
> *
> > [MNG-4591] - Enhance the download rate output to include downloaded file
> > name
> * [MNG-4610] - Bump maven-release-plugin to v2.0 in super
> > POM
> * [MNG-4619] - Issue warning in case parent.relativePath
> > points at POM with different groupId/artifactId
> * [MNG-4623] -
> > model parsing errors can be less helpful in Maven 3
> *
> > [MNG-4628] - ReactorArtifactRepository is not setup soon enough for
> > AbstractMavenLifecycleParticipant#afterProjectsRead
> *
> > [MNG-4634] - Allow custom lifecycles
>
> ** Task
> *
> > [MNG-3917] - Complete the POM construction tests which will be the
> validation
> > for the specification
>
>
> Enjoy,
>
>
> -The Maven
> > team
>
>
> ---------------------------------------------------------------------
> To
> > unsubscribe, e-mail:
> > href="mailto:dev-unsubscribe@maven.apache.org">
> dev-unsubscribe@maven.apache.org
> For
> > additional commands, e-mail:
> > href="mailto:dev-help@maven.apache.org">dev-help@maven.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Re : [ANN] Apache Maven 3.0-beta-1 Released
Posted by Benjamin Bentmann <be...@udo.edu>.
Julien HENRY wrote:
> [ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates (default-cli) on project myproject: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed. NullPointerException -> [Help 1]
Yes, already reported as http://jira.codehaus.org/browse/MVERSIONS-105.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re : [ANN] Apache Maven 3.0-beta-1 Released
Posted by Julien HENRY <he...@yahoo.fr>.
Hi,
I have the following error using Maven 3.0-beta-1. Before trying to reproduce on a smaller project, could you please have a look and tell me if this is a known issue. The only similar issue I have found is: MENFORCER-55
$ mvn versions:display-plugin-updates -X
[...]
[DEBUG] final aggregate version map
org.apache.maven.plugins:maven-clean-plugin:2.3
org.apache.maven.plugins:maven-surefire-plugin:2.4.3
org.codehaus.mojo:exec-maven-plugin:1.1
org.apache.maven.plugins:maven-ear-plugin:2.3.2
org.apache.maven.plugins:maven-war-plugin:2.1-beta-1
org.apache.maven.plugins:maven-jar-plugin:2.3
org.apache.maven.plugins:maven-source-plugin:2.1.1
org.apache.maven.plugins:maven-dependency-plugin:2.1
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
org.apache.maven.plugins:maven-compiler-plugin:2.0.2
org.apache.maven.plugins:maven-install-plugin:2.3
org.apache.maven.plugins:maven-site-plugin:2.0.1
org.apache.maven.plugins:maven-release-plugin:2.0-beta-8
[DEBUG] after adding local pluginManagement
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.250s
[INFO] Finished at: Mon Apr 26 14:18:46 CEST 2010
[INFO] Final Memory: 6M/19M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates (default-cli) on project myproject: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed. NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates (default-cli) on project myproject: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:149)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.PluginExecutionException: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:1.1:display-plugin-updates failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:114)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133)
... 19 more
Caused by: java.lang.NullPointerException
at org.codehaus.plexus.util.ReflectionUtils.getValueIncludingSuperclasses(ReflectionUtils.java:179)
at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getBoundPlugins(DisplayPluginUpdatesMojo.java:660)
at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getLifecyclePlugins(DisplayPluginUpdatesMojo.java:619)
at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.getProjectPlugins(DisplayPluginUpdatesMojo.java:1096)
at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.execute(DisplayPluginUpdatesMojo.java:277)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
... 20 more
It seems to works fine with Maven 2.2.1 (in fact it is taking a very long time to check update of each plugin so the execution with Maven 2 is still not completed, but with Maven 3 the NPE occurs after few seconds only).
Regards,
Julien
----- Message d'origine ----
> De : Benjamin Bentmann <be...@apache.org>
> À : announce@maven.apache.org; users@maven.apache.org
> Cc : Maven Developers List <de...@maven.apache.org>
> Envoyé le : Ven 23 avril 2010, 15 h 05 min 57 s
> Objet : [ANN] Apache Maven 3.0-beta-1 Released
>
> The Maven team is pleased to announce the release of Apache Maven
> 3.0-beta-1.
Maven is a project comprehension and build tool, designed to
> simplify the process of maintaining a healthy development lifecycle for your
> project. You can read more here:
> href="http://maven.apache.org/" target=_blank
> >http://maven.apache.org/
Downloads of source and binary
> distributions are listed in our download section:
> href="http://maven.apache.org/download.html" target=_blank
> >http://maven.apache.org/download.html
A major goal of Maven 3.0 is
> to be compatible, to the extent possible, with existing plugins and projects
> designed for Maven 2.x. Users interested in testing this beta release should
> have a glance at the compatibility notes for known differences between Maven 3.0
> and Maven 2.x:
> href="http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html"
> target=_blank
> >http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
If
> you encounter unexpected problems while using Maven 3.0-beta-1, please feel free
> to contact us via the Maven developer list:
> href="http://maven.apache.org/mail-lists.html" target=_blank
> >http://maven.apache.org/mail-lists.html
Release Notes - Maven 2
> & 3 - Version 3.0-beta-1
** Bug
* [MNG-1751] -
> merging metadata doesn't fail when timestamp is in the future
*
> [MNG-2103] - Inheritance of <plugin> overrides that of
> <execution>
* [MNG-2222] - dependency to dependency
> without source code fails
* [MNG-2276] - profile activation by
> property doesn't work with properties defined in settings.
*
> [MNG-2994] - Snapshot repositories are not checked when using ranges
> * [MNG-3092] - Version ranges with non-snapshot bounds can contain
> snapshot versions
* [MNG-3133] -
> DefaultModelInheritence::appendPath assumes it is operating on
> interpolated/literal paths
* [MNG-3470] - Build does not fail
> on corrupted POM even with checksumPolicy=fail
* [MNG-3477] -
> Authentication failures on dependency download aren't reported
> * [MNG-3529] - mvn -Da=" " throws an excepltion
* [MNG-3616] -
> Null Pointer Exception when mirrorOf missing from mirror in
> settings.xml
* [MNG-3700] - ModelUtils.clone doesn't clone
> plugin entries where inherited == false
* [MNG-4022] -
> Incorrect merge behavior using profile driven plugin configuration
> * [MNG-4326] - Maven should not check snapshot repositories for
> dependencies in the reactor
* [MNG-4418] - Dependency
> resolution appears to misbehave if a remote repository uses the id
> "local"
* [MNG-4453] - [regression] Plugin versions defined in
> a lifecycle mapping are not respected
* [MNG-4555] - mvn
> archetype:generate -o (offline) still results in a "checking updates from
> central"
* [MNG-4580] - Plugin dependencies for module ignored
> when building from aggregator project using direct plugin invocation
> * [MNG-4586] - Plugin prefix can't be resolved from plugin management if
> management entry is missing plugin version
* [MNG-4590] -
> [regression] System properties are no longer interpolated in imported
> POMs
* [MNG-4600] - [regression] Optional flag from dependency
> management applied to dependencies
* [MNG-4618] -
> maven-javadoc-plugin aggregate-jar fails with maven3 and multiple
> modules
* [MNG-4625] - Interpolation of settings.xml fails if
> an expression's value contains XML markup
* [MNG-4629] -
> [regression] POM validation fails upon non-existing system-scope
> dependency
* [MNG-4632] - Class loading is not
> thread-safe
** Improvement
* [MNG-1701] - Validate that
> a plugin is not configured twice in the pom
* [MNG-2187] -
> Improve error message when the pom is encoded in the wrong charset
> * [MNG-2741] - [regression] Meaningless error message: "Error
> transferring file"
* [MNG-3004] - Allow build lifecycle to
> execute projects in parallel
* [MNG-3779] - Improve error
> message when trying to execute mojo with no pom.xml
*
> [MNG-4162] - Removal of all reporting logic from the core of Maven
> * [MNG-4194] - API to safely release of plugin realms
*
> [MNG-4591] - Enhance the download rate output to include downloaded file
> name
* [MNG-4610] - Bump maven-release-plugin to v2.0 in super
> POM
* [MNG-4619] - Issue warning in case parent.relativePath
> points at POM with different groupId/artifactId
* [MNG-4623] -
> model parsing errors can be less helpful in Maven 3
*
> [MNG-4628] - ReactorArtifactRepository is not setup soon enough for
> AbstractMavenLifecycleParticipant#afterProjectsRead
*
> [MNG-4634] - Allow custom lifecycles
** Task
*
> [MNG-3917] - Complete the POM construction tests which will be the validation
> for the specification
Enjoy,
-The Maven
> team
---------------------------------------------------------------------
To
> unsubscribe, e-mail:
> href="mailto:dev-unsubscribe@maven.apache.org">dev-unsubscribe@maven.apache.org
For
> additional commands, e-mail:
> href="mailto:dev-help@maven.apache.org">dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Arnaud Héritier <ah...@gmail.com>.
Yes i began to study this issue I discovered two days ago
The issue was introduced in 2.4 and is in all 2.4.x releases.
I think it is enough critical to try to fix it quickly (And we can loose
many time before finding it and applying the workaround - myself 30 min)
I'm studying plexus-interpolator code to see how to do that (PLXCOMP-150)
and I'll try to submit a patch (I'm not commiter on plexus)
I already prepared the IT for the resources plugin.
Arnaud
On Thu, Apr 29, 2010 at 9:27 AM, Frederic Camblor <fc...@gmail.com>wrote:
> For you information,
>
> Because of http://jira.codehaus.org/browse/MRESOURCES-104, there will be
> regressions in 3.0-beta1 on filtering of ressources files containing a "@"
> inside it (like urls or datasources) if you relies on the super pom
> definition of the maven-resources-plugin (aligned from 2.3 to 2.4.2 between
> mvn 2.2.1 and 3.0-beta1)
>
> Frederic
>
> On Thu, Apr 29, 2010 at 1:53 AM, Hervé BOUTEMY <herve.boutemy@free.fr
> >wrote:
>
> > FYI, this has just been fixed (thanks Kristian).
> >
> > The fix is in Maven 3 trunk, then won't be available to general public
> > before
> > Maven 3.0-beta-2 release: no ETA ;)
> >
> > I just compiled Maven trunk for myself then maven-site-plugin 3.0 branch,
> > and
> > everything is now ok.
> >
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 24 avril 2010, Kristian Rosenvold a écrit :
> > > This will be fixed "real soon", the site plugin needs a minor update.
> > >
> > > On Fri, Apr 23, 2010 at 11:06 PM, Kathryn Huxtable <
> > >
> > > kathryn@kathrynhuxtable.org> wrote:
> > > > Any reason why "mvn clean package" on the checked out source would
> > yield:
> > > >
> > > > [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @
> > > > maven-site-plugin ---
> > > > [INFO] Compiling 23 source files to
> > > >
> > /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> > > >/target/classes [INFO]
> > > > ------------------------------------------------------------- [ERROR]
> > > > COMPILATION ERROR :
> > > > [INFO] -------------------------------------------------------------
> > > > [ERROR]
> > > >
> > /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> > >
> >
> >/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja
> > > >va:[209,41] cannot find symbol
> > > > symbol : method
> > > >
> > calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apach
> > > >e.maven.execution.MavenSession) location: interface
> > > > org.apache.maven.lifecycle.LifecycleExecutor
> > > >
> > > > [ERROR]
> > > >
> > /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> > >
> >
> >/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja
> > > >va:[213,45] cannot find symbol
> > > > symbol : method
> > > >
> > executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.
> > > >maven.execution.MavenSession) location: interface
> > > > org.apache.maven.lifecycle.LifecycleExecutor
> > > >
> > > > [INFO] 2 errors
> > > > [INFO] -------------------------------------------------------------
> > > > [INFO]
> > > >
> > ------------------------------------------------------------------------
> > > > [INFO] BUILD FAILURE
> > > >
> > > > -K
> > > >
> > > > On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote:
> > > > > Great! I'll try it out and let you know.
> > > > >
> > > > > You're probably already doing integration testing, so you probably
> > > >
> > > > already know anything I'll report. I'l check the JIRA before I
> > > > complain...
> > > >
> > > > > Thanks!
> > > > >
> > > > > -K
> > > > >
> > > > > On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote:
> > > > >> this one isn't done by Jason, but this won't give you an ETA
> neither
> > > > >> ;)
> > > > >>
> > > > >> maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
> > > > >> you can install it for yourself and see if it works
> > > > >>
> > > > >> we will probably put the release out in the next weeks
> > > > >>
> > > > >> Regards,
> > > > >>
> > > > >> Hervé
> > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
> > > >in
> > > >
> > > > >> Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
> > > > >>> I know Jason says he won't give ETAs, but is there any ETA on the
> > > > >>> site reporting? I make a lot of use of it, and I doubt I'm alone.
> > > > >>>
> > > > >>> My personal preference is to find some way to integrate the
> docbkx
> > > >
> > > > plugin
> > > >
> > > > >>> with the site framework. I've got some code that does this for
> > Maven
> > > > >>> 2, and it works for Maven 3, but the reports aren't generated.
> > > > >>>
> > > > >>> -K
> > > > >>>
> > > > >>> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
> > > > >>>> The Maven team is pleased to announce the release of Apache
> Maven
> > > > >>>> 3.0-beta-1.
> > > > >>>>
> > > > >>>> Maven is a project comprehension and build tool, designed to
> > > > >>>> simplify
> > > >
> > > > the
> > > >
> > > > >>>> process of maintaining a healthy development lifecycle for your
> > > >
> > > > project.
> > > >
> > > > >>>> You can read more here:
> > > > >>>>
> > > > >>>> http://maven.apache.org/
> > > > >>>>
> > > > >>>> Downloads of source and binary distributions are listed in our
> > > >
> > > > download
> > > >
> > > > >>>> section:
> > > > >>>>
> > > > >>>> http://maven.apache.org/download.html
> > > > >>>>
> > > > >>>> A major goal of Maven 3.0 is to be compatible, to the extent
> > > > >>>> possible, with existing plugins and projects designed for Maven
> > 2.x.
> > > > >>>> Users interested in testing this beta release should have a
> glance
> > > > >>>> at the compatibility notes for known differences between Maven
> 3.0
> > > > >>>> and Maven 2.x:
> > > > >>>>
> > > > >>>> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
> > > > >>>>
> > > > >>>> If you encounter unexpected problems while using Maven
> 3.0-beta-1,
> > > >
> > > > please
> > > >
> > > > >>>> feel free to contact us via the Maven developer list:
> > > > >>>>
> > > > >>>> http://maven.apache.org/mail-lists.html
> > > > >>>>
> > > > >>>> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
> > > > >>>>
> > > > >>>> ** Bug
> > > > >>>> * [MNG-1751] - merging metadata doesn't fail when timestamp is
> in
> > > > >>>> the future * [MNG-2103] - Inheritance of <plugin> overrides that
> > of
> > > > >>>> <execution> * [MNG-2222] - dependency to dependency without
> source
> > > >
> > > > code
> > > >
> > > > >>>> fails * [MNG-2276] - profile activation by property doesn't work
> > > > >>>> with properties defined in settings. * [MNG-2994] - Snapshot
> > > > >>>> repositories
> > > >
> > > > are
> > > >
> > > > >>>> not checked when using ranges * [MNG-3092] - Version ranges with
> > > > >>>> non-snapshot bounds can contain snapshot versions * [MNG-3133] -
> > > > >>>> DefaultModelInheritence::appendPath assumes it is operating on
> > > > >>>> interpolated/literal paths * [MNG-3470] - Build does not fail on
> > > > >>>> corrupted POM even with checksumPolicy=fail * [MNG-3477] -
> > > >
> > > > Authentication
> > > >
> > > > >>>> failures on dependency download aren't reported * [MNG-3529] -
> mvn
> > > >
> > > > -Da="
> > > >
> > > > >>>> " throws an excepltion
> > > > >>>> * [MNG-3616] - Null Pointer Exception when mirrorOf missing
> from
> > > > >>>> mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't
> > clone
> > > > >>>> plugin entries where inherited == false * [MNG-4022] - Incorrect
> > > > >>>> merge behavior using profile driven plugin configuration *
> > > > >>>> [MNG-4326] -
> > > >
> > > > Maven
> > > >
> > > > >>>> should not check snapshot repositories for dependencies in the
> > > > >>>> reactor
> > > >
> > > > *
> > > >
> > > > >>>> [MNG-4418] - Dependency resolution appears to misbehave if a
> > remote
> > > > >>>> repository uses the id "local" * [MNG-4453] - [regression]
> Plugin
> > > > >>>> versions defined in a lifecycle mapping are not respected *
> > > > >>>> [MNG-4555]
> > > >
> > > > -
> > > >
> > > > >>>> mvn archetype:generate -o (offline) still results in a "checking
> > > >
> > > > updates
> > > >
> > > > >>>> from central" * [MNG-4580] - Plugin dependencies for module
> > ignored
> > > >
> > > > when
> > > >
> > > > >>>> building from aggregator project using direct plugin invocation
> *
> > > > >>>> [MNG-4586] - Plugin prefix can't be resolved from plugin
> > management
> > > > >>>> if management entry is missing plugin version * [MNG-4590] -
> > > > >>>> [regression] System properties are no longer interpolated in
> > > > >>>> imported POMs * [MNG-4600] - [regression] Optional flag from
> > > > >>>> dependency management applied to dependencies * [MNG-4618] -
> > > > >>>> maven-javadoc-plugin
> > > >
> > > > aggregate-jar
> > > >
> > > > >>>> fails with maven3 and multiple modules * [MNG-4625] -
> > Interpolation
> > > > >>>> of settings.xml fails if an expression's value contains XML
> markup
> > *
> > > > >>>> [MNG-4629] - [regression] POM validation fails upon non-existing
> > > > >>>> system-scope dependency * [MNG-4632] - Class loading is not
> > > >
> > > > thread-safe
> > > >
> > > > >>>> ** Improvement
> > > > >>>> * [MNG-1701] - Validate that a plugin is not configured twice
> in
> > > > >>>> the pom * [MNG-2187] - Improve error message when the pom is
> > encoded
> > > > >>>> in
> > > >
> > > > the
> > > >
> > > > >>>> wrong charset * [MNG-2741] - [regression] Meaningless error
> > message:
> > > > >>>> "Error transferring file" * [MNG-3004] - Allow build lifecycle
> to
> > > >
> > > > execute
> > > >
> > > > >>>> projects in parallel * [MNG-3779] - Improve error message when
> > > > >>>> trying
> > > >
> > > > to
> > > >
> > > > >>>> execute mojo with no pom.xml * [MNG-4162] - Removal of all
> > reporting
> > > > >>>> logic from the core of Maven * [MNG-4194] - API to safely
> release
> > of
> > > > >>>> plugin realms
> > > > >>>> * [MNG-4591] - Enhance the download rate output to include
> > > > >>>> downloaded file name * [MNG-4610] - Bump maven-release-plugin to
> > > > >>>> v2.0 in super
> > > >
> > > > POM *
> > > >
> > > > >>>> [MNG-4619] - Issue warning in case parent.relativePath points at
> > POM
> > > >
> > > > with
> > > >
> > > > >>>> different groupId/artifactId * [MNG-4623] - model parsing errors
> > can
> > > >
> > > > be
> > > >
> > > > >>>> less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository
> > is
> > > >
> > > > not
> > > >
> > > > >>>> setup soon enough for
> > > >
> > > > AbstractMavenLifecycleParticipant#afterProjectsRead
> > > >
> > > > >>>> * [MNG-4634] - Allow custom lifecycles
> > > > >>>>
> > > > >>>> ** Task
> > > > >>>> * [MNG-3917] - Complete the POM construction tests which will
> be
> > > > >>>> the validation for the specification
> > > > >>>>
> > > > >>>>
> > > > >>>> Enjoy,
> > > > >>>>
> > > > >>>>
> > > > >>>> -The Maven team
> > > > >>>
> > > > >>>
> > ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > >>> For additional commands, e-mail: users-help@maven.apache.org
> > > > >>
> > > > >>
> > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > >> For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Frederic Camblor <fc...@gmail.com>.
For you information,
Because of http://jira.codehaus.org/browse/MRESOURCES-104, there will be
regressions in 3.0-beta1 on filtering of ressources files containing a "@"
inside it (like urls or datasources) if you relies on the super pom
definition of the maven-resources-plugin (aligned from 2.3 to 2.4.2 between
mvn 2.2.1 and 3.0-beta1)
Frederic
On Thu, Apr 29, 2010 at 1:53 AM, Hervé BOUTEMY <he...@free.fr>wrote:
> FYI, this has just been fixed (thanks Kristian).
>
> The fix is in Maven 3 trunk, then won't be available to general public
> before
> Maven 3.0-beta-2 release: no ETA ;)
>
> I just compiled Maven trunk for myself then maven-site-plugin 3.0 branch,
> and
> everything is now ok.
>
>
> Regards,
>
> Hervé
>
> Le samedi 24 avril 2010, Kristian Rosenvold a écrit :
> > This will be fixed "real soon", the site plugin needs a minor update.
> >
> > On Fri, Apr 23, 2010 at 11:06 PM, Kathryn Huxtable <
> >
> > kathryn@kathrynhuxtable.org> wrote:
> > > Any reason why "mvn clean package" on the checked out source would
> yield:
> > >
> > > [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @
> > > maven-site-plugin ---
> > > [INFO] Compiling 23 source files to
> > >
> /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> > >/target/classes [INFO]
> > > ------------------------------------------------------------- [ERROR]
> > > COMPILATION ERROR :
> > > [INFO] -------------------------------------------------------------
> > > [ERROR]
> > >
> /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> >
> >/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja
> > >va:[209,41] cannot find symbol
> > > symbol : method
> > >
> calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apach
> > >e.maven.execution.MavenSession) location: interface
> > > org.apache.maven.lifecycle.LifecycleExecutor
> > >
> > > [ERROR]
> > >
> /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> >
> >/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja
> > >va:[213,45] cannot find symbol
> > > symbol : method
> > >
> executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.
> > >maven.execution.MavenSession) location: interface
> > > org.apache.maven.lifecycle.LifecycleExecutor
> > >
> > > [INFO] 2 errors
> > > [INFO] -------------------------------------------------------------
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] BUILD FAILURE
> > >
> > > -K
> > >
> > > On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote:
> > > > Great! I'll try it out and let you know.
> > > >
> > > > You're probably already doing integration testing, so you probably
> > >
> > > already know anything I'll report. I'l check the JIRA before I
> > > complain...
> > >
> > > > Thanks!
> > > >
> > > > -K
> > > >
> > > > On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote:
> > > >> this one isn't done by Jason, but this won't give you an ETA neither
> > > >> ;)
> > > >>
> > > >> maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
> > > >> you can install it for yourself and see if it works
> > > >>
> > > >> we will probably put the release out in the next weeks
> > > >>
> > > >> Regards,
> > > >>
> > > >> Hervé
> > >
> > >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
> > >in
> > >
> > > >> Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
> > > >>> I know Jason says he won't give ETAs, but is there any ETA on the
> > > >>> site reporting? I make a lot of use of it, and I doubt I'm alone.
> > > >>>
> > > >>> My personal preference is to find some way to integrate the docbkx
> > >
> > > plugin
> > >
> > > >>> with the site framework. I've got some code that does this for
> Maven
> > > >>> 2, and it works for Maven 3, but the reports aren't generated.
> > > >>>
> > > >>> -K
> > > >>>
> > > >>> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
> > > >>>> The Maven team is pleased to announce the release of Apache Maven
> > > >>>> 3.0-beta-1.
> > > >>>>
> > > >>>> Maven is a project comprehension and build tool, designed to
> > > >>>> simplify
> > >
> > > the
> > >
> > > >>>> process of maintaining a healthy development lifecycle for your
> > >
> > > project.
> > >
> > > >>>> You can read more here:
> > > >>>>
> > > >>>> http://maven.apache.org/
> > > >>>>
> > > >>>> Downloads of source and binary distributions are listed in our
> > >
> > > download
> > >
> > > >>>> section:
> > > >>>>
> > > >>>> http://maven.apache.org/download.html
> > > >>>>
> > > >>>> A major goal of Maven 3.0 is to be compatible, to the extent
> > > >>>> possible, with existing plugins and projects designed for Maven
> 2.x.
> > > >>>> Users interested in testing this beta release should have a glance
> > > >>>> at the compatibility notes for known differences between Maven 3.0
> > > >>>> and Maven 2.x:
> > > >>>>
> > > >>>> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
> > > >>>>
> > > >>>> If you encounter unexpected problems while using Maven 3.0-beta-1,
> > >
> > > please
> > >
> > > >>>> feel free to contact us via the Maven developer list:
> > > >>>>
> > > >>>> http://maven.apache.org/mail-lists.html
> > > >>>>
> > > >>>> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
> > > >>>>
> > > >>>> ** Bug
> > > >>>> * [MNG-1751] - merging metadata doesn't fail when timestamp is in
> > > >>>> the future * [MNG-2103] - Inheritance of <plugin> overrides that
> of
> > > >>>> <execution> * [MNG-2222] - dependency to dependency without source
> > >
> > > code
> > >
> > > >>>> fails * [MNG-2276] - profile activation by property doesn't work
> > > >>>> with properties defined in settings. * [MNG-2994] - Snapshot
> > > >>>> repositories
> > >
> > > are
> > >
> > > >>>> not checked when using ranges * [MNG-3092] - Version ranges with
> > > >>>> non-snapshot bounds can contain snapshot versions * [MNG-3133] -
> > > >>>> DefaultModelInheritence::appendPath assumes it is operating on
> > > >>>> interpolated/literal paths * [MNG-3470] - Build does not fail on
> > > >>>> corrupted POM even with checksumPolicy=fail * [MNG-3477] -
> > >
> > > Authentication
> > >
> > > >>>> failures on dependency download aren't reported * [MNG-3529] - mvn
> > >
> > > -Da="
> > >
> > > >>>> " throws an excepltion
> > > >>>> * [MNG-3616] - Null Pointer Exception when mirrorOf missing from
> > > >>>> mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't
> clone
> > > >>>> plugin entries where inherited == false * [MNG-4022] - Incorrect
> > > >>>> merge behavior using profile driven plugin configuration *
> > > >>>> [MNG-4326] -
> > >
> > > Maven
> > >
> > > >>>> should not check snapshot repositories for dependencies in the
> > > >>>> reactor
> > >
> > > *
> > >
> > > >>>> [MNG-4418] - Dependency resolution appears to misbehave if a
> remote
> > > >>>> repository uses the id "local" * [MNG-4453] - [regression] Plugin
> > > >>>> versions defined in a lifecycle mapping are not respected *
> > > >>>> [MNG-4555]
> > >
> > > -
> > >
> > > >>>> mvn archetype:generate -o (offline) still results in a "checking
> > >
> > > updates
> > >
> > > >>>> from central" * [MNG-4580] - Plugin dependencies for module
> ignored
> > >
> > > when
> > >
> > > >>>> building from aggregator project using direct plugin invocation *
> > > >>>> [MNG-4586] - Plugin prefix can't be resolved from plugin
> management
> > > >>>> if management entry is missing plugin version * [MNG-4590] -
> > > >>>> [regression] System properties are no longer interpolated in
> > > >>>> imported POMs * [MNG-4600] - [regression] Optional flag from
> > > >>>> dependency management applied to dependencies * [MNG-4618] -
> > > >>>> maven-javadoc-plugin
> > >
> > > aggregate-jar
> > >
> > > >>>> fails with maven3 and multiple modules * [MNG-4625] -
> Interpolation
> > > >>>> of settings.xml fails if an expression's value contains XML markup
> *
> > > >>>> [MNG-4629] - [regression] POM validation fails upon non-existing
> > > >>>> system-scope dependency * [MNG-4632] - Class loading is not
> > >
> > > thread-safe
> > >
> > > >>>> ** Improvement
> > > >>>> * [MNG-1701] - Validate that a plugin is not configured twice in
> > > >>>> the pom * [MNG-2187] - Improve error message when the pom is
> encoded
> > > >>>> in
> > >
> > > the
> > >
> > > >>>> wrong charset * [MNG-2741] - [regression] Meaningless error
> message:
> > > >>>> "Error transferring file" * [MNG-3004] - Allow build lifecycle to
> > >
> > > execute
> > >
> > > >>>> projects in parallel * [MNG-3779] - Improve error message when
> > > >>>> trying
> > >
> > > to
> > >
> > > >>>> execute mojo with no pom.xml * [MNG-4162] - Removal of all
> reporting
> > > >>>> logic from the core of Maven * [MNG-4194] - API to safely release
> of
> > > >>>> plugin realms
> > > >>>> * [MNG-4591] - Enhance the download rate output to include
> > > >>>> downloaded file name * [MNG-4610] - Bump maven-release-plugin to
> > > >>>> v2.0 in super
> > >
> > > POM *
> > >
> > > >>>> [MNG-4619] - Issue warning in case parent.relativePath points at
> POM
> > >
> > > with
> > >
> > > >>>> different groupId/artifactId * [MNG-4623] - model parsing errors
> can
> > >
> > > be
> > >
> > > >>>> less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository
> is
> > >
> > > not
> > >
> > > >>>> setup soon enough for
> > >
> > > AbstractMavenLifecycleParticipant#afterProjectsRead
> > >
> > > >>>> * [MNG-4634] - Allow custom lifecycles
> > > >>>>
> > > >>>> ** Task
> > > >>>> * [MNG-3917] - Complete the POM construction tests which will be
> > > >>>> the validation for the specification
> > > >>>>
> > > >>>>
> > > >>>> Enjoy,
> > > >>>>
> > > >>>>
> > > >>>> -The Maven team
> > > >>>
> > > >>>
> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > >>> For additional commands, e-mail: users-help@maven.apache.org
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Hervé BOUTEMY <he...@free.fr>.
FYI, this has just been fixed (thanks Kristian).
The fix is in Maven 3 trunk, then won't be available to general public before
Maven 3.0-beta-2 release: no ETA ;)
I just compiled Maven trunk for myself then maven-site-plugin 3.0 branch, and
everything is now ok.
Regards,
Hervé
Le samedi 24 avril 2010, Kristian Rosenvold a écrit :
> This will be fixed "real soon", the site plugin needs a minor update.
>
> On Fri, Apr 23, 2010 at 11:06 PM, Kathryn Huxtable <
>
> kathryn@kathrynhuxtable.org> wrote:
> > Any reason why "mvn clean package" on the checked out source would yield:
> >
> > [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @
> > maven-site-plugin ---
> > [INFO] Compiling 23 source files to
> > /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> >/target/classes [INFO]
> > ------------------------------------------------------------- [ERROR]
> > COMPILATION ERROR :
> > [INFO] -------------------------------------------------------------
> > [ERROR]
> > /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> >/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja
> >va:[209,41] cannot find symbol
> > symbol : method
> > calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apach
> >e.maven.execution.MavenSession) location: interface
> > org.apache.maven.lifecycle.LifecycleExecutor
> >
> > [ERROR]
> > /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT
> >/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja
> >va:[213,45] cannot find symbol
> > symbol : method
> > executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.
> >maven.execution.MavenSession) location: interface
> > org.apache.maven.lifecycle.LifecycleExecutor
> >
> > [INFO] 2 errors
> > [INFO] -------------------------------------------------------------
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> >
> > -K
> >
> > On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote:
> > > Great! I'll try it out and let you know.
> > >
> > > You're probably already doing integration testing, so you probably
> >
> > already know anything I'll report. I'l check the JIRA before I
> > complain...
> >
> > > Thanks!
> > >
> > > -K
> > >
> > > On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote:
> > >> this one isn't done by Jason, but this won't give you an ETA neither
> > >> ;)
> > >>
> > >> maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
> > >> you can install it for yourself and see if it works
> > >>
> > >> we will probably put the release out in the next weeks
> > >>
> > >> Regards,
> > >>
> > >> Hervé
> >
> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
> >in
> >
> > >> Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
> > >>> I know Jason says he won't give ETAs, but is there any ETA on the
> > >>> site reporting? I make a lot of use of it, and I doubt I'm alone.
> > >>>
> > >>> My personal preference is to find some way to integrate the docbkx
> >
> > plugin
> >
> > >>> with the site framework. I've got some code that does this for Maven
> > >>> 2, and it works for Maven 3, but the reports aren't generated.
> > >>>
> > >>> -K
> > >>>
> > >>> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
> > >>>> The Maven team is pleased to announce the release of Apache Maven
> > >>>> 3.0-beta-1.
> > >>>>
> > >>>> Maven is a project comprehension and build tool, designed to
> > >>>> simplify
> >
> > the
> >
> > >>>> process of maintaining a healthy development lifecycle for your
> >
> > project.
> >
> > >>>> You can read more here:
> > >>>>
> > >>>> http://maven.apache.org/
> > >>>>
> > >>>> Downloads of source and binary distributions are listed in our
> >
> > download
> >
> > >>>> section:
> > >>>>
> > >>>> http://maven.apache.org/download.html
> > >>>>
> > >>>> A major goal of Maven 3.0 is to be compatible, to the extent
> > >>>> possible, with existing plugins and projects designed for Maven 2.x.
> > >>>> Users interested in testing this beta release should have a glance
> > >>>> at the compatibility notes for known differences between Maven 3.0
> > >>>> and Maven 2.x:
> > >>>>
> > >>>> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
> > >>>>
> > >>>> If you encounter unexpected problems while using Maven 3.0-beta-1,
> >
> > please
> >
> > >>>> feel free to contact us via the Maven developer list:
> > >>>>
> > >>>> http://maven.apache.org/mail-lists.html
> > >>>>
> > >>>> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
> > >>>>
> > >>>> ** Bug
> > >>>> * [MNG-1751] - merging metadata doesn't fail when timestamp is in
> > >>>> the future * [MNG-2103] - Inheritance of <plugin> overrides that of
> > >>>> <execution> * [MNG-2222] - dependency to dependency without source
> >
> > code
> >
> > >>>> fails * [MNG-2276] - profile activation by property doesn't work
> > >>>> with properties defined in settings. * [MNG-2994] - Snapshot
> > >>>> repositories
> >
> > are
> >
> > >>>> not checked when using ranges * [MNG-3092] - Version ranges with
> > >>>> non-snapshot bounds can contain snapshot versions * [MNG-3133] -
> > >>>> DefaultModelInheritence::appendPath assumes it is operating on
> > >>>> interpolated/literal paths * [MNG-3470] - Build does not fail on
> > >>>> corrupted POM even with checksumPolicy=fail * [MNG-3477] -
> >
> > Authentication
> >
> > >>>> failures on dependency download aren't reported * [MNG-3529] - mvn
> >
> > -Da="
> >
> > >>>> " throws an excepltion
> > >>>> * [MNG-3616] - Null Pointer Exception when mirrorOf missing from
> > >>>> mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone
> > >>>> plugin entries where inherited == false * [MNG-4022] - Incorrect
> > >>>> merge behavior using profile driven plugin configuration *
> > >>>> [MNG-4326] -
> >
> > Maven
> >
> > >>>> should not check snapshot repositories for dependencies in the
> > >>>> reactor
> >
> > *
> >
> > >>>> [MNG-4418] - Dependency resolution appears to misbehave if a remote
> > >>>> repository uses the id "local" * [MNG-4453] - [regression] Plugin
> > >>>> versions defined in a lifecycle mapping are not respected *
> > >>>> [MNG-4555]
> >
> > -
> >
> > >>>> mvn archetype:generate -o (offline) still results in a "checking
> >
> > updates
> >
> > >>>> from central" * [MNG-4580] - Plugin dependencies for module ignored
> >
> > when
> >
> > >>>> building from aggregator project using direct plugin invocation *
> > >>>> [MNG-4586] - Plugin prefix can't be resolved from plugin management
> > >>>> if management entry is missing plugin version * [MNG-4590] -
> > >>>> [regression] System properties are no longer interpolated in
> > >>>> imported POMs * [MNG-4600] - [regression] Optional flag from
> > >>>> dependency management applied to dependencies * [MNG-4618] -
> > >>>> maven-javadoc-plugin
> >
> > aggregate-jar
> >
> > >>>> fails with maven3 and multiple modules * [MNG-4625] - Interpolation
> > >>>> of settings.xml fails if an expression's value contains XML markup *
> > >>>> [MNG-4629] - [regression] POM validation fails upon non-existing
> > >>>> system-scope dependency * [MNG-4632] - Class loading is not
> >
> > thread-safe
> >
> > >>>> ** Improvement
> > >>>> * [MNG-1701] - Validate that a plugin is not configured twice in
> > >>>> the pom * [MNG-2187] - Improve error message when the pom is encoded
> > >>>> in
> >
> > the
> >
> > >>>> wrong charset * [MNG-2741] - [regression] Meaningless error message:
> > >>>> "Error transferring file" * [MNG-3004] - Allow build lifecycle to
> >
> > execute
> >
> > >>>> projects in parallel * [MNG-3779] - Improve error message when
> > >>>> trying
> >
> > to
> >
> > >>>> execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting
> > >>>> logic from the core of Maven * [MNG-4194] - API to safely release of
> > >>>> plugin realms
> > >>>> * [MNG-4591] - Enhance the download rate output to include
> > >>>> downloaded file name * [MNG-4610] - Bump maven-release-plugin to
> > >>>> v2.0 in super
> >
> > POM *
> >
> > >>>> [MNG-4619] - Issue warning in case parent.relativePath points at POM
> >
> > with
> >
> > >>>> different groupId/artifactId * [MNG-4623] - model parsing errors can
> >
> > be
> >
> > >>>> less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is
> >
> > not
> >
> > >>>> setup soon enough for
> >
> > AbstractMavenLifecycleParticipant#afterProjectsRead
> >
> > >>>> * [MNG-4634] - Allow custom lifecycles
> > >>>>
> > >>>> ** Task
> > >>>> * [MNG-3917] - Complete the POM construction tests which will be
> > >>>> the validation for the specification
> > >>>>
> > >>>>
> > >>>> Enjoy,
> > >>>>
> > >>>>
> > >>>> -The Maven team
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >>> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Kristian Rosenvold <kr...@gmail.com>.
This will be fixed "real soon", the site plugin needs a minor update.
On Fri, Apr 23, 2010 at 11:06 PM, Kathryn Huxtable <
kathryn@kathrynhuxtable.org> wrote:
> Any reason why "mvn clean package" on the checked out source would yield:
>
> [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @
> maven-site-plugin ---
> [INFO] Compiling 23 source files to
> /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/target/classes
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR]
> /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java:[209,41]
> cannot find symbol
> symbol : method
> calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.maven.execution.MavenSession)
> location: interface org.apache.maven.lifecycle.LifecycleExecutor
>
> [ERROR]
> /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java:[213,45]
> cannot find symbol
> symbol : method
> executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.maven.execution.MavenSession)
> location: interface org.apache.maven.lifecycle.LifecycleExecutor
>
> [INFO] 2 errors
> [INFO] -------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
>
> -K
>
> On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote:
>
> > Great! I'll try it out and let you know.
> >
> > You're probably already doing integration testing, so you probably
> already know anything I'll report. I'l check the JIRA before I complain...
> >
> > Thanks!
> >
> > -K
> >
> > On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote:
> >
> >> this one isn't done by Jason, but this won't give you an ETA neither ;)
> >>
> >> maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
> >> you can install it for yourself and see if it works
> >>
> >> we will probably put the release out in the next weeks
> >>
> >> Regards,
> >>
> >> Hervé
> >>
> >>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
> >>
> >> Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
> >>> I know Jason says he won't give ETAs, but is there any ETA on the site
> >>> reporting? I make a lot of use of it, and I doubt I'm alone.
> >>>
> >>> My personal preference is to find some way to integrate the docbkx
> plugin
> >>> with the site framework. I've got some code that does this for Maven 2,
> >>> and it works for Maven 3, but the reports aren't generated.
> >>>
> >>> -K
> >>>
> >>> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
> >>>> The Maven team is pleased to announce the release of Apache Maven
> >>>> 3.0-beta-1.
> >>>>
> >>>> Maven is a project comprehension and build tool, designed to simplify
> the
> >>>> process of maintaining a healthy development lifecycle for your
> project.
> >>>> You can read more here:
> >>>>
> >>>> http://maven.apache.org/
> >>>>
> >>>> Downloads of source and binary distributions are listed in our
> download
> >>>> section:
> >>>>
> >>>> http://maven.apache.org/download.html
> >>>>
> >>>> A major goal of Maven 3.0 is to be compatible, to the extent possible,
> >>>> with existing plugins and projects designed for Maven 2.x. Users
> >>>> interested in testing this beta release should have a glance at the
> >>>> compatibility notes for known differences between Maven 3.0 and Maven
> >>>> 2.x:
> >>>>
> >>>> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
> >>>>
> >>>> If you encounter unexpected problems while using Maven 3.0-beta-1,
> please
> >>>> feel free to contact us via the Maven developer list:
> >>>>
> >>>> http://maven.apache.org/mail-lists.html
> >>>>
> >>>> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
> >>>>
> >>>> ** Bug
> >>>> * [MNG-1751] - merging metadata doesn't fail when timestamp is in the
> >>>> future * [MNG-2103] - Inheritance of <plugin> overrides that of
> >>>> <execution> * [MNG-2222] - dependency to dependency without source
> code
> >>>> fails * [MNG-2276] - profile activation by property doesn't work with
> >>>> properties defined in settings. * [MNG-2994] - Snapshot repositories
> are
> >>>> not checked when using ranges * [MNG-3092] - Version ranges with
> >>>> non-snapshot bounds can contain snapshot versions * [MNG-3133] -
> >>>> DefaultModelInheritence::appendPath assumes it is operating on
> >>>> interpolated/literal paths * [MNG-3470] - Build does not fail on
> >>>> corrupted POM even with checksumPolicy=fail * [MNG-3477] -
> Authentication
> >>>> failures on dependency download aren't reported * [MNG-3529] - mvn
> -Da="
> >>>> " throws an excepltion
> >>>> * [MNG-3616] - Null Pointer Exception when mirrorOf missing from
> >>>> mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone
> >>>> plugin entries where inherited == false * [MNG-4022] - Incorrect merge
> >>>> behavior using profile driven plugin configuration * [MNG-4326] -
> Maven
> >>>> should not check snapshot repositories for dependencies in the reactor
> *
> >>>> [MNG-4418] - Dependency resolution appears to misbehave if a remote
> >>>> repository uses the id "local" * [MNG-4453] - [regression] Plugin
> >>>> versions defined in a lifecycle mapping are not respected * [MNG-4555]
> -
> >>>> mvn archetype:generate -o (offline) still results in a "checking
> updates
> >>>> from central" * [MNG-4580] - Plugin dependencies for module ignored
> when
> >>>> building from aggregator project using direct plugin invocation *
> >>>> [MNG-4586] - Plugin prefix can't be resolved from plugin management if
> >>>> management entry is missing plugin version * [MNG-4590] - [regression]
> >>>> System properties are no longer interpolated in imported POMs *
> >>>> [MNG-4600] - [regression] Optional flag from dependency management
> >>>> applied to dependencies * [MNG-4618] - maven-javadoc-plugin
> aggregate-jar
> >>>> fails with maven3 and multiple modules * [MNG-4625] - Interpolation of
> >>>> settings.xml fails if an expression's value contains XML markup *
> >>>> [MNG-4629] - [regression] POM validation fails upon non-existing
> >>>> system-scope dependency * [MNG-4632] - Class loading is not
> thread-safe
> >>>>
> >>>> ** Improvement
> >>>> * [MNG-1701] - Validate that a plugin is not configured twice in the
> >>>> pom * [MNG-2187] - Improve error message when the pom is encoded in
> the
> >>>> wrong charset * [MNG-2741] - [regression] Meaningless error message:
> >>>> "Error transferring file" * [MNG-3004] - Allow build lifecycle to
> execute
> >>>> projects in parallel * [MNG-3779] - Improve error message when trying
> to
> >>>> execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting
> >>>> logic from the core of Maven * [MNG-4194] - API to safely release of
> >>>> plugin realms
> >>>> * [MNG-4591] - Enhance the download rate output to include downloaded
> >>>> file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super
> POM *
> >>>> [MNG-4619] - Issue warning in case parent.relativePath points at POM
> with
> >>>> different groupId/artifactId * [MNG-4623] - model parsing errors can
> be
> >>>> less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is
> not
> >>>> setup soon enough for
> AbstractMavenLifecycleParticipant#afterProjectsRead
> >>>> * [MNG-4634] - Allow custom lifecycles
> >>>>
> >>>> ** Task
> >>>> * [MNG-3917] - Complete the POM construction tests which will be the
> >>>> validation for the specification
> >>>>
> >>>>
> >>>> Enjoy,
> >>>>
> >>>>
> >>>> -The Maven team
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Kathryn Huxtable <ka...@kathrynhuxtable.org>.
Any reason why "mvn clean package" on the checked out source would yield:
[INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @ maven-site-plugin ---
[INFO] Compiling 23 source files to /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java:[209,41] cannot find symbol
symbol : method calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.maven.execution.MavenSession)
location: interface org.apache.maven.lifecycle.LifecycleExecutor
[ERROR] /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java:[213,45] cannot find symbol
symbol : method executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.maven.execution.MavenSession)
location: interface org.apache.maven.lifecycle.LifecycleExecutor
[INFO] 2 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
-K
On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote:
> Great! I'll try it out and let you know.
>
> You're probably already doing integration testing, so you probably already know anything I'll report. I'l check the JIRA before I complain...
>
> Thanks!
>
> -K
>
> On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote:
>
>> this one isn't done by Jason, but this won't give you an ETA neither ;)
>>
>> maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
>> you can install it for yourself and see if it works
>>
>> we will probably put the release out in the next weeks
>>
>> Regards,
>>
>> Hervé
>>
>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
>>
>> Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
>>> I know Jason says he won't give ETAs, but is there any ETA on the site
>>> reporting? I make a lot of use of it, and I doubt I'm alone.
>>>
>>> My personal preference is to find some way to integrate the docbkx plugin
>>> with the site framework. I've got some code that does this for Maven 2,
>>> and it works for Maven 3, but the reports aren't generated.
>>>
>>> -K
>>>
>>> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
>>>> The Maven team is pleased to announce the release of Apache Maven
>>>> 3.0-beta-1.
>>>>
>>>> Maven is a project comprehension and build tool, designed to simplify the
>>>> process of maintaining a healthy development lifecycle for your project.
>>>> You can read more here:
>>>>
>>>> http://maven.apache.org/
>>>>
>>>> Downloads of source and binary distributions are listed in our download
>>>> section:
>>>>
>>>> http://maven.apache.org/download.html
>>>>
>>>> A major goal of Maven 3.0 is to be compatible, to the extent possible,
>>>> with existing plugins and projects designed for Maven 2.x. Users
>>>> interested in testing this beta release should have a glance at the
>>>> compatibility notes for known differences between Maven 3.0 and Maven
>>>> 2.x:
>>>>
>>>> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>>>
>>>> If you encounter unexpected problems while using Maven 3.0-beta-1, please
>>>> feel free to contact us via the Maven developer list:
>>>>
>>>> http://maven.apache.org/mail-lists.html
>>>>
>>>> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
>>>>
>>>> ** Bug
>>>> * [MNG-1751] - merging metadata doesn't fail when timestamp is in the
>>>> future * [MNG-2103] - Inheritance of <plugin> overrides that of
>>>> <execution> * [MNG-2222] - dependency to dependency without source code
>>>> fails * [MNG-2276] - profile activation by property doesn't work with
>>>> properties defined in settings. * [MNG-2994] - Snapshot repositories are
>>>> not checked when using ranges * [MNG-3092] - Version ranges with
>>>> non-snapshot bounds can contain snapshot versions * [MNG-3133] -
>>>> DefaultModelInheritence::appendPath assumes it is operating on
>>>> interpolated/literal paths * [MNG-3470] - Build does not fail on
>>>> corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication
>>>> failures on dependency download aren't reported * [MNG-3529] - mvn -Da="
>>>> " throws an excepltion
>>>> * [MNG-3616] - Null Pointer Exception when mirrorOf missing from
>>>> mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone
>>>> plugin entries where inherited == false * [MNG-4022] - Incorrect merge
>>>> behavior using profile driven plugin configuration * [MNG-4326] - Maven
>>>> should not check snapshot repositories for dependencies in the reactor *
>>>> [MNG-4418] - Dependency resolution appears to misbehave if a remote
>>>> repository uses the id "local" * [MNG-4453] - [regression] Plugin
>>>> versions defined in a lifecycle mapping are not respected * [MNG-4555] -
>>>> mvn archetype:generate -o (offline) still results in a "checking updates
>>>> from central" * [MNG-4580] - Plugin dependencies for module ignored when
>>>> building from aggregator project using direct plugin invocation *
>>>> [MNG-4586] - Plugin prefix can't be resolved from plugin management if
>>>> management entry is missing plugin version * [MNG-4590] - [regression]
>>>> System properties are no longer interpolated in imported POMs *
>>>> [MNG-4600] - [regression] Optional flag from dependency management
>>>> applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar
>>>> fails with maven3 and multiple modules * [MNG-4625] - Interpolation of
>>>> settings.xml fails if an expression's value contains XML markup *
>>>> [MNG-4629] - [regression] POM validation fails upon non-existing
>>>> system-scope dependency * [MNG-4632] - Class loading is not thread-safe
>>>>
>>>> ** Improvement
>>>> * [MNG-1701] - Validate that a plugin is not configured twice in the
>>>> pom * [MNG-2187] - Improve error message when the pom is encoded in the
>>>> wrong charset * [MNG-2741] - [regression] Meaningless error message:
>>>> "Error transferring file" * [MNG-3004] - Allow build lifecycle to execute
>>>> projects in parallel * [MNG-3779] - Improve error message when trying to
>>>> execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting
>>>> logic from the core of Maven * [MNG-4194] - API to safely release of
>>>> plugin realms
>>>> * [MNG-4591] - Enhance the download rate output to include downloaded
>>>> file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM *
>>>> [MNG-4619] - Issue warning in case parent.relativePath points at POM with
>>>> different groupId/artifactId * [MNG-4623] - model parsing errors can be
>>>> less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not
>>>> setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead
>>>> * [MNG-4634] - Allow custom lifecycles
>>>>
>>>> ** Task
>>>> * [MNG-3917] - Complete the POM construction tests which will be the
>>>> validation for the specification
>>>>
>>>>
>>>> Enjoy,
>>>>
>>>>
>>>> -The Maven team
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Kathryn Huxtable <ka...@kathrynhuxtable.org>.
Great! I'll try it out and let you know.
You're probably already doing integration testing, so you probably already know anything I'll report. I'l check the JIRA before I complain...
Thanks!
-K
On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote:
> this one isn't done by Jason, but this won't give you an ETA neither ;)
>
> maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
> you can install it for yourself and see if it works
>
> we will probably put the release out in the next weeks
>
> Regards,
>
> Hervé
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
>
> Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
>> I know Jason says he won't give ETAs, but is there any ETA on the site
>> reporting? I make a lot of use of it, and I doubt I'm alone.
>>
>> My personal preference is to find some way to integrate the docbkx plugin
>> with the site framework. I've got some code that does this for Maven 2,
>> and it works for Maven 3, but the reports aren't generated.
>>
>> -K
>>
>> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
>>> The Maven team is pleased to announce the release of Apache Maven
>>> 3.0-beta-1.
>>>
>>> Maven is a project comprehension and build tool, designed to simplify the
>>> process of maintaining a healthy development lifecycle for your project.
>>> You can read more here:
>>>
>>> http://maven.apache.org/
>>>
>>> Downloads of source and binary distributions are listed in our download
>>> section:
>>>
>>> http://maven.apache.org/download.html
>>>
>>> A major goal of Maven 3.0 is to be compatible, to the extent possible,
>>> with existing plugins and projects designed for Maven 2.x. Users
>>> interested in testing this beta release should have a glance at the
>>> compatibility notes for known differences between Maven 3.0 and Maven
>>> 2.x:
>>>
>>> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>>>
>>> If you encounter unexpected problems while using Maven 3.0-beta-1, please
>>> feel free to contact us via the Maven developer list:
>>>
>>> http://maven.apache.org/mail-lists.html
>>>
>>> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
>>>
>>> ** Bug
>>> * [MNG-1751] - merging metadata doesn't fail when timestamp is in the
>>> future * [MNG-2103] - Inheritance of <plugin> overrides that of
>>> <execution> * [MNG-2222] - dependency to dependency without source code
>>> fails * [MNG-2276] - profile activation by property doesn't work with
>>> properties defined in settings. * [MNG-2994] - Snapshot repositories are
>>> not checked when using ranges * [MNG-3092] - Version ranges with
>>> non-snapshot bounds can contain snapshot versions * [MNG-3133] -
>>> DefaultModelInheritence::appendPath assumes it is operating on
>>> interpolated/literal paths * [MNG-3470] - Build does not fail on
>>> corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication
>>> failures on dependency download aren't reported * [MNG-3529] - mvn -Da="
>>> " throws an excepltion
>>> * [MNG-3616] - Null Pointer Exception when mirrorOf missing from
>>> mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone
>>> plugin entries where inherited == false * [MNG-4022] - Incorrect merge
>>> behavior using profile driven plugin configuration * [MNG-4326] - Maven
>>> should not check snapshot repositories for dependencies in the reactor *
>>> [MNG-4418] - Dependency resolution appears to misbehave if a remote
>>> repository uses the id "local" * [MNG-4453] - [regression] Plugin
>>> versions defined in a lifecycle mapping are not respected * [MNG-4555] -
>>> mvn archetype:generate -o (offline) still results in a "checking updates
>>> from central" * [MNG-4580] - Plugin dependencies for module ignored when
>>> building from aggregator project using direct plugin invocation *
>>> [MNG-4586] - Plugin prefix can't be resolved from plugin management if
>>> management entry is missing plugin version * [MNG-4590] - [regression]
>>> System properties are no longer interpolated in imported POMs *
>>> [MNG-4600] - [regression] Optional flag from dependency management
>>> applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar
>>> fails with maven3 and multiple modules * [MNG-4625] - Interpolation of
>>> settings.xml fails if an expression's value contains XML markup *
>>> [MNG-4629] - [regression] POM validation fails upon non-existing
>>> system-scope dependency * [MNG-4632] - Class loading is not thread-safe
>>>
>>> ** Improvement
>>> * [MNG-1701] - Validate that a plugin is not configured twice in the
>>> pom * [MNG-2187] - Improve error message when the pom is encoded in the
>>> wrong charset * [MNG-2741] - [regression] Meaningless error message:
>>> "Error transferring file" * [MNG-3004] - Allow build lifecycle to execute
>>> projects in parallel * [MNG-3779] - Improve error message when trying to
>>> execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting
>>> logic from the core of Maven * [MNG-4194] - API to safely release of
>>> plugin realms
>>> * [MNG-4591] - Enhance the download rate output to include downloaded
>>> file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM *
>>> [MNG-4619] - Issue warning in case parent.relativePath points at POM with
>>> different groupId/artifactId * [MNG-4623] - model parsing errors can be
>>> less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not
>>> setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead
>>> * [MNG-4634] - Allow custom lifecycles
>>>
>>> ** Task
>>> * [MNG-3917] - Complete the POM construction tests which will be the
>>> validation for the specification
>>>
>>>
>>> Enjoy,
>>>
>>>
>>> -The Maven team
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Hervé BOUTEMY <he...@free.fr>.
this one isn't done by Jason, but this won't give you an ETA neither ;)
maven-site-plugin 3.0-beta-1 shouldn't be far: see [1]
you can install it for yourself and see if it works
we will probably put the release out in the next weeks
Regards,
Hervé
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
Le vendredi 23 avril 2010, Kathryn Huxtable a écrit :
> I know Jason says he won't give ETAs, but is there any ETA on the site
> reporting? I make a lot of use of it, and I doubt I'm alone.
>
> My personal preference is to find some way to integrate the docbkx plugin
> with the site framework. I've got some code that does this for Maven 2,
> and it works for Maven 3, but the reports aren't generated.
>
> -K
>
> On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
> > The Maven team is pleased to announce the release of Apache Maven
> > 3.0-beta-1.
> >
> > Maven is a project comprehension and build tool, designed to simplify the
> > process of maintaining a healthy development lifecycle for your project.
> > You can read more here:
> >
> > http://maven.apache.org/
> >
> > Downloads of source and binary distributions are listed in our download
> > section:
> >
> > http://maven.apache.org/download.html
> >
> > A major goal of Maven 3.0 is to be compatible, to the extent possible,
> > with existing plugins and projects designed for Maven 2.x. Users
> > interested in testing this beta release should have a glance at the
> > compatibility notes for known differences between Maven 3.0 and Maven
> > 2.x:
> >
> > http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
> >
> > If you encounter unexpected problems while using Maven 3.0-beta-1, please
> > feel free to contact us via the Maven developer list:
> >
> > http://maven.apache.org/mail-lists.html
> >
> > Release Notes - Maven 2 & 3 - Version 3.0-beta-1
> >
> > ** Bug
> > * [MNG-1751] - merging metadata doesn't fail when timestamp is in the
> > future * [MNG-2103] - Inheritance of <plugin> overrides that of
> > <execution> * [MNG-2222] - dependency to dependency without source code
> > fails * [MNG-2276] - profile activation by property doesn't work with
> > properties defined in settings. * [MNG-2994] - Snapshot repositories are
> > not checked when using ranges * [MNG-3092] - Version ranges with
> > non-snapshot bounds can contain snapshot versions * [MNG-3133] -
> > DefaultModelInheritence::appendPath assumes it is operating on
> > interpolated/literal paths * [MNG-3470] - Build does not fail on
> > corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication
> > failures on dependency download aren't reported * [MNG-3529] - mvn -Da="
> > " throws an excepltion
> > * [MNG-3616] - Null Pointer Exception when mirrorOf missing from
> > mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone
> > plugin entries where inherited == false * [MNG-4022] - Incorrect merge
> > behavior using profile driven plugin configuration * [MNG-4326] - Maven
> > should not check snapshot repositories for dependencies in the reactor *
> > [MNG-4418] - Dependency resolution appears to misbehave if a remote
> > repository uses the id "local" * [MNG-4453] - [regression] Plugin
> > versions defined in a lifecycle mapping are not respected * [MNG-4555] -
> > mvn archetype:generate -o (offline) still results in a "checking updates
> > from central" * [MNG-4580] - Plugin dependencies for module ignored when
> > building from aggregator project using direct plugin invocation *
> > [MNG-4586] - Plugin prefix can't be resolved from plugin management if
> > management entry is missing plugin version * [MNG-4590] - [regression]
> > System properties are no longer interpolated in imported POMs *
> > [MNG-4600] - [regression] Optional flag from dependency management
> > applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar
> > fails with maven3 and multiple modules * [MNG-4625] - Interpolation of
> > settings.xml fails if an expression's value contains XML markup *
> > [MNG-4629] - [regression] POM validation fails upon non-existing
> > system-scope dependency * [MNG-4632] - Class loading is not thread-safe
> >
> > ** Improvement
> > * [MNG-1701] - Validate that a plugin is not configured twice in the
> > pom * [MNG-2187] - Improve error message when the pom is encoded in the
> > wrong charset * [MNG-2741] - [regression] Meaningless error message:
> > "Error transferring file" * [MNG-3004] - Allow build lifecycle to execute
> > projects in parallel * [MNG-3779] - Improve error message when trying to
> > execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting
> > logic from the core of Maven * [MNG-4194] - API to safely release of
> > plugin realms
> > * [MNG-4591] - Enhance the download rate output to include downloaded
> > file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM *
> > [MNG-4619] - Issue warning in case parent.relativePath points at POM with
> > different groupId/artifactId * [MNG-4623] - model parsing errors can be
> > less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not
> > setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead
> > * [MNG-4634] - Allow custom lifecycles
> >
> > ** Task
> > * [MNG-3917] - Complete the POM construction tests which will be the
> > validation for the specification
> >
> >
> > Enjoy,
> >
> >
> > -The Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Apache Maven 3.0-beta-1 Released
Posted by Kathryn Huxtable <ka...@kathrynhuxtable.org>.
I know Jason says he won't give ETAs, but is there any ETA on the site reporting? I make a lot of use of it, and I doubt I'm alone.
My personal preference is to find some way to integrate the docbkx plugin with the site framework. I've got some code that does this for Maven 2, and it works for Maven 3, but the reports aren't generated.
-K
On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote:
> The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1.
>
> Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here:
>
> http://maven.apache.org/
>
> Downloads of source and binary distributions are listed in our download section:
>
> http://maven.apache.org/download.html
>
> A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x:
>
> http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
>
> If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list:
>
> http://maven.apache.org/mail-lists.html
>
> Release Notes - Maven 2 & 3 - Version 3.0-beta-1
>
> ** Bug
> * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future
> * [MNG-2103] - Inheritance of <plugin> overrides that of <execution>
> * [MNG-2222] - dependency to dependency without source code fails
> * [MNG-2276] - profile activation by property doesn't work with properties defined in settings.
> * [MNG-2994] - Snapshot repositories are not checked when using ranges
> * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions
> * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths
> * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail
> * [MNG-3477] - Authentication failures on dependency download aren't reported
> * [MNG-3529] - mvn -Da=" " throws an excepltion
> * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml
> * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false
> * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration
> * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor
> * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id "local"
> * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected
> * [MNG-4555] - mvn archetype:generate -o (offline) still results in a "checking updates from central"
> * [MNG-4580] - Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation
> * [MNG-4586] - Plugin prefix can't be resolved from plugin management if management entry is missing plugin version
> * [MNG-4590] - [regression] System properties are no longer interpolated in imported POMs
> * [MNG-4600] - [regression] Optional flag from dependency management applied to dependencies
> * [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules
> * [MNG-4625] - Interpolation of settings.xml fails if an expression's value contains XML markup
> * [MNG-4629] - [regression] POM validation fails upon non-existing system-scope dependency
> * [MNG-4632] - Class loading is not thread-safe
>
> ** Improvement
> * [MNG-1701] - Validate that a plugin is not configured twice in the pom
> * [MNG-2187] - Improve error message when the pom is encoded in the wrong charset
> * [MNG-2741] - [regression] Meaningless error message: "Error transferring file"
> * [MNG-3004] - Allow build lifecycle to execute projects in parallel
> * [MNG-3779] - Improve error message when trying to execute mojo with no pom.xml
> * [MNG-4162] - Removal of all reporting logic from the core of Maven
> * [MNG-4194] - API to safely release of plugin realms
> * [MNG-4591] - Enhance the download rate output to include downloaded file name
> * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM
> * [MNG-4619] - Issue warning in case parent.relativePath points at POM with different groupId/artifactId
> * [MNG-4623] - model parsing errors can be less helpful in Maven 3
> * [MNG-4628] - ReactorArtifactRepository is not setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead
> * [MNG-4634] - Allow custom lifecycles
>
> ** Task
> * [MNG-3917] - Complete the POM construction tests which will be the validation for the specification
>
>
> Enjoy,
>
>
> -The Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org