You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2008/03/18 16:35:34 UTC
[Pre-Vote] release maven 2.0.9
The list of fixes in this release is substantial. See release notes at
the bottom. High level changes are: locking down the plugins in the
super pom, new import scope, new toolchain support, native webdav
support, execution inheritance=false is fixed, plugin dependency
overrides, errors in transfer won't corrupt the local repo, and
generally a lot of fixes for artifact resolution and other identified
regressions from the user list.
The release is staged at:
http://people.apache.org/~brianf/staging-repository/
The bundles are here:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.9/
I'll let this staged RC sit for a few days before calling the formal
vote.
Release Notes - Maven 2 - Version 2.0.9
** Bug
* [MNG-1412] - dependency sorting in classpath
* [MNG-1914] - Wrong url in error message when using a mirror
* [MNG-2123] - NullPointerException when a dependency uses version
range and another uses an actual version incompatible with that range
* [MNG-2145] - Plugins' dependencies are not always checked
* [MNG-2178] - incorrect M2_HOME guess in mvn.bat
* [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
profiles section is missing or empty
* [MNG-2339] - ${project.*} are interpreted in the wrong place
* [MNG-2744] - checksum comparison should be case-insensitive
* [MNG-2809] - Can't activate a profile by checking for the presence
of a file in ${user.home}
* [MNG-2848] - Environment variables in profile activation not
working
* [MNG-2861] - NullPointerException in DefaultArtifactCollector for
relocated resolvedArtifacts with different version ranges and available
versions.
* [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
there's no mojo in pom.xml
* [MNG-2928] - Null pointer exeception when introducing version
range [major.minor.build-SNAPSHOT,)
* [MNG-2956] - The documentation refers to system property
"user.dir" when it should refer to "user.home"
* [MNG-2972] - Ignores version of plugin dependency specified in my
pom
* [MNG-3086] - NullPointerException in
ResolutionNode.getTrail(ResolutionNode.java:136)
* [MNG-3099] - Profiles ignored when working with non-projects (such
as archetype:create)
* [MNG-3111] - Classpath order incorrect
* [MNG-3156] - NullPointerException with mvn dependency:sources
* [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
* [MNG-3259] - Regression: Maven drops dependencies in multi-module
build
* [MNG-3288] - Invalid systemPath allows build to continue--failing
in later phase.
* [MNG-3296] - mvn.bat looses error code on windows NT type
platforms
* [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
* [MNG-3316] - Barfs at attribues named .*encoding
* [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
with Novell login
* [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
${pom.build.testSourceDirectory} no longer recognized
* [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
* [MNG-3394] - Plugin versions inherited via <pluginManagement>
cannot be overriden by <build>.<plugins> section of sub modules
* [MNG-3396] - Managed versions dont affect over constrained ranges
* [MNG-3400] - MavenProject is not extensible
* [MNG-3405] - "Checking for updates from repository" logging should
not display if WagonManager is offline
* [MNG-3410] - Managed versions in plugins are not considered when
using them
* [MNG-3415] - Transfer errors cause junk metadata in the local repo
* [MNG-3426] - regression : <dependency> in plugin configuration
doesn't override plugin classpath
* [MNG-3430] - Toolchain doesn't match Toolchain extensions
* [MNG-3431] - Pom Extensions not supported for Toolchains
* [MNG-3439] - incorrect child dependency selected when parent is
not selected
* [MNG-3441] - Maven should always retrieve metadata to be updated
from the deployment repository
* [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
fails if you use a different local repo
* [MNG-3464] - maven-toolchains missing from final binary.. need to
update the assembly
** Improvement
* [MNG-428] - Japanese message resource
* [MNG-2881] - Improve logging when downloading snapshots in offline
mode
* [MNG-3119] - Duplicate attached artifacts should not be allowed.
* [MNG-3279] - Support Exception Chaining for MojoFailureException
* [MNG-3318] - ActiveProjectArtifact should have appropriate equals
and hashCode methods
* [MNG-3331] - Normalize paths to sub modules
* [MNG-3388] - DefaultPluginManager needs to catch LinkageError
* [MNG-3395] - Default core plugin versions in the superpom.
* [MNG-3442] - Add explicit resource bundle for English
* [MNG-3453] - Avoid references to the deprecated expression
"${project.build.resources}"
* [MNG-3461] - Mirrors should not apply to file:// repositories
** New Feature
* [MNG-2664] - Add native support for webdav
* [MNG-3360] - Added the documentation in the Maven release
** Task
* [MNG-2883] - Make sure that the network isn't used for snapshots
in offline mode when legacy repositories are used
** Wish
* [MNG-1491] - Reactor should print out a message if it detects a
collision of artifact ids
Re: [Pre-Vote] release maven 2.0.9
Posted by Raphaël Piéroni <ra...@gmail.com>.
+1 tested on the archetype plugin build.
Raphaël
2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> The list of fixes in this release is substantial. See release notes at
> the bottom. High level changes are: locking down the plugins in the
> super pom, new import scope, new toolchain support, native webdav
> support, execution inheritance=false is fixed, plugin dependency
> overrides, errors in transfer won't corrupt the local repo, and
> generally a lot of fixes for artifact resolution and other identified
> regressions from the user list.
>
>
>
> The release is staged at:
>
> http://people.apache.org/~brianf/staging-repository/
>
>
>
> The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/2.0.9/
>
>
>
> I'll let this staged RC sit for a few days before calling the formal
> vote.
>
>
>
> Release Notes - Maven 2 - Version 2.0.9
>
>
>
>
>
> ** Bug
>
> * [MNG-1412] - dependency sorting in classpath
>
> * [MNG-1914] - Wrong url in error message when using a mirror
>
> * [MNG-2123] - NullPointerException when a dependency uses version
> range and another uses an actual version incompatible with that range
>
> * [MNG-2145] - Plugins' dependencies are not always checked
>
> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>
> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> profiles section is missing or empty
>
> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>
> * [MNG-2744] - checksum comparison should be case-insensitive
>
> * [MNG-2809] - Can't activate a profile by checking for the presence
> of a file in ${user.home}
>
> * [MNG-2848] - Environment variables in profile activation not
> working
>
> * [MNG-2861] - NullPointerException in DefaultArtifactCollector for
> relocated resolvedArtifacts with different version ranges and available
> versions.
>
> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
> there's no mojo in pom.xml
>
> * [MNG-2928] - Null pointer exeception when introducing version
> range [major.minor.build-SNAPSHOT,)
>
> * [MNG-2956] - The documentation refers to system property
> "user.dir" when it should refer to "user.home"
>
> * [MNG-2972] - Ignores version of plugin dependency specified in my
> pom
>
> * [MNG-3086] - NullPointerException in
> ResolutionNode.getTrail(ResolutionNode.java:136)
>
> * [MNG-3099] - Profiles ignored when working with non-projects (such
> as archetype:create)
>
> * [MNG-3111] - Classpath order incorrect
>
> * [MNG-3156] - NullPointerException with mvn dependency:sources
>
> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>
> * [MNG-3259] - Regression: Maven drops dependencies in multi-module
> build
>
> * [MNG-3288] - Invalid systemPath allows build to continue--failing
> in later phase.
>
> * [MNG-3296] - mvn.bat looses error code on windows NT type
> platforms
>
> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>
> * [MNG-3316] - Barfs at attribues named .*encoding
>
> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> with Novell login
>
> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> ${pom.build.testSourceDirectory} no longer recognized
>
> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>
> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> cannot be overriden by <build>.<plugins> section of sub modules
>
> * [MNG-3396] - Managed versions dont affect over constrained ranges
>
> * [MNG-3400] - MavenProject is not extensible
>
> * [MNG-3405] - "Checking for updates from repository" logging should
> not display if WagonManager is offline
>
> * [MNG-3410] - Managed versions in plugins are not considered when
> using them
>
> * [MNG-3415] - Transfer errors cause junk metadata in the local repo
>
> * [MNG-3426] - regression : <dependency> in plugin configuration
> doesn't override plugin classpath
>
> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>
> * [MNG-3431] - Pom Extensions not supported for Toolchains
>
> * [MNG-3439] - incorrect child dependency selected when parent is
> not selected
>
> * [MNG-3441] - Maven should always retrieve metadata to be updated
> from the deployment repository
>
> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> fails if you use a different local repo
>
> * [MNG-3464] - maven-toolchains missing from final binary.. need to
> update the assembly
>
>
>
> ** Improvement
>
> * [MNG-428] - Japanese message resource
>
> * [MNG-2881] - Improve logging when downloading snapshots in offline
> mode
>
> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>
> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>
> * [MNG-3318] - ActiveProjectArtifact should have appropriate equals
> and hashCode methods
>
> * [MNG-3331] - Normalize paths to sub modules
>
> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>
> * [MNG-3395] - Default core plugin versions in the superpom.
>
> * [MNG-3442] - Add explicit resource bundle for English
>
> * [MNG-3453] - Avoid references to the deprecated expression
> "${project.build.resources}"
>
> * [MNG-3461] - Mirrors should not apply to file:// repositories
>
>
>
> ** New Feature
>
> * [MNG-2664] - Add native support for webdav
>
> * [MNG-3360] - Added the documentation in the Maven release
>
>
>
> ** Task
>
> * [MNG-2883] - Make sure that the network isn't used for snapshots
> in offline mode when legacy repositories are used
>
>
>
>
>
> ** Wish
>
> * [MNG-1491] - Reactor should print out a message if it detects a
> collision of artifact ids
>
>
[Pre-Vote take 2] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Adjusted the EAR plugin version to 2.3.1
The release is staged at:
http://people.apache.org/~brianf/staging-repository/
The bundles are here:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.9/
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Tuesday, March 18, 2008 11:36 AM
To: Maven Developers List
Subject: [Pre-Vote] release maven 2.0.9
The list of fixes in this release is substantial. See release notes at
the bottom. High level changes are: locking down the plugins in the
super pom, new import scope, new toolchain support, native webdav
support, execution inheritance=false is fixed, plugin dependency
overrides, errors in transfer won't corrupt the local repo, and
generally a lot of fixes for artifact resolution and other identified
regressions from the user list.
The release is staged at:
http://people.apache.org/~brianf/staging-repository/
The bundles are here:
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/2.0.9/
I'll let this staged RC sit for a few days before calling the formal
vote.
Release Notes - Maven 2 - Version 2.0.9
** Bug
* [MNG-1412] - dependency sorting in classpath
* [MNG-1914] - Wrong url in error message when using a mirror
* [MNG-2123] - NullPointerException when a dependency uses version
range and another uses an actual version incompatible with that range
* [MNG-2145] - Plugins' dependencies are not always checked
* [MNG-2178] - incorrect M2_HOME guess in mvn.bat
* [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
profiles section is missing or empty
* [MNG-2339] - ${project.*} are interpreted in the wrong place
* [MNG-2744] - checksum comparison should be case-insensitive
* [MNG-2809] - Can't activate a profile by checking for the presence
of a file in ${user.home}
* [MNG-2848] - Environment variables in profile activation not
working
* [MNG-2861] - NullPointerException in DefaultArtifactCollector for
relocated resolvedArtifacts with different version ranges and available
versions.
* [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
there's no mojo in pom.xml
* [MNG-2928] - Null pointer exeception when introducing version
range [major.minor.build-SNAPSHOT,)
* [MNG-2956] - The documentation refers to system property
"user.dir" when it should refer to "user.home"
* [MNG-2972] - Ignores version of plugin dependency specified in my
pom
* [MNG-3086] - NullPointerException in
ResolutionNode.getTrail(ResolutionNode.java:136)
* [MNG-3099] - Profiles ignored when working with non-projects (such
as archetype:create)
* [MNG-3111] - Classpath order incorrect
* [MNG-3156] - NullPointerException with mvn dependency:sources
* [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
* [MNG-3259] - Regression: Maven drops dependencies in multi-module
build
* [MNG-3288] - Invalid systemPath allows build to continue--failing
in later phase.
* [MNG-3296] - mvn.bat looses error code on windows NT type
platforms
* [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
* [MNG-3316] - Barfs at attribues named .*encoding
* [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
with Novell login
* [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
${pom.build.testSourceDirectory} no longer recognized
* [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
* [MNG-3394] - Plugin versions inherited via <pluginManagement>
cannot be overriden by <build>.<plugins> section of sub modules
* [MNG-3396] - Managed versions dont affect over constrained ranges
* [MNG-3400] - MavenProject is not extensible
* [MNG-3405] - "Checking for updates from repository" logging should
not display if WagonManager is offline
* [MNG-3410] - Managed versions in plugins are not considered when
using them
* [MNG-3415] - Transfer errors cause junk metadata in the local repo
* [MNG-3426] - regression : <dependency> in plugin configuration
doesn't override plugin classpath
* [MNG-3430] - Toolchain doesn't match Toolchain extensions
* [MNG-3431] - Pom Extensions not supported for Toolchains
* [MNG-3439] - incorrect child dependency selected when parent is
not selected
* [MNG-3441] - Maven should always retrieve metadata to be updated
from the deployment repository
* [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
fails if you use a different local repo
* [MNG-3464] - maven-toolchains missing from final binary.. need to
update the assembly
** Improvement
* [MNG-428] - Japanese message resource
* [MNG-2881] - Improve logging when downloading snapshots in offline
mode
* [MNG-3119] - Duplicate attached artifacts should not be allowed.
* [MNG-3279] - Support Exception Chaining for MojoFailureException
* [MNG-3318] - ActiveProjectArtifact should have appropriate equals
and hashCode methods
* [MNG-3331] - Normalize paths to sub modules
* [MNG-3388] - DefaultPluginManager needs to catch LinkageError
* [MNG-3395] - Default core plugin versions in the superpom.
* [MNG-3442] - Add explicit resource bundle for English
* [MNG-3453] - Avoid references to the deprecated expression
"${project.build.resources}"
* [MNG-3461] - Mirrors should not apply to file:// repositories
** New Feature
* [MNG-2664] - Add native support for webdav
* [MNG-3360] - Added the documentation in the Maven release
** Task
* [MNG-2883] - Make sure that the network isn't used for snapshots
in offline mode when legacy repositories are used
** Wish
* [MNG-1491] - Reactor should print out a message if it detects a
collision of artifact ids
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Sure, that'd be great.
-----Original Message-----
From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
On Behalf Of Paul Benedict
Sent: Tuesday, March 18, 2008 11:19 PM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
I'd like to contribute a table to the 2.0.9 release under the "issues
that
may affect build" section detailing the defaulted plugins and versions.
Can
I just attach it to MNG-3395?
Paul
On Tue, Mar 18, 2008 at 5:42 PM, Vincent Siveton
<vi...@gmail.com>
wrote:
> Hi Brian,
>
> Don't forget to call the include-site profile to include the site
> documentation in the release (MNG-3360)
>
> Cheers,
>
> Vincent
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes
at
> > the bottom. High level changes are: locking down the plugins in the
> > super pom, new import scope, new toolchain support, native webdav
> > support, execution inheritance=false is fixed, plugin dependency
> > overrides, errors in transfer won't corrupt the local repo, and
> > generally a lot of fixes for artifact resolution and other
identified
> > regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> >
http://people.apache.org/~brianf/staging-repository/<http://people.apach
e.org/%7Ebrianf/staging-repository/>
> >
> >
> >
> > The bundles are here:
> >
> >
>
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/
apa>
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the
formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses
version
> > range and another uses an actual version incompatible with that
range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
when
> > profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the
presence
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
for
> > relocated resolvedArtifacts with different version ranges and
available
> > versions.
> >
> > * [MNG-2925] - NullPointerException in
PluginDescriptor.getMojo() if
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in
my
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects
(such
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in
multi-module
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to
continue--failing
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
XP
> > with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained
ranges
> >
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging
should
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered
when
> > using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local
repo
> >
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent
is
> > not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be
updated
> > from the deployment repository
> >
> > * [MNG-3460] -
org.apache.maven.profiles.DefaultProfileManagerTest
> > fails if you use a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need
to
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in
offline
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be
allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for
MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate
equals
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for
snapshots
> > in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects
a
> > collision of artifact ids
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by Paul Benedict <pb...@apache.org>.
I'd like to contribute a table to the 2.0.9 release under the "issues that
may affect build" section detailing the defaulted plugins and versions. Can
I just attach it to MNG-3395?
Paul
On Tue, Mar 18, 2008 at 5:42 PM, Vincent Siveton <vi...@gmail.com>
wrote:
> Hi Brian,
>
> Don't forget to call the include-site profile to include the site
> documentation in the release (MNG-3360)
>
> Cheers,
>
> Vincent
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes at
> > the bottom. High level changes are: locking down the plugins in the
> > super pom, new import scope, new toolchain support, native webdav
> > support, execution inheritance=false is fixed, plugin dependency
> > overrides, errors in transfer won't corrupt the local repo, and
> > generally a lot of fixes for artifact resolution and other identified
> > regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> > http://people.apache.org/~brianf/staging-repository/<http://people.apache.org/%7Ebrianf/staging-repository/>
> >
> >
> >
> > The bundles are here:
> >
> >
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/apa>
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses version
> > range and another uses an actual version incompatible with that range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> > profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the presence
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector for
> > relocated resolvedArtifacts with different version ranges and available
> > versions.
> >
> > * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in my
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects (such
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in multi-module
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to continue--failing
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> > with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained ranges
> >
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging should
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered when
> > using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local repo
> >
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent is
> > not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be updated
> > from the deployment repository
> >
> > * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> > fails if you use a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need to
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in offline
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate equals
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for snapshots
> > in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects a
> > collision of artifact ids
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [Pre-Vote] release maven 2.0.9
Posted by Vincent Siveton <vi...@gmail.com>.
2008/3/19, Brian E. Fox <br...@reply.infinity.nu>:
> This seems a little weird. Why are we packaging up the entire site and
> deploying it in the assembly?
>
Because users want documentation. The only problem is that we don't
use tag for site.
Cheers,
Vincent
>
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Tuesday, March 18, 2008 6:42 PM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> Hi Brian,
>
> Don't forget to call the include-site profile to include the site
> documentation in the release (MNG-3360)
>
> Cheers,
>
> Vincent
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes at
> > the bottom. High level changes are: locking down the plugins in the
> > super pom, new import scope, new toolchain support, native webdav
> > support, execution inheritance=false is fixed, plugin dependency
> > overrides, errors in transfer won't corrupt the local repo, and
> > generally a lot of fixes for artifact resolution and other identified
> > regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> > http://people.apache.org/~brianf/staging-repository/
> >
> >
> >
> > The bundles are here:
> >
> >
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses version
> > range and another uses an actual version incompatible with that range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> > profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the
> presence
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
> for
> > relocated resolvedArtifacts with different version ranges and
> available
> > versions.
> >
> > * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo()
> if
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in
> my
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects
> (such
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in
> multi-module
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to
> continue--failing
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> > with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained
> ranges
> >
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging
> should
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered when
> > using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local
> repo
> >
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent is
> > not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be updated
> > from the deployment repository
> >
> > * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> > fails if you use a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need
> to
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in
> offline
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate
> equals
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for snapshots
> > in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects a
> > collision of artifact ids
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
http://jira.codehaus.org/browse/MNG-3360
If this profile is activated, the entire site gets jammed into the
bundle.
-----Original Message-----
From: Jason van Zyl [mailto:jason@maven.org]
Sent: Wednesday, March 19, 2008 11:09 AM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
On 19-Mar-08, at 7:54 AM, Brian E. Fox wrote:
> This seems a little weird. Why are we packaging up the entire site and
> deploying it in the assembly?
>
That's not right. Who started doing that?
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Tuesday, March 18, 2008 6:42 PM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> Hi Brian,
>
> Don't forget to call the include-site profile to include the site
> documentation in the release (MNG-3360)
>
> Cheers,
>
> Vincent
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
>> The list of fixes in this release is substantial. See release notes
>> at
>> the bottom. High level changes are: locking down the plugins in the
>> super pom, new import scope, new toolchain support, native webdav
>> support, execution inheritance=false is fixed, plugin dependency
>> overrides, errors in transfer won't corrupt the local repo, and
>> generally a lot of fixes for artifact resolution and other identified
>> regressions from the user list.
>>
>>
>>
>> The release is staged at:
>>
>> http://people.apache.org/~brianf/staging-repository/
>>
>>
>>
>> The bundles are here:
>>
>>
>
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
>> che-maven/2.0.9/
>>
>>
>>
>> I'll let this staged RC sit for a few days before calling the formal
>> vote.
>>
>>
>>
>> Release Notes - Maven 2 - Version 2.0.9
>>
>>
>>
>>
>>
>> ** Bug
>>
>> * [MNG-1412] - dependency sorting in classpath
>>
>> * [MNG-1914] - Wrong url in error message when using a mirror
>>
>> * [MNG-2123] - NullPointerException when a dependency uses version
>> range and another uses an actual version incompatible with that range
>>
>> * [MNG-2145] - Plugins' dependencies are not always checked
>>
>> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>>
>> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
>> profiles section is missing or empty
>>
>> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>>
>> * [MNG-2744] - checksum comparison should be case-insensitive
>>
>> * [MNG-2809] - Can't activate a profile by checking for the
> presence
>> of a file in ${user.home}
>>
>> * [MNG-2848] - Environment variables in profile activation not
>> working
>>
>> * [MNG-2861] - NullPointerException in DefaultArtifactCollector
> for
>> relocated resolvedArtifacts with different version ranges and
> available
>> versions.
>>
>> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo()
> if
>> there's no mojo in pom.xml
>>
>> * [MNG-2928] - Null pointer exeception when introducing version
>> range [major.minor.build-SNAPSHOT,)
>>
>> * [MNG-2956] - The documentation refers to system property
>> "user.dir" when it should refer to "user.home"
>>
>> * [MNG-2972] - Ignores version of plugin dependency specified in
> my
>> pom
>>
>> * [MNG-3086] - NullPointerException in
>> ResolutionNode.getTrail(ResolutionNode.java:136)
>>
>> * [MNG-3099] - Profiles ignored when working with non-projects
> (such
>> as archetype:create)
>>
>> * [MNG-3111] - Classpath order incorrect
>>
>> * [MNG-3156] - NullPointerException with mvn dependency:sources
>>
>> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>>
>> * [MNG-3259] - Regression: Maven drops dependencies in
> multi-module
>> build
>>
>> * [MNG-3288] - Invalid systemPath allows build to
> continue--failing
>> in later phase.
>>
>> * [MNG-3296] - mvn.bat looses error code on windows NT type
>> platforms
>>
>> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>>
>> * [MNG-3316] - Barfs at attribues named .*encoding
>>
>> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
>> with Novell login
>>
>> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
>> ${pom.build.testSourceDirectory} no longer recognized
>>
>> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>>
>> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
>> cannot be overriden by <build>.<plugins> section of sub modules
>>
>> * [MNG-3396] - Managed versions dont affect over constrained
> ranges
>>
>> * [MNG-3400] - MavenProject is not extensible
>>
>> * [MNG-3405] - "Checking for updates from repository" logging
> should
>> not display if WagonManager is offline
>>
>> * [MNG-3410] - Managed versions in plugins are not considered when
>> using them
>>
>> * [MNG-3415] - Transfer errors cause junk metadata in the local
> repo
>>
>> * [MNG-3426] - regression : <dependency> in plugin configuration
>> doesn't override plugin classpath
>>
>> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>>
>> * [MNG-3431] - Pom Extensions not supported for Toolchains
>>
>> * [MNG-3439] - incorrect child dependency selected when parent is
>> not selected
>>
>> * [MNG-3441] - Maven should always retrieve metadata to be updated
>> from the deployment repository
>>
>> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
>> fails if you use a different local repo
>>
>> * [MNG-3464] - maven-toolchains missing from final binary.. need
> to
>> update the assembly
>>
>>
>>
>> ** Improvement
>>
>> * [MNG-428] - Japanese message resource
>>
>> * [MNG-2881] - Improve logging when downloading snapshots in
> offline
>> mode
>>
>> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>>
>> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>>
>> * [MNG-3318] - ActiveProjectArtifact should have appropriate
> equals
>> and hashCode methods
>>
>> * [MNG-3331] - Normalize paths to sub modules
>>
>> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>>
>> * [MNG-3395] - Default core plugin versions in the superpom.
>>
>> * [MNG-3442] - Add explicit resource bundle for English
>>
>> * [MNG-3453] - Avoid references to the deprecated expression
>> "${project.build.resources}"
>>
>> * [MNG-3461] - Mirrors should not apply to file:// repositories
>>
>>
>>
>> ** New Feature
>>
>> * [MNG-2664] - Add native support for webdav
>>
>> * [MNG-3360] - Added the documentation in the Maven release
>>
>>
>>
>> ** Task
>>
>> * [MNG-2883] - Make sure that the network isn't used for snapshots
>> in offline mode when legacy repositories are used
>>
>>
>>
>>
>>
>> ** Wish
>>
>> * [MNG-1491] - Reactor should print out a message if it detects a
>> collision of artifact ids
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by Jason van Zyl <ja...@maven.org>.
On 19-Mar-08, at 7:54 AM, Brian E. Fox wrote:
> This seems a little weird. Why are we packaging up the entire site and
> deploying it in the assembly?
>
That's not right. Who started doing that?
> -----Original Message-----
> From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
> Sent: Tuesday, March 18, 2008 6:42 PM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> Hi Brian,
>
> Don't forget to call the include-site profile to include the site
> documentation in the release (MNG-3360)
>
> Cheers,
>
> Vincent
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
>> The list of fixes in this release is substantial. See release notes
>> at
>> the bottom. High level changes are: locking down the plugins in the
>> super pom, new import scope, new toolchain support, native webdav
>> support, execution inheritance=false is fixed, plugin dependency
>> overrides, errors in transfer won't corrupt the local repo, and
>> generally a lot of fixes for artifact resolution and other identified
>> regressions from the user list.
>>
>>
>>
>> The release is staged at:
>>
>> http://people.apache.org/~brianf/staging-repository/
>>
>>
>>
>> The bundles are here:
>>
>>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
>> che-maven/2.0.9/
>>
>>
>>
>> I'll let this staged RC sit for a few days before calling the formal
>> vote.
>>
>>
>>
>> Release Notes - Maven 2 - Version 2.0.9
>>
>>
>>
>>
>>
>> ** Bug
>>
>> * [MNG-1412] - dependency sorting in classpath
>>
>> * [MNG-1914] - Wrong url in error message when using a mirror
>>
>> * [MNG-2123] - NullPointerException when a dependency uses version
>> range and another uses an actual version incompatible with that range
>>
>> * [MNG-2145] - Plugins' dependencies are not always checked
>>
>> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>>
>> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
>> profiles section is missing or empty
>>
>> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>>
>> * [MNG-2744] - checksum comparison should be case-insensitive
>>
>> * [MNG-2809] - Can't activate a profile by checking for the
> presence
>> of a file in ${user.home}
>>
>> * [MNG-2848] - Environment variables in profile activation not
>> working
>>
>> * [MNG-2861] - NullPointerException in DefaultArtifactCollector
> for
>> relocated resolvedArtifacts with different version ranges and
> available
>> versions.
>>
>> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo()
> if
>> there's no mojo in pom.xml
>>
>> * [MNG-2928] - Null pointer exeception when introducing version
>> range [major.minor.build-SNAPSHOT,)
>>
>> * [MNG-2956] - The documentation refers to system property
>> "user.dir" when it should refer to "user.home"
>>
>> * [MNG-2972] - Ignores version of plugin dependency specified in
> my
>> pom
>>
>> * [MNG-3086] - NullPointerException in
>> ResolutionNode.getTrail(ResolutionNode.java:136)
>>
>> * [MNG-3099] - Profiles ignored when working with non-projects
> (such
>> as archetype:create)
>>
>> * [MNG-3111] - Classpath order incorrect
>>
>> * [MNG-3156] - NullPointerException with mvn dependency:sources
>>
>> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>>
>> * [MNG-3259] - Regression: Maven drops dependencies in
> multi-module
>> build
>>
>> * [MNG-3288] - Invalid systemPath allows build to
> continue--failing
>> in later phase.
>>
>> * [MNG-3296] - mvn.bat looses error code on windows NT type
>> platforms
>>
>> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>>
>> * [MNG-3316] - Barfs at attribues named .*encoding
>>
>> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
>> with Novell login
>>
>> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
>> ${pom.build.testSourceDirectory} no longer recognized
>>
>> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>>
>> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
>> cannot be overriden by <build>.<plugins> section of sub modules
>>
>> * [MNG-3396] - Managed versions dont affect over constrained
> ranges
>>
>> * [MNG-3400] - MavenProject is not extensible
>>
>> * [MNG-3405] - "Checking for updates from repository" logging
> should
>> not display if WagonManager is offline
>>
>> * [MNG-3410] - Managed versions in plugins are not considered when
>> using them
>>
>> * [MNG-3415] - Transfer errors cause junk metadata in the local
> repo
>>
>> * [MNG-3426] - regression : <dependency> in plugin configuration
>> doesn't override plugin classpath
>>
>> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>>
>> * [MNG-3431] - Pom Extensions not supported for Toolchains
>>
>> * [MNG-3439] - incorrect child dependency selected when parent is
>> not selected
>>
>> * [MNG-3441] - Maven should always retrieve metadata to be updated
>> from the deployment repository
>>
>> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
>> fails if you use a different local repo
>>
>> * [MNG-3464] - maven-toolchains missing from final binary.. need
> to
>> update the assembly
>>
>>
>>
>> ** Improvement
>>
>> * [MNG-428] - Japanese message resource
>>
>> * [MNG-2881] - Improve logging when downloading snapshots in
> offline
>> mode
>>
>> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>>
>> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>>
>> * [MNG-3318] - ActiveProjectArtifact should have appropriate
> equals
>> and hashCode methods
>>
>> * [MNG-3331] - Normalize paths to sub modules
>>
>> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>>
>> * [MNG-3395] - Default core plugin versions in the superpom.
>>
>> * [MNG-3442] - Add explicit resource bundle for English
>>
>> * [MNG-3453] - Avoid references to the deprecated expression
>> "${project.build.resources}"
>>
>> * [MNG-3461] - Mirrors should not apply to file:// repositories
>>
>>
>>
>> ** New Feature
>>
>> * [MNG-2664] - Add native support for webdav
>>
>> * [MNG-3360] - Added the documentation in the Maven release
>>
>>
>>
>> ** Task
>>
>> * [MNG-2883] - Make sure that the network isn't used for snapshots
>> in offline mode when legacy repositories are used
>>
>>
>>
>>
>>
>> ** Wish
>>
>> * [MNG-1491] - Reactor should print out a message if it detects a
>> collision of artifact ids
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Pre-Vote] release maven 2.0.9
Posted by Vincent Siveton <vi...@gmail.com>.
2008/3/19, Wendy Smoak <ws...@gmail.com>:
> On Wed, Mar 19, 2008 at 7:54 AM, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> > This seems a little weird. Why are we packaging up the entire site and
> > deploying it in the assembly?
>
>
> I don't think it should go inside the Maven distribution, but a
> separate docs assembly would be nice to have.
>
> What is it meant to contain? Just maven/site/trunk, or also the
> reference docs (Javadoc, reports?) Are any plugin docs included?
We already have it. See the maven-site-1.0-site.jar in the download page.
Like said, we could starting tagging the site when doing a release.
Cheers,
Vincent
> --
>
> Wendy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, Mar 19, 2008 at 7:54 AM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> This seems a little weird. Why are we packaging up the entire site and
> deploying it in the assembly?
I don't think it should go inside the Maven distribution, but a
separate docs assembly would be nice to have.
What is it meant to contain? Just maven/site/trunk, or also the
reference docs (Javadoc, reports?) Are any plugin docs included?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
This seems a little weird. Why are we packaging up the entire site and
deploying it in the assembly?
-----Original Message-----
From: Vincent Siveton [mailto:vincent.siveton@gmail.com]
Sent: Tuesday, March 18, 2008 6:42 PM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
Hi Brian,
Don't forget to call the include-site profile to include the site
documentation in the release (MNG-3360)
Cheers,
Vincent
2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> The list of fixes in this release is substantial. See release notes at
> the bottom. High level changes are: locking down the plugins in the
> super pom, new import scope, new toolchain support, native webdav
> support, execution inheritance=false is fixed, plugin dependency
> overrides, errors in transfer won't corrupt the local repo, and
> generally a lot of fixes for artifact resolution and other identified
> regressions from the user list.
>
>
>
> The release is staged at:
>
> http://people.apache.org/~brianf/staging-repository/
>
>
>
> The bundles are here:
>
>
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/2.0.9/
>
>
>
> I'll let this staged RC sit for a few days before calling the formal
> vote.
>
>
>
> Release Notes - Maven 2 - Version 2.0.9
>
>
>
>
>
> ** Bug
>
> * [MNG-1412] - dependency sorting in classpath
>
> * [MNG-1914] - Wrong url in error message when using a mirror
>
> * [MNG-2123] - NullPointerException when a dependency uses version
> range and another uses an actual version incompatible with that range
>
> * [MNG-2145] - Plugins' dependencies are not always checked
>
> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>
> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> profiles section is missing or empty
>
> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>
> * [MNG-2744] - checksum comparison should be case-insensitive
>
> * [MNG-2809] - Can't activate a profile by checking for the
presence
> of a file in ${user.home}
>
> * [MNG-2848] - Environment variables in profile activation not
> working
>
> * [MNG-2861] - NullPointerException in DefaultArtifactCollector
for
> relocated resolvedArtifacts with different version ranges and
available
> versions.
>
> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo()
if
> there's no mojo in pom.xml
>
> * [MNG-2928] - Null pointer exeception when introducing version
> range [major.minor.build-SNAPSHOT,)
>
> * [MNG-2956] - The documentation refers to system property
> "user.dir" when it should refer to "user.home"
>
> * [MNG-2972] - Ignores version of plugin dependency specified in
my
> pom
>
> * [MNG-3086] - NullPointerException in
> ResolutionNode.getTrail(ResolutionNode.java:136)
>
> * [MNG-3099] - Profiles ignored when working with non-projects
(such
> as archetype:create)
>
> * [MNG-3111] - Classpath order incorrect
>
> * [MNG-3156] - NullPointerException with mvn dependency:sources
>
> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>
> * [MNG-3259] - Regression: Maven drops dependencies in
multi-module
> build
>
> * [MNG-3288] - Invalid systemPath allows build to
continue--failing
> in later phase.
>
> * [MNG-3296] - mvn.bat looses error code on windows NT type
> platforms
>
> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>
> * [MNG-3316] - Barfs at attribues named .*encoding
>
> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> with Novell login
>
> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> ${pom.build.testSourceDirectory} no longer recognized
>
> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>
> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> cannot be overriden by <build>.<plugins> section of sub modules
>
> * [MNG-3396] - Managed versions dont affect over constrained
ranges
>
> * [MNG-3400] - MavenProject is not extensible
>
> * [MNG-3405] - "Checking for updates from repository" logging
should
> not display if WagonManager is offline
>
> * [MNG-3410] - Managed versions in plugins are not considered when
> using them
>
> * [MNG-3415] - Transfer errors cause junk metadata in the local
repo
>
> * [MNG-3426] - regression : <dependency> in plugin configuration
> doesn't override plugin classpath
>
> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>
> * [MNG-3431] - Pom Extensions not supported for Toolchains
>
> * [MNG-3439] - incorrect child dependency selected when parent is
> not selected
>
> * [MNG-3441] - Maven should always retrieve metadata to be updated
> from the deployment repository
>
> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> fails if you use a different local repo
>
> * [MNG-3464] - maven-toolchains missing from final binary.. need
to
> update the assembly
>
>
>
> ** Improvement
>
> * [MNG-428] - Japanese message resource
>
> * [MNG-2881] - Improve logging when downloading snapshots in
offline
> mode
>
> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>
> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>
> * [MNG-3318] - ActiveProjectArtifact should have appropriate
equals
> and hashCode methods
>
> * [MNG-3331] - Normalize paths to sub modules
>
> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>
> * [MNG-3395] - Default core plugin versions in the superpom.
>
> * [MNG-3442] - Add explicit resource bundle for English
>
> * [MNG-3453] - Avoid references to the deprecated expression
> "${project.build.resources}"
>
> * [MNG-3461] - Mirrors should not apply to file:// repositories
>
>
>
> ** New Feature
>
> * [MNG-2664] - Add native support for webdav
>
> * [MNG-3360] - Added the documentation in the Maven release
>
>
>
> ** Task
>
> * [MNG-2883] - Make sure that the network isn't used for snapshots
> in offline mode when legacy repositories are used
>
>
>
>
>
> ** Wish
>
> * [MNG-1491] - Reactor should print out a message if it detects a
> collision of artifact ids
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Brian,
Don't forget to call the include-site profile to include the site
documentation in the release (MNG-3360)
Cheers,
Vincent
2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> The list of fixes in this release is substantial. See release notes at
> the bottom. High level changes are: locking down the plugins in the
> super pom, new import scope, new toolchain support, native webdav
> support, execution inheritance=false is fixed, plugin dependency
> overrides, errors in transfer won't corrupt the local repo, and
> generally a lot of fixes for artifact resolution and other identified
> regressions from the user list.
>
>
>
> The release is staged at:
>
> http://people.apache.org/~brianf/staging-repository/
>
>
>
> The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/2.0.9/
>
>
>
> I'll let this staged RC sit for a few days before calling the formal
> vote.
>
>
>
> Release Notes - Maven 2 - Version 2.0.9
>
>
>
>
>
> ** Bug
>
> * [MNG-1412] - dependency sorting in classpath
>
> * [MNG-1914] - Wrong url in error message when using a mirror
>
> * [MNG-2123] - NullPointerException when a dependency uses version
> range and another uses an actual version incompatible with that range
>
> * [MNG-2145] - Plugins' dependencies are not always checked
>
> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>
> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> profiles section is missing or empty
>
> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>
> * [MNG-2744] - checksum comparison should be case-insensitive
>
> * [MNG-2809] - Can't activate a profile by checking for the presence
> of a file in ${user.home}
>
> * [MNG-2848] - Environment variables in profile activation not
> working
>
> * [MNG-2861] - NullPointerException in DefaultArtifactCollector for
> relocated resolvedArtifacts with different version ranges and available
> versions.
>
> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
> there's no mojo in pom.xml
>
> * [MNG-2928] - Null pointer exeception when introducing version
> range [major.minor.build-SNAPSHOT,)
>
> * [MNG-2956] - The documentation refers to system property
> "user.dir" when it should refer to "user.home"
>
> * [MNG-2972] - Ignores version of plugin dependency specified in my
> pom
>
> * [MNG-3086] - NullPointerException in
> ResolutionNode.getTrail(ResolutionNode.java:136)
>
> * [MNG-3099] - Profiles ignored when working with non-projects (such
> as archetype:create)
>
> * [MNG-3111] - Classpath order incorrect
>
> * [MNG-3156] - NullPointerException with mvn dependency:sources
>
> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>
> * [MNG-3259] - Regression: Maven drops dependencies in multi-module
> build
>
> * [MNG-3288] - Invalid systemPath allows build to continue--failing
> in later phase.
>
> * [MNG-3296] - mvn.bat looses error code on windows NT type
> platforms
>
> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>
> * [MNG-3316] - Barfs at attribues named .*encoding
>
> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> with Novell login
>
> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> ${pom.build.testSourceDirectory} no longer recognized
>
> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>
> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> cannot be overriden by <build>.<plugins> section of sub modules
>
> * [MNG-3396] - Managed versions dont affect over constrained ranges
>
> * [MNG-3400] - MavenProject is not extensible
>
> * [MNG-3405] - "Checking for updates from repository" logging should
> not display if WagonManager is offline
>
> * [MNG-3410] - Managed versions in plugins are not considered when
> using them
>
> * [MNG-3415] - Transfer errors cause junk metadata in the local repo
>
> * [MNG-3426] - regression : <dependency> in plugin configuration
> doesn't override plugin classpath
>
> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>
> * [MNG-3431] - Pom Extensions not supported for Toolchains
>
> * [MNG-3439] - incorrect child dependency selected when parent is
> not selected
>
> * [MNG-3441] - Maven should always retrieve metadata to be updated
> from the deployment repository
>
> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> fails if you use a different local repo
>
> * [MNG-3464] - maven-toolchains missing from final binary.. need to
> update the assembly
>
>
>
> ** Improvement
>
> * [MNG-428] - Japanese message resource
>
> * [MNG-2881] - Improve logging when downloading snapshots in offline
> mode
>
> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>
> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>
> * [MNG-3318] - ActiveProjectArtifact should have appropriate equals
> and hashCode methods
>
> * [MNG-3331] - Normalize paths to sub modules
>
> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>
> * [MNG-3395] - Default core plugin versions in the superpom.
>
> * [MNG-3442] - Add explicit resource bundle for English
>
> * [MNG-3453] - Avoid references to the deprecated expression
> "${project.build.resources}"
>
> * [MNG-3461] - Mirrors should not apply to file:// repositories
>
>
>
> ** New Feature
>
> * [MNG-2664] - Add native support for webdav
>
> * [MNG-3360] - Added the documentation in the Maven release
>
>
>
> ** Task
>
> * [MNG-2883] - Make sure that the network isn't used for snapshots
> in offline mode when legacy repositories are used
>
>
>
>
>
> ** Wish
>
> * [MNG-1491] - Reactor should print out a message if it detects a
> collision of artifact ids
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Huh? This wasn't a vote and I restaged it already....
-----Original Message-----
From: Sejal Patel [mailto:sepatel@gmail.com]
Sent: Wednesday, March 19, 2008 5:41 PM
To: Maven Developers List
Cc: Daniel Kulp
Subject: Re: [Pre-Vote] release maven 2.0.9
Not to be a party pooper but given all the discussions that are cropping
up
over and around this release, I feel like a vote of -1 is in order.
On Wed, Mar 19, 2008 at 11:42 AM, Brian E. Fox
<br...@reply.infinity.nu>
wrote:
> >Well, the auto-update of the archetype-plugin certainly has caused a
> LOT
> >of issues lately. Would that be considered one of your "commonly
used
>
> >utilities"?
>
> Normally yes, but it's already out there and locking down to alpha-2
> probably isn't a good idea as it will block lots of people from
getting
> the later alphas. Once it's out of alpha/beta then yes we should lock
> it.
>
> Here's my initial thought process: Only lock down default plugins and
> some utils like assembly, dependency etc. These should be locked to
the
> current latest version so that anyone using 2.0.8 that hasn't already
> locked them down (which should still be best practice) doesn't get
> downgraded.
>
> Later on, we should not lock down to anything but a full release
unless
> there is significant cause to do otherwise. Also, I think we should
not
> lock down to anything that has been released less than 30 days again
> unless there is a good reason. We don't want to find out about
> regressions by locking down on a new version.
>
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, March 19, 2008 11:33 AM
> To: dev@maven.apache.org
> Cc: Brian E. Fox
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
>
> Well, the auto-update of the archetype-plugin certainly has caused a
LOT
>
> of issues lately. Would that be considered one of your "commonly
used
> utilities"?
>
> Dan
>
> On Wednesday 19 March 2008, Brian E. Fox wrote:
> > Crap. I'll have to fix the ear version. The other stuff I don't
think
> > needs to be locked down. The goal was to lock down the most
important
> > plugins, things that directly affect a build as part of the default
> > lifecycle and commonly used utilities. I don't think we want to
start
> > including every single plugin in here, it was never the intent.
> >
> > -----Original Message-----
> > From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
> > Behalf Of nicolas de loof
> > Sent: Wednesday, March 19, 2008 11:18 AM
> > To: Maven Developers List
> > Subject: Re: [Pre-Vote] release maven 2.0.9
> >
> > I notice some official maven plugin don't have fixed version in the
> > super-POM :
> >
> > maven-archetype-plugin
> > maven-checkstyle-plugin
> > maven-eclipse-plugin
> > maven-idea-plugin
> > maven-jxr-plugin
> > maven-invoker-plugin
> > maven-one-plugin
> > maven-patch-plugin
> > maven-pmd-plugin
> > maven-projecthelp-plugin
> > maven-remote-resources-plugin
> > maven-repository-plugin
> > maven-shade-plugin
> > maven-scm-plugin
> > maven-stage-plugin
> > maven-verifier-plugin
> > maven-project-info-reports-plugin
> > maven-surefire-report-plugin
> >
> >
> > maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
> > available.
> >
> > Also maven-install-plugin is not right ordered considering
alphabetic
> > order
> > (not an issue but makes this check more difficult)
> >
> > 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > > The list of fixes in this release is substantial. See release
notes
> > > at the bottom. High level changes are: locking down the plugins in
> > > the super pom, new import scope, new toolchain support, native
> > > webdav support, execution inheritance=false is fixed, plugin
> > > dependency overrides, errors in transfer won't corrupt the local
> > > repo, and generally a lot of fixes for artifact resolution and
other
> > > identified regressions from the user list.
> > >
> > >
> > >
> > > The release is staged at:
> > >
> > >
http://people.apache.org/~brianf/staging-repository/<http://people.apach
e.org/%7Ebrianf/staging-repository/>
> > >
> > >
> > >
> > > The bundles are here:
> >
> >
http://people.apache.org/~brianf/staging-repository/org/apache/maven/a<h
ttp://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/a>
> >pa
> >
> > > che-maven/2.0.9/
> > >
> > >
> > >
> > > I'll let this staged RC sit for a few days before calling the
formal
> > > vote.
> > >
> > >
> > >
> > > Release Notes - Maven 2 - Version 2.0.9
> > >
> > >
> > >
> > >
> > >
> > > ** Bug
> > >
> > > * [MNG-1412] - dependency sorting in classpath
> > >
> > > * [MNG-1914] - Wrong url in error message when using a mirror
> > >
> > > * [MNG-2123] - NullPointerException when a dependency uses
> > > version range and another uses an actual version incompatible with
> > > that range
> > >
> > > * [MNG-2145] - Plugins' dependencies are not always checked
> > >
> > > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> > >
> > > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
> > > when profiles section is missing or empty
> > >
> > > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> > >
> > > * [MNG-2744] - checksum comparison should be case-insensitive
> > >
> > > * [MNG-2809] - Can't activate a profile by checking for the
> >
> > presence
> >
> > > of a file in ${user.home}
> > >
> > > * [MNG-2848] - Environment variables in profile activation not
> > > working
> > >
> > > * [MNG-2861] - NullPointerException in
DefaultArtifactCollector
> >
> > for
> >
> > > relocated resolvedArtifacts with different version ranges and
> >
> > available
> >
> > > versions.
> > >
> > > * [MNG-2925] - NullPointerException in
> > > PluginDescriptor.getMojo()
> >
> > if
> >
> > > there's no mojo in pom.xml
> > >
> > > * [MNG-2928] - Null pointer exeception when introducing
version
> > > range [major.minor.build-SNAPSHOT,)
> > >
> > > * [MNG-2956] - The documentation refers to system property
> > > "user.dir" when it should refer to "user.home"
> > >
> > > * [MNG-2972] - Ignores version of plugin dependency specified
in
> >
> > my
> >
> > > pom
> > >
> > > * [MNG-3086] - NullPointerException in
> > > ResolutionNode.getTrail(ResolutionNode.java:136)
> > >
> > > * [MNG-3099] - Profiles ignored when working with non-projects
> >
> > (such
> >
> > > as archetype:create)
> > >
> > > * [MNG-3111] - Classpath order incorrect
> > >
> > > * [MNG-3156] - NullPointerException with mvn
dependency:sources
> > >
> > > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> > >
> > > * [MNG-3259] - Regression: Maven drops dependencies in
> >
> > multi-module
> >
> > > build
> > >
> > > * [MNG-3288] - Invalid systemPath allows build to
> >
> > continue--failing
> >
> > > in later phase.
> > >
> > > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > > platforms
> > >
> > > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not
set
> > >
> > > * [MNG-3316] - Barfs at attribues named .*encoding
> > >
> > > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
> > > XP with Novell login
> > >
> > > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > > ${pom.build.testSourceDirectory} no longer recognized
> > >
> > > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
> > > mvn.bat
> > >
> > > * [MNG-3394] - Plugin versions inherited via
<pluginManagement>
> > > cannot be overriden by <build>.<plugins> section of sub modules
> > >
> > > * [MNG-3396] - Managed versions dont affect over constrained
> >
> > ranges
> >
> > > * [MNG-3400] - MavenProject is not extensible
> > >
> > > * [MNG-3405] - "Checking for updates from repository" logging
> >
> > should
> >
> > > not display if WagonManager is offline
> > >
> > > * [MNG-3410] - Managed versions in plugins are not considered
> > > when using them
> > >
> > > * [MNG-3415] - Transfer errors cause junk metadata in the
local
> >
> > repo
> >
> > > * [MNG-3426] - regression : <dependency> in plugin
configuration
> > > doesn't override plugin classpath
> > >
> > > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> > >
> > > * [MNG-3431] - Pom Extensions not supported for Toolchains
> > >
> > > * [MNG-3439] - incorrect child dependency selected when parent
> > > is not selected
> > >
> > > * [MNG-3441] - Maven should always retrieve metadata to be
> > > updated from the deployment repository
> > >
> > > * [MNG-3460] -
> > > org.apache.maven.profiles.DefaultProfileManagerTest fails if you
use
> > > a different local repo
> > >
> > > * [MNG-3464] - maven-toolchains missing from final binary..
need
> >
> > to
> >
> > > update the assembly
> > >
> > >
> > >
> > > ** Improvement
> > >
> > > * [MNG-428] - Japanese message resource
> > >
> > > * [MNG-2881] - Improve logging when downloading snapshots in
> >
> > offline
> >
> > > mode
> > >
> > > * [MNG-3119] - Duplicate attached artifacts should not be
> > > allowed.
> > >
> > > * [MNG-3279] - Support Exception Chaining for
> > > MojoFailureException
> > >
> > > * [MNG-3318] - ActiveProjectArtifact should have appropriate
> >
> > equals
> >
> > > and hashCode methods
> > >
> > > * [MNG-3331] - Normalize paths to sub modules
> > >
> > > * [MNG-3388] - DefaultPluginManager needs to catch
LinkageError
> > >
> > > * [MNG-3395] - Default core plugin versions in the superpom.
> > >
> > > * [MNG-3442] - Add explicit resource bundle for English
> > >
> > > * [MNG-3453] - Avoid references to the deprecated expression
> > > "${project.build.resources}"
> > >
> > > * [MNG-3461] - Mirrors should not apply to file://
repositories
> > >
> > >
> > >
> > > ** New Feature
> > >
> > > * [MNG-2664] - Add native support for webdav
> > >
> > > * [MNG-3360] - Added the documentation in the Maven release
> > >
> > >
> > >
> > > ** Task
> > >
> > > * [MNG-2883] - Make sure that the network isn't used for
> > > snapshots in offline mode when legacy repositories are used
> > >
> > >
> > >
> > >
> > >
> > > ** Wish
> > >
> > > * [MNG-1491] - Reactor should print out a message if it
detects
> > > a collision of artifact ids
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Justice is nothing more than that which is in the greatest self-interest
of
the largest portion of the population.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Pre-Vote] release maven 2.0.9
Posted by Sejal Patel <se...@gmail.com>.
Ah yes I did miss that.I've been seeing a combination of plugins not being
locked down and in other threads people using the 2.0.9 snapshot having
problems with their plugins and didn't see that you had locked them down
specifically. I also just now see in the previous thread why they are being
locked down to alpha/beta versions as well (which was a concern of mine).
On Wed, Mar 19, 2008 at 5:53 PM, Paul Benedict <pb...@apache.org> wrote:
> Sejal,
>
> You must have missed the previous responses that said that only plug-ins
> that affect the build cycle will be locked down. So the list below is
> incorrect. Nicolas was making a comment/suggestion, not stating what *is*
> locked down.
>
> For the record, this is from the Maven 2.0.9 POM (minus config):
>
> http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=markup&pathrev=637049
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-clean-plugin</artifactId>
> <version>2.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.0.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-deploy-plugin</artifactId>
> <version>2.3</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-gpg-plugin</artifactId>
> <version>1.0-alpha-4</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-install-plugin</artifactId>
> <version>2.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <version>2.3</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-plugin-plugin</artifactId>
> <version>2.3</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-7</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-remote-resources-plugin</artifactId>
> <version>1.0-beta-2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-resources-plugin</artifactId>
> <version>2.2</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <version>2.0-beta-6</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-source-plugin</artifactId>
> <version>2.0.4</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.4.2</version>
> </plugin>
>
> Paul
>
--
Justice is nothing more than that which is in the greatest self-interest of
the largest portion of the population.
Re: [Pre-Vote] release maven 2.0.9
Posted by Paul Benedict <pb...@apache.org>.
Sejal,
You must have missed the previous responses that said that only plug-ins
that affect the build cycle will be locked down. So the list below is
incorrect. Nicolas was making a comment/suggestion, not stating what *is*
locked down.
For the record, this is from the Maven 2.0.9 POM (minus config):
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=markup&pathrev=637049
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.3</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>1.0-alpha-4</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.3</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-plugin-plugin</artifactId>
<version>2.3</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-7</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-remote-resources-plugin</artifactId>
<version>1.0-beta-2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>2.0-beta-6</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.0.4</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4.2</version>
</plugin>
Paul
Re: [Pre-Vote] release maven 2.0.9
Posted by Sejal Patel <se...@gmail.com>.
Not to be a party pooper but given all the discussions that are cropping up
over and around this release, I feel like a vote of -1 is in order.
On Wed, Mar 19, 2008 at 11:42 AM, Brian E. Fox <br...@reply.infinity.nu>
wrote:
> >Well, the auto-update of the archetype-plugin certainly has caused a
> LOT
> >of issues lately. Would that be considered one of your "commonly used
>
> >utilities"?
>
> Normally yes, but it's already out there and locking down to alpha-2
> probably isn't a good idea as it will block lots of people from getting
> the later alphas. Once it's out of alpha/beta then yes we should lock
> it.
>
> Here's my initial thought process: Only lock down default plugins and
> some utils like assembly, dependency etc. These should be locked to the
> current latest version so that anyone using 2.0.8 that hasn't already
> locked them down (which should still be best practice) doesn't get
> downgraded.
>
> Later on, we should not lock down to anything but a full release unless
> there is significant cause to do otherwise. Also, I think we should not
> lock down to anything that has been released less than 30 days again
> unless there is a good reason. We don't want to find out about
> regressions by locking down on a new version.
>
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Wednesday, March 19, 2008 11:33 AM
> To: dev@maven.apache.org
> Cc: Brian E. Fox
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
>
> Well, the auto-update of the archetype-plugin certainly has caused a LOT
>
> of issues lately. Would that be considered one of your "commonly used
> utilities"?
>
> Dan
>
> On Wednesday 19 March 2008, Brian E. Fox wrote:
> > Crap. I'll have to fix the ear version. The other stuff I don't think
> > needs to be locked down. The goal was to lock down the most important
> > plugins, things that directly affect a build as part of the default
> > lifecycle and commonly used utilities. I don't think we want to start
> > including every single plugin in here, it was never the intent.
> >
> > -----Original Message-----
> > From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
> > Behalf Of nicolas de loof
> > Sent: Wednesday, March 19, 2008 11:18 AM
> > To: Maven Developers List
> > Subject: Re: [Pre-Vote] release maven 2.0.9
> >
> > I notice some official maven plugin don't have fixed version in the
> > super-POM :
> >
> > maven-archetype-plugin
> > maven-checkstyle-plugin
> > maven-eclipse-plugin
> > maven-idea-plugin
> > maven-jxr-plugin
> > maven-invoker-plugin
> > maven-one-plugin
> > maven-patch-plugin
> > maven-pmd-plugin
> > maven-projecthelp-plugin
> > maven-remote-resources-plugin
> > maven-repository-plugin
> > maven-shade-plugin
> > maven-scm-plugin
> > maven-stage-plugin
> > maven-verifier-plugin
> > maven-project-info-reports-plugin
> > maven-surefire-report-plugin
> >
> >
> > maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
> > available.
> >
> > Also maven-install-plugin is not right ordered considering alphabetic
> > order
> > (not an issue but makes this check more difficult)
> >
> > 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > > The list of fixes in this release is substantial. See release notes
> > > at the bottom. High level changes are: locking down the plugins in
> > > the super pom, new import scope, new toolchain support, native
> > > webdav support, execution inheritance=false is fixed, plugin
> > > dependency overrides, errors in transfer won't corrupt the local
> > > repo, and generally a lot of fixes for artifact resolution and other
> > > identified regressions from the user list.
> > >
> > >
> > >
> > > The release is staged at:
> > >
> > > http://people.apache.org/~brianf/staging-repository/<http://people.apache.org/%7Ebrianf/staging-repository/>
> > >
> > >
> > >
> > > The bundles are here:
> >
> > http://people.apache.org/~brianf/staging-repository/org/apache/maven/a<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/a>
> >pa
> >
> > > che-maven/2.0.9/
> > >
> > >
> > >
> > > I'll let this staged RC sit for a few days before calling the formal
> > > vote.
> > >
> > >
> > >
> > > Release Notes - Maven 2 - Version 2.0.9
> > >
> > >
> > >
> > >
> > >
> > > ** Bug
> > >
> > > * [MNG-1412] - dependency sorting in classpath
> > >
> > > * [MNG-1914] - Wrong url in error message when using a mirror
> > >
> > > * [MNG-2123] - NullPointerException when a dependency uses
> > > version range and another uses an actual version incompatible with
> > > that range
> > >
> > > * [MNG-2145] - Plugins' dependencies are not always checked
> > >
> > > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> > >
> > > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
> > > when profiles section is missing or empty
> > >
> > > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> > >
> > > * [MNG-2744] - checksum comparison should be case-insensitive
> > >
> > > * [MNG-2809] - Can't activate a profile by checking for the
> >
> > presence
> >
> > > of a file in ${user.home}
> > >
> > > * [MNG-2848] - Environment variables in profile activation not
> > > working
> > >
> > > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
> >
> > for
> >
> > > relocated resolvedArtifacts with different version ranges and
> >
> > available
> >
> > > versions.
> > >
> > > * [MNG-2925] - NullPointerException in
> > > PluginDescriptor.getMojo()
> >
> > if
> >
> > > there's no mojo in pom.xml
> > >
> > > * [MNG-2928] - Null pointer exeception when introducing version
> > > range [major.minor.build-SNAPSHOT,)
> > >
> > > * [MNG-2956] - The documentation refers to system property
> > > "user.dir" when it should refer to "user.home"
> > >
> > > * [MNG-2972] - Ignores version of plugin dependency specified in
> >
> > my
> >
> > > pom
> > >
> > > * [MNG-3086] - NullPointerException in
> > > ResolutionNode.getTrail(ResolutionNode.java:136)
> > >
> > > * [MNG-3099] - Profiles ignored when working with non-projects
> >
> > (such
> >
> > > as archetype:create)
> > >
> > > * [MNG-3111] - Classpath order incorrect
> > >
> > > * [MNG-3156] - NullPointerException with mvn dependency:sources
> > >
> > > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> > >
> > > * [MNG-3259] - Regression: Maven drops dependencies in
> >
> > multi-module
> >
> > > build
> > >
> > > * [MNG-3288] - Invalid systemPath allows build to
> >
> > continue--failing
> >
> > > in later phase.
> > >
> > > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > > platforms
> > >
> > > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> > >
> > > * [MNG-3316] - Barfs at attribues named .*encoding
> > >
> > > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
> > > XP with Novell login
> > >
> > > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > > ${pom.build.testSourceDirectory} no longer recognized
> > >
> > > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
> > > mvn.bat
> > >
> > > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > > cannot be overriden by <build>.<plugins> section of sub modules
> > >
> > > * [MNG-3396] - Managed versions dont affect over constrained
> >
> > ranges
> >
> > > * [MNG-3400] - MavenProject is not extensible
> > >
> > > * [MNG-3405] - "Checking for updates from repository" logging
> >
> > should
> >
> > > not display if WagonManager is offline
> > >
> > > * [MNG-3410] - Managed versions in plugins are not considered
> > > when using them
> > >
> > > * [MNG-3415] - Transfer errors cause junk metadata in the local
> >
> > repo
> >
> > > * [MNG-3426] - regression : <dependency> in plugin configuration
> > > doesn't override plugin classpath
> > >
> > > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> > >
> > > * [MNG-3431] - Pom Extensions not supported for Toolchains
> > >
> > > * [MNG-3439] - incorrect child dependency selected when parent
> > > is not selected
> > >
> > > * [MNG-3441] - Maven should always retrieve metadata to be
> > > updated from the deployment repository
> > >
> > > * [MNG-3460] -
> > > org.apache.maven.profiles.DefaultProfileManagerTest fails if you use
> > > a different local repo
> > >
> > > * [MNG-3464] - maven-toolchains missing from final binary.. need
> >
> > to
> >
> > > update the assembly
> > >
> > >
> > >
> > > ** Improvement
> > >
> > > * [MNG-428] - Japanese message resource
> > >
> > > * [MNG-2881] - Improve logging when downloading snapshots in
> >
> > offline
> >
> > > mode
> > >
> > > * [MNG-3119] - Duplicate attached artifacts should not be
> > > allowed.
> > >
> > > * [MNG-3279] - Support Exception Chaining for
> > > MojoFailureException
> > >
> > > * [MNG-3318] - ActiveProjectArtifact should have appropriate
> >
> > equals
> >
> > > and hashCode methods
> > >
> > > * [MNG-3331] - Normalize paths to sub modules
> > >
> > > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> > >
> > > * [MNG-3395] - Default core plugin versions in the superpom.
> > >
> > > * [MNG-3442] - Add explicit resource bundle for English
> > >
> > > * [MNG-3453] - Avoid references to the deprecated expression
> > > "${project.build.resources}"
> > >
> > > * [MNG-3461] - Mirrors should not apply to file:// repositories
> > >
> > >
> > >
> > > ** New Feature
> > >
> > > * [MNG-2664] - Add native support for webdav
> > >
> > > * [MNG-3360] - Added the documentation in the Maven release
> > >
> > >
> > >
> > > ** Task
> > >
> > > * [MNG-2883] - Make sure that the network isn't used for
> > > snapshots in offline mode when legacy repositories are used
> > >
> > >
> > >
> > >
> > >
> > > ** Wish
> > >
> > > * [MNG-1491] - Reactor should print out a message if it detects
> > > a collision of artifact ids
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Justice is nothing more than that which is in the greatest self-interest of
the largest portion of the population.
RE: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Another update,
We tracked down the 3473 issue and John made a fix for it because the
change that caused the problem (3426) was correct, but it just exposed
other issues. In the process we found 3 regressions in the plugin tools
[1] that essentially break existing builds and/or are not compatible
with the fixes in 2.0.9. So the plan now is to quickly fix and stage the
plugin tools 2.5 (fixing only the 3 issues really causing regressions
from 2.3) and then we can proceed to restage 2.0.9. (most likely in
parallel with 2.5 in the same staging repo)
[1]
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide
&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11139&fixfor=
14138
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, March 20, 2008 3:31 PM
To: Maven Developers List
Subject: RE: [Pre-Vote] release maven 2.0.9
We uncovered a regression in 2.0.9 somehow related to the plugin tools:
http://jira.codehaus.org/browse/MNG-3473
John is helping me to track it down, but we'll end up respinning this
release again.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 19, 2008 11:42 AM
To: Daniel Kulp; dev@maven.apache.org
Subject: RE: [Pre-Vote] release maven 2.0.9
>Well, the auto-update of the archetype-plugin certainly has caused a
LOT
>of issues lately. Would that be considered one of your "commonly used
>utilities"?
Normally yes, but it's already out there and locking down to alpha-2
probably isn't a good idea as it will block lots of people from getting
the later alphas. Once it's out of alpha/beta then yes we should lock
it.
Here's my initial thought process: Only lock down default plugins and
some utils like assembly, dependency etc. These should be locked to the
current latest version so that anyone using 2.0.8 that hasn't already
locked them down (which should still be best practice) doesn't get
downgraded.
Later on, we should not lock down to anything but a full release unless
there is significant cause to do otherwise. Also, I think we should not
lock down to anything that has been released less than 30 days again
unless there is a good reason. We don't want to find out about
regressions by locking down on a new version.
-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org]
Sent: Wednesday, March 19, 2008 11:33 AM
To: dev@maven.apache.org
Cc: Brian E. Fox
Subject: Re: [Pre-Vote] release maven 2.0.9
Well, the auto-update of the archetype-plugin certainly has caused a LOT
of issues lately. Would that be considered one of your "commonly used
utilities"?
Dan
On Wednesday 19 March 2008, Brian E. Fox wrote:
> Crap. I'll have to fix the ear version. The other stuff I don't think
> needs to be locked down. The goal was to lock down the most important
> plugins, things that directly affect a build as part of the default
> lifecycle and commonly used utilities. I don't think we want to start
> including every single plugin in here, it was never the intent.
>
> -----Original Message-----
> From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
> Behalf Of nicolas de loof
> Sent: Wednesday, March 19, 2008 11:18 AM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> I notice some official maven plugin don't have fixed version in the
> super-POM :
>
> maven-archetype-plugin
> maven-checkstyle-plugin
> maven-eclipse-plugin
> maven-idea-plugin
> maven-jxr-plugin
> maven-invoker-plugin
> maven-one-plugin
> maven-patch-plugin
> maven-pmd-plugin
> maven-projecthelp-plugin
> maven-remote-resources-plugin
> maven-repository-plugin
> maven-shade-plugin
> maven-scm-plugin
> maven-stage-plugin
> maven-verifier-plugin
> maven-project-info-reports-plugin
> maven-surefire-report-plugin
>
>
> maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
> available.
>
> Also maven-install-plugin is not right ordered considering alphabetic
> order
> (not an issue but makes this check more difficult)
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes
> > at the bottom. High level changes are: locking down the plugins in
> > the super pom, new import scope, new toolchain support, native
> > webdav support, execution inheritance=false is fixed, plugin
> > dependency overrides, errors in transfer won't corrupt the local
> > repo, and generally a lot of fixes for artifact resolution and other
> > identified regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> > http://people.apache.org/~brianf/staging-repository/
> >
> >
> >
> > The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/a
>pa
>
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses
> > version range and another uses an actual version incompatible with
> > that range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
> > when profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the
>
> presence
>
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
>
> for
>
> > relocated resolvedArtifacts with different version ranges and
>
> available
>
> > versions.
> >
> > * [MNG-2925] - NullPointerException in
> > PluginDescriptor.getMojo()
>
> if
>
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in
>
> my
>
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects
>
> (such
>
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in
>
> multi-module
>
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to
>
> continue--failing
>
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
> > XP with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
> > mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained
>
> ranges
>
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging
>
> should
>
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered
> > when using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local
>
> repo
>
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent
> > is not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be
> > updated from the deployment repository
> >
> > * [MNG-3460] -
> > org.apache.maven.profiles.DefaultProfileManagerTest fails if you use
> > a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need
>
> to
>
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in
>
> offline
>
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be
> > allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for
> > MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate
>
> equals
>
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for
> > snapshots in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects
> > a collision of artifact ids
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
We uncovered a regression in 2.0.9 somehow related to the plugin tools:
http://jira.codehaus.org/browse/MNG-3473
John is helping me to track it down, but we'll end up respinning this
release again.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, March 19, 2008 11:42 AM
To: Daniel Kulp; dev@maven.apache.org
Subject: RE: [Pre-Vote] release maven 2.0.9
>Well, the auto-update of the archetype-plugin certainly has caused a
LOT
>of issues lately. Would that be considered one of your "commonly used
>utilities"?
Normally yes, but it's already out there and locking down to alpha-2
probably isn't a good idea as it will block lots of people from getting
the later alphas. Once it's out of alpha/beta then yes we should lock
it.
Here's my initial thought process: Only lock down default plugins and
some utils like assembly, dependency etc. These should be locked to the
current latest version so that anyone using 2.0.8 that hasn't already
locked them down (which should still be best practice) doesn't get
downgraded.
Later on, we should not lock down to anything but a full release unless
there is significant cause to do otherwise. Also, I think we should not
lock down to anything that has been released less than 30 days again
unless there is a good reason. We don't want to find out about
regressions by locking down on a new version.
-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org]
Sent: Wednesday, March 19, 2008 11:33 AM
To: dev@maven.apache.org
Cc: Brian E. Fox
Subject: Re: [Pre-Vote] release maven 2.0.9
Well, the auto-update of the archetype-plugin certainly has caused a LOT
of issues lately. Would that be considered one of your "commonly used
utilities"?
Dan
On Wednesday 19 March 2008, Brian E. Fox wrote:
> Crap. I'll have to fix the ear version. The other stuff I don't think
> needs to be locked down. The goal was to lock down the most important
> plugins, things that directly affect a build as part of the default
> lifecycle and commonly used utilities. I don't think we want to start
> including every single plugin in here, it was never the intent.
>
> -----Original Message-----
> From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
> Behalf Of nicolas de loof
> Sent: Wednesday, March 19, 2008 11:18 AM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> I notice some official maven plugin don't have fixed version in the
> super-POM :
>
> maven-archetype-plugin
> maven-checkstyle-plugin
> maven-eclipse-plugin
> maven-idea-plugin
> maven-jxr-plugin
> maven-invoker-plugin
> maven-one-plugin
> maven-patch-plugin
> maven-pmd-plugin
> maven-projecthelp-plugin
> maven-remote-resources-plugin
> maven-repository-plugin
> maven-shade-plugin
> maven-scm-plugin
> maven-stage-plugin
> maven-verifier-plugin
> maven-project-info-reports-plugin
> maven-surefire-report-plugin
>
>
> maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
> available.
>
> Also maven-install-plugin is not right ordered considering alphabetic
> order
> (not an issue but makes this check more difficult)
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes
> > at the bottom. High level changes are: locking down the plugins in
> > the super pom, new import scope, new toolchain support, native
> > webdav support, execution inheritance=false is fixed, plugin
> > dependency overrides, errors in transfer won't corrupt the local
> > repo, and generally a lot of fixes for artifact resolution and other
> > identified regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> > http://people.apache.org/~brianf/staging-repository/
> >
> >
> >
> > The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/a
>pa
>
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses
> > version range and another uses an actual version incompatible with
> > that range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
> > when profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the
>
> presence
>
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
>
> for
>
> > relocated resolvedArtifacts with different version ranges and
>
> available
>
> > versions.
> >
> > * [MNG-2925] - NullPointerException in
> > PluginDescriptor.getMojo()
>
> if
>
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in
>
> my
>
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects
>
> (such
>
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in
>
> multi-module
>
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to
>
> continue--failing
>
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
> > XP with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
> > mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained
>
> ranges
>
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging
>
> should
>
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered
> > when using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local
>
> repo
>
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent
> > is not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be
> > updated from the deployment repository
> >
> > * [MNG-3460] -
> > org.apache.maven.profiles.DefaultProfileManagerTest fails if you use
> > a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need
>
> to
>
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in
>
> offline
>
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be
> > allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for
> > MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate
>
> equals
>
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for
> > snapshots in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects
> > a collision of artifact ids
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>Well, the auto-update of the archetype-plugin certainly has caused a
LOT
>of issues lately. Would that be considered one of your "commonly used
>utilities"?
Normally yes, but it's already out there and locking down to alpha-2
probably isn't a good idea as it will block lots of people from getting
the later alphas. Once it's out of alpha/beta then yes we should lock
it.
Here's my initial thought process: Only lock down default plugins and
some utils like assembly, dependency etc. These should be locked to the
current latest version so that anyone using 2.0.8 that hasn't already
locked them down (which should still be best practice) doesn't get
downgraded.
Later on, we should not lock down to anything but a full release unless
there is significant cause to do otherwise. Also, I think we should not
lock down to anything that has been released less than 30 days again
unless there is a good reason. We don't want to find out about
regressions by locking down on a new version.
-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org]
Sent: Wednesday, March 19, 2008 11:33 AM
To: dev@maven.apache.org
Cc: Brian E. Fox
Subject: Re: [Pre-Vote] release maven 2.0.9
Well, the auto-update of the archetype-plugin certainly has caused a LOT
of issues lately. Would that be considered one of your "commonly used
utilities"?
Dan
On Wednesday 19 March 2008, Brian E. Fox wrote:
> Crap. I'll have to fix the ear version. The other stuff I don't think
> needs to be locked down. The goal was to lock down the most important
> plugins, things that directly affect a build as part of the default
> lifecycle and commonly used utilities. I don't think we want to start
> including every single plugin in here, it was never the intent.
>
> -----Original Message-----
> From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
> Behalf Of nicolas de loof
> Sent: Wednesday, March 19, 2008 11:18 AM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> I notice some official maven plugin don't have fixed version in the
> super-POM :
>
> maven-archetype-plugin
> maven-checkstyle-plugin
> maven-eclipse-plugin
> maven-idea-plugin
> maven-jxr-plugin
> maven-invoker-plugin
> maven-one-plugin
> maven-patch-plugin
> maven-pmd-plugin
> maven-projecthelp-plugin
> maven-remote-resources-plugin
> maven-repository-plugin
> maven-shade-plugin
> maven-scm-plugin
> maven-stage-plugin
> maven-verifier-plugin
> maven-project-info-reports-plugin
> maven-surefire-report-plugin
>
>
> maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
> available.
>
> Also maven-install-plugin is not right ordered considering alphabetic
> order
> (not an issue but makes this check more difficult)
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes
> > at the bottom. High level changes are: locking down the plugins in
> > the super pom, new import scope, new toolchain support, native
> > webdav support, execution inheritance=false is fixed, plugin
> > dependency overrides, errors in transfer won't corrupt the local
> > repo, and generally a lot of fixes for artifact resolution and other
> > identified regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> > http://people.apache.org/~brianf/staging-repository/
> >
> >
> >
> > The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/a
>pa
>
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses
> > version range and another uses an actual version incompatible with
> > that range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
> > when profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the
>
> presence
>
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
>
> for
>
> > relocated resolvedArtifacts with different version ranges and
>
> available
>
> > versions.
> >
> > * [MNG-2925] - NullPointerException in
> > PluginDescriptor.getMojo()
>
> if
>
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in
>
> my
>
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects
>
> (such
>
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in
>
> multi-module
>
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to
>
> continue--failing
>
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
> > XP with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
> > mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained
>
> ranges
>
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging
>
> should
>
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered
> > when using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local
>
> repo
>
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent
> > is not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be
> > updated from the deployment repository
> >
> > * [MNG-3460] -
> > org.apache.maven.profiles.DefaultProfileManagerTest fails if you use
> > a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need
>
> to
>
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in
>
> offline
>
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be
> > allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for
> > MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate
>
> equals
>
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for
> > snapshots in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects
> > a collision of artifact ids
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Pre-Vote] release maven 2.0.9
Posted by Daniel Kulp <dk...@apache.org>.
Well, the auto-update of the archetype-plugin certainly has caused a LOT
of issues lately. Would that be considered one of your "commonly used
utilities"?
Dan
On Wednesday 19 March 2008, Brian E. Fox wrote:
> Crap. I'll have to fix the ear version. The other stuff I don't think
> needs to be locked down. The goal was to lock down the most important
> plugins, things that directly affect a build as part of the default
> lifecycle and commonly used utilities. I don't think we want to start
> including every single plugin in here, it was never the intent.
>
> -----Original Message-----
> From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
> Behalf Of nicolas de loof
> Sent: Wednesday, March 19, 2008 11:18 AM
> To: Maven Developers List
> Subject: Re: [Pre-Vote] release maven 2.0.9
>
> I notice some official maven plugin don't have fixed version in the
> super-POM :
>
> maven-archetype-plugin
> maven-checkstyle-plugin
> maven-eclipse-plugin
> maven-idea-plugin
> maven-jxr-plugin
> maven-invoker-plugin
> maven-one-plugin
> maven-patch-plugin
> maven-pmd-plugin
> maven-projecthelp-plugin
> maven-remote-resources-plugin
> maven-repository-plugin
> maven-shade-plugin
> maven-scm-plugin
> maven-stage-plugin
> maven-verifier-plugin
> maven-project-info-reports-plugin
> maven-surefire-report-plugin
>
>
> maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
> available.
>
> Also maven-install-plugin is not right ordered considering alphabetic
> order
> (not an issue but makes this check more difficult)
>
> 2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
> > The list of fixes in this release is substantial. See release notes
> > at the bottom. High level changes are: locking down the plugins in
> > the super pom, new import scope, new toolchain support, native
> > webdav support, execution inheritance=false is fixed, plugin
> > dependency overrides, errors in transfer won't corrupt the local
> > repo, and generally a lot of fixes for artifact resolution and other
> > identified regressions from the user list.
> >
> >
> >
> > The release is staged at:
> >
> > http://people.apache.org/~brianf/staging-repository/
> >
> >
> >
> > The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/a
>pa
>
> > che-maven/2.0.9/
> >
> >
> >
> > I'll let this staged RC sit for a few days before calling the formal
> > vote.
> >
> >
> >
> > Release Notes - Maven 2 - Version 2.0.9
> >
> >
> >
> >
> >
> > ** Bug
> >
> > * [MNG-1412] - dependency sorting in classpath
> >
> > * [MNG-1914] - Wrong url in error message when using a mirror
> >
> > * [MNG-2123] - NullPointerException when a dependency uses
> > version range and another uses an actual version incompatible with
> > that range
> >
> > * [MNG-2145] - Plugins' dependencies are not always checked
> >
> > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
> >
> > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored
> > when profiles section is missing or empty
> >
> > * [MNG-2339] - ${project.*} are interpreted in the wrong place
> >
> > * [MNG-2744] - checksum comparison should be case-insensitive
> >
> > * [MNG-2809] - Can't activate a profile by checking for the
>
> presence
>
> > of a file in ${user.home}
> >
> > * [MNG-2848] - Environment variables in profile activation not
> > working
> >
> > * [MNG-2861] - NullPointerException in DefaultArtifactCollector
>
> for
>
> > relocated resolvedArtifacts with different version ranges and
>
> available
>
> > versions.
> >
> > * [MNG-2925] - NullPointerException in
> > PluginDescriptor.getMojo()
>
> if
>
> > there's no mojo in pom.xml
> >
> > * [MNG-2928] - Null pointer exeception when introducing version
> > range [major.minor.build-SNAPSHOT,)
> >
> > * [MNG-2956] - The documentation refers to system property
> > "user.dir" when it should refer to "user.home"
> >
> > * [MNG-2972] - Ignores version of plugin dependency specified in
>
> my
>
> > pom
> >
> > * [MNG-3086] - NullPointerException in
> > ResolutionNode.getTrail(ResolutionNode.java:136)
> >
> > * [MNG-3099] - Profiles ignored when working with non-projects
>
> (such
>
> > as archetype:create)
> >
> > * [MNG-3111] - Classpath order incorrect
> >
> > * [MNG-3156] - NullPointerException with mvn dependency:sources
> >
> > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
> >
> > * [MNG-3259] - Regression: Maven drops dependencies in
>
> multi-module
>
> > build
> >
> > * [MNG-3288] - Invalid systemPath allows build to
>
> continue--failing
>
> > in later phase.
> >
> > * [MNG-3296] - mvn.bat looses error code on windows NT type
> > platforms
> >
> > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
> >
> > * [MNG-3316] - Barfs at attribues named .*encoding
> >
> > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or
> > XP with Novell login
> >
> > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> > ${pom.build.testSourceDirectory} no longer recognized
> >
> > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in
> > mvn.bat
> >
> > * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> > cannot be overriden by <build>.<plugins> section of sub modules
> >
> > * [MNG-3396] - Managed versions dont affect over constrained
>
> ranges
>
> > * [MNG-3400] - MavenProject is not extensible
> >
> > * [MNG-3405] - "Checking for updates from repository" logging
>
> should
>
> > not display if WagonManager is offline
> >
> > * [MNG-3410] - Managed versions in plugins are not considered
> > when using them
> >
> > * [MNG-3415] - Transfer errors cause junk metadata in the local
>
> repo
>
> > * [MNG-3426] - regression : <dependency> in plugin configuration
> > doesn't override plugin classpath
> >
> > * [MNG-3430] - Toolchain doesn't match Toolchain extensions
> >
> > * [MNG-3431] - Pom Extensions not supported for Toolchains
> >
> > * [MNG-3439] - incorrect child dependency selected when parent
> > is not selected
> >
> > * [MNG-3441] - Maven should always retrieve metadata to be
> > updated from the deployment repository
> >
> > * [MNG-3460] -
> > org.apache.maven.profiles.DefaultProfileManagerTest fails if you use
> > a different local repo
> >
> > * [MNG-3464] - maven-toolchains missing from final binary.. need
>
> to
>
> > update the assembly
> >
> >
> >
> > ** Improvement
> >
> > * [MNG-428] - Japanese message resource
> >
> > * [MNG-2881] - Improve logging when downloading snapshots in
>
> offline
>
> > mode
> >
> > * [MNG-3119] - Duplicate attached artifacts should not be
> > allowed.
> >
> > * [MNG-3279] - Support Exception Chaining for
> > MojoFailureException
> >
> > * [MNG-3318] - ActiveProjectArtifact should have appropriate
>
> equals
>
> > and hashCode methods
> >
> > * [MNG-3331] - Normalize paths to sub modules
> >
> > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
> >
> > * [MNG-3395] - Default core plugin versions in the superpom.
> >
> > * [MNG-3442] - Add explicit resource bundle for English
> >
> > * [MNG-3453] - Avoid references to the deprecated expression
> > "${project.build.resources}"
> >
> > * [MNG-3461] - Mirrors should not apply to file:// repositories
> >
> >
> >
> > ** New Feature
> >
> > * [MNG-2664] - Add native support for webdav
> >
> > * [MNG-3360] - Added the documentation in the Maven release
> >
> >
> >
> > ** Task
> >
> > * [MNG-2883] - Make sure that the network isn't used for
> > snapshots in offline mode when legacy repositories are used
> >
> >
> >
> >
> >
> > ** Wish
> >
> > * [MNG-1491] - Reactor should print out a message if it detects
> > a collision of artifact ids
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Crap. I'll have to fix the ear version. The other stuff I don't think
needs to be locked down. The goal was to lock down the most important
plugins, things that directly affect a build as part of the default
lifecycle and commonly used utilities. I don't think we want to start
including every single plugin in here, it was never the intent.
-----Original Message-----
From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On
Behalf Of nicolas de loof
Sent: Wednesday, March 19, 2008 11:18 AM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
I notice some official maven plugin don't have fixed version in the
super-POM :
maven-archetype-plugin
maven-checkstyle-plugin
maven-eclipse-plugin
maven-idea-plugin
maven-jxr-plugin
maven-invoker-plugin
maven-one-plugin
maven-patch-plugin
maven-pmd-plugin
maven-projecthelp-plugin
maven-remote-resources-plugin
maven-repository-plugin
maven-shade-plugin
maven-scm-plugin
maven-stage-plugin
maven-verifier-plugin
maven-project-info-reports-plugin
maven-surefire-report-plugin
maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
available.
Also maven-install-plugin is not right ordered considering alphabetic
order
(not an issue but makes this check more difficult)
2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
>
> The list of fixes in this release is substantial. See release notes at
> the bottom. High level changes are: locking down the plugins in the
> super pom, new import scope, new toolchain support, native webdav
> support, execution inheritance=false is fixed, plugin dependency
> overrides, errors in transfer won't corrupt the local repo, and
> generally a lot of fixes for artifact resolution and other identified
> regressions from the user list.
>
>
>
> The release is staged at:
>
> http://people.apache.org/~brianf/staging-repository/
>
>
>
> The bundles are here:
>
>
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/2.0.9/
>
>
>
> I'll let this staged RC sit for a few days before calling the formal
> vote.
>
>
>
> Release Notes - Maven 2 - Version 2.0.9
>
>
>
>
>
> ** Bug
>
> * [MNG-1412] - dependency sorting in classpath
>
> * [MNG-1914] - Wrong url in error message when using a mirror
>
> * [MNG-2123] - NullPointerException when a dependency uses version
> range and another uses an actual version incompatible with that range
>
> * [MNG-2145] - Plugins' dependencies are not always checked
>
> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>
> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> profiles section is missing or empty
>
> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>
> * [MNG-2744] - checksum comparison should be case-insensitive
>
> * [MNG-2809] - Can't activate a profile by checking for the
presence
> of a file in ${user.home}
>
> * [MNG-2848] - Environment variables in profile activation not
> working
>
> * [MNG-2861] - NullPointerException in DefaultArtifactCollector
for
> relocated resolvedArtifacts with different version ranges and
available
> versions.
>
> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo()
if
> there's no mojo in pom.xml
>
> * [MNG-2928] - Null pointer exeception when introducing version
> range [major.minor.build-SNAPSHOT,)
>
> * [MNG-2956] - The documentation refers to system property
> "user.dir" when it should refer to "user.home"
>
> * [MNG-2972] - Ignores version of plugin dependency specified in
my
> pom
>
> * [MNG-3086] - NullPointerException in
> ResolutionNode.getTrail(ResolutionNode.java:136)
>
> * [MNG-3099] - Profiles ignored when working with non-projects
(such
> as archetype:create)
>
> * [MNG-3111] - Classpath order incorrect
>
> * [MNG-3156] - NullPointerException with mvn dependency:sources
>
> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>
> * [MNG-3259] - Regression: Maven drops dependencies in
multi-module
> build
>
> * [MNG-3288] - Invalid systemPath allows build to
continue--failing
> in later phase.
>
> * [MNG-3296] - mvn.bat looses error code on windows NT type
> platforms
>
> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>
> * [MNG-3316] - Barfs at attribues named .*encoding
>
> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> with Novell login
>
> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> ${pom.build.testSourceDirectory} no longer recognized
>
> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>
> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> cannot be overriden by <build>.<plugins> section of sub modules
>
> * [MNG-3396] - Managed versions dont affect over constrained
ranges
>
> * [MNG-3400] - MavenProject is not extensible
>
> * [MNG-3405] - "Checking for updates from repository" logging
should
> not display if WagonManager is offline
>
> * [MNG-3410] - Managed versions in plugins are not considered when
> using them
>
> * [MNG-3415] - Transfer errors cause junk metadata in the local
repo
>
> * [MNG-3426] - regression : <dependency> in plugin configuration
> doesn't override plugin classpath
>
> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>
> * [MNG-3431] - Pom Extensions not supported for Toolchains
>
> * [MNG-3439] - incorrect child dependency selected when parent is
> not selected
>
> * [MNG-3441] - Maven should always retrieve metadata to be updated
> from the deployment repository
>
> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> fails if you use a different local repo
>
> * [MNG-3464] - maven-toolchains missing from final binary.. need
to
> update the assembly
>
>
>
> ** Improvement
>
> * [MNG-428] - Japanese message resource
>
> * [MNG-2881] - Improve logging when downloading snapshots in
offline
> mode
>
> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>
> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>
> * [MNG-3318] - ActiveProjectArtifact should have appropriate
equals
> and hashCode methods
>
> * [MNG-3331] - Normalize paths to sub modules
>
> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>
> * [MNG-3395] - Default core plugin versions in the superpom.
>
> * [MNG-3442] - Add explicit resource bundle for English
>
> * [MNG-3453] - Avoid references to the deprecated expression
> "${project.build.resources}"
>
> * [MNG-3461] - Mirrors should not apply to file:// repositories
>
>
>
> ** New Feature
>
> * [MNG-2664] - Add native support for webdav
>
> * [MNG-3360] - Added the documentation in the Maven release
>
>
>
> ** Task
>
> * [MNG-2883] - Make sure that the network isn't used for snapshots
> in offline mode when legacy repositories are used
>
>
>
>
>
> ** Wish
>
> * [MNG-1491] - Reactor should print out a message if it detects a
> collision of artifact ids
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Pre-Vote] release maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
There's already a jira for it, scheduled for 2.1 as it introduces new elements to the poms.
-----Original Message-----
From: nicolas.deloof@gmail.com [mailto:nicolas.deloof@gmail.com] On Behalf Of nicolas de loof
Sent: Thursday, March 20, 2008 4:07 AM
To: Maven Developers List
Subject: Re: [Pre-Vote] release maven 2.0.9
I agree this should be fixed, as there is no <reportingManagement> section
in POM to force the report plugin versions and the <version> element is
optional in <reporting>.
Nico.
2008/3/20, Geoffrey De Smet <ge...@gmail.com>:
>
> The reporting section ignores pluginManagement, which is said to be a
> feature, but IMHO it violates the principle of least suprise and it's a
> bug.
>
> With kind regards,
> Geoffrey De Smet
>
> Jörg Schaible schreef:
> > paulus.benedictus@gmail.com wrote:
> >> nicolas,
> >>
> >> I won't speak for Brian, but I thought his intention was to lock down
> >> plug-ins that only affect the build cycle.
> >
> > Shouldn't the generated reports of a release also be reproducable?
> However, anone noticed that a plugin with a locked version in the
> pluginManagement is not locked if used without version in the report
> section? Bug or feature?
> >
> > - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: 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: [Pre-Vote] release maven 2.0.9
Posted by nicolas de loof <ni...@apache.org>.
I agree this should be fixed, as there is no <reportingManagement> section
in POM to force the report plugin versions and the <version> element is
optional in <reporting>.
Nico.
2008/3/20, Geoffrey De Smet <ge...@gmail.com>:
>
> The reporting section ignores pluginManagement, which is said to be a
> feature, but IMHO it violates the principle of least suprise and it's a
> bug.
>
> With kind regards,
> Geoffrey De Smet
>
> Jörg Schaible schreef:
> > paulus.benedictus@gmail.com wrote:
> >> nicolas,
> >>
> >> I won't speak for Brian, but I thought his intention was to lock down
> >> plug-ins that only affect the build cycle.
> >
> > Shouldn't the generated reports of a release also be reproducable?
> However, anone noticed that a plugin with a locked version in the
> pluginManagement is not locked if used without version in the report
> section? Bug or feature?
> >
> > - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [Pre-Vote] release maven 2.0.9
Posted by Geoffrey De Smet <ge...@gmail.com>.
The reporting section ignores pluginManagement, which is said to be a
feature, but IMHO it violates the principle of least suprise and it's a bug.
With kind regards,
Geoffrey De Smet
Jörg Schaible schreef:
> paulus.benedictus@gmail.com wrote:
>> nicolas,
>>
>> I won't speak for Brian, but I thought his intention was to lock down
>> plug-ins that only affect the build cycle.
>
> Shouldn't the generated reports of a release also be reproducable? However, anone noticed that a plugin with a locked version in the pluginManagement is not locked if used without version in the report section? Bug or feature?
>
> - Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Pre-Vote] release maven 2.0.9
Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
paulus.benedictus@gmail.com wrote:
> nicolas,
>
> I won't speak for Brian, but I thought his intention was to lock down
> plug-ins that only affect the build cycle.
Shouldn't the generated reports of a release also be reproducable? However, anone noticed that a plugin with a locked version in the pluginManagement is not locked if used without version in the report section? Bug or feature?
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Pre-Vote] release maven 2.0.9
Posted by Jason van Zyl <ja...@maven.org>.
Yes, the default build lifecycle not everything.
On 19-Mar-08, at 8:20 AM, Paul Benedict wrote:
> nicolas,
>
> I won't speak for Brian, but I thought his intention was to lock down
> plug-ins that only affect the build cycle.
>
> Paul
>
> On Wed, Mar 19, 2008 at 10:18 AM, nicolas de loof <ni...@apache.org>
> wrote:
>
>> I notice some official maven plugin don't have fixed version in the
>> super-POM :
>>
>> maven-archetype-plugin
>> maven-checkstyle-plugin
>> maven-eclipse-plugin
>> maven-idea-plugin
>> maven-jxr-plugin
>> maven-invoker-plugin
>> maven-one-plugin
>> maven-patch-plugin
>> maven-pmd-plugin
>> maven-projecthelp-plugin
>> maven-remote-resources-plugin
>> maven-repository-plugin
>> maven-shade-plugin
>> maven-scm-plugin
>> maven-stage-plugin
>> maven-verifier-plugin
>> maven-project-info-reports-plugin
>> maven-surefire-report-plugin
>>
>>
>> maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest
>> available.
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Pre-Vote] release maven 2.0.9
Posted by Paul Benedict <pb...@apache.org>.
nicolas,
I won't speak for Brian, but I thought his intention was to lock down
plug-ins that only affect the build cycle.
Paul
On Wed, Mar 19, 2008 at 10:18 AM, nicolas de loof <ni...@apache.org>
wrote:
> I notice some official maven plugin don't have fixed version in the
> super-POM :
>
> maven-archetype-plugin
> maven-checkstyle-plugin
> maven-eclipse-plugin
> maven-idea-plugin
> maven-jxr-plugin
> maven-invoker-plugin
> maven-one-plugin
> maven-patch-plugin
> maven-pmd-plugin
> maven-projecthelp-plugin
> maven-remote-resources-plugin
> maven-repository-plugin
> maven-shade-plugin
> maven-scm-plugin
> maven-stage-plugin
> maven-verifier-plugin
> maven-project-info-reports-plugin
> maven-surefire-report-plugin
>
>
> maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest available.
>
Re: [Pre-Vote] release maven 2.0.9
Posted by nicolas de loof <ni...@apache.org>.
I notice some official maven plugin don't have fixed version in the
super-POM :
maven-archetype-plugin
maven-checkstyle-plugin
maven-eclipse-plugin
maven-idea-plugin
maven-jxr-plugin
maven-invoker-plugin
maven-one-plugin
maven-patch-plugin
maven-pmd-plugin
maven-projecthelp-plugin
maven-remote-resources-plugin
maven-repository-plugin
maven-shade-plugin
maven-scm-plugin
maven-stage-plugin
maven-verifier-plugin
maven-project-info-reports-plugin
maven-surefire-report-plugin
maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest available.
Also maven-install-plugin is not right ordered considering alphabetic order
(not an issue but makes this check more difficult)
2008/3/18, Brian E. Fox <br...@reply.infinity.nu>:
>
> The list of fixes in this release is substantial. See release notes at
> the bottom. High level changes are: locking down the plugins in the
> super pom, new import scope, new toolchain support, native webdav
> support, execution inheritance=false is fixed, plugin dependency
> overrides, errors in transfer won't corrupt the local repo, and
> generally a lot of fixes for artifact resolution and other identified
> regressions from the user list.
>
>
>
> The release is staged at:
>
> http://people.apache.org/~brianf/staging-repository/
>
>
>
> The bundles are here:
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/2.0.9/
>
>
>
> I'll let this staged RC sit for a few days before calling the formal
> vote.
>
>
>
> Release Notes - Maven 2 - Version 2.0.9
>
>
>
>
>
> ** Bug
>
> * [MNG-1412] - dependency sorting in classpath
>
> * [MNG-1914] - Wrong url in error message when using a mirror
>
> * [MNG-2123] - NullPointerException when a dependency uses version
> range and another uses an actual version incompatible with that range
>
> * [MNG-2145] - Plugins' dependencies are not always checked
>
> * [MNG-2178] - incorrect M2_HOME guess in mvn.bat
>
> * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
> profiles section is missing or empty
>
> * [MNG-2339] - ${project.*} are interpreted in the wrong place
>
> * [MNG-2744] - checksum comparison should be case-insensitive
>
> * [MNG-2809] - Can't activate a profile by checking for the presence
> of a file in ${user.home}
>
> * [MNG-2848] - Environment variables in profile activation not
> working
>
> * [MNG-2861] - NullPointerException in DefaultArtifactCollector for
> relocated resolvedArtifacts with different version ranges and available
> versions.
>
> * [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
> there's no mojo in pom.xml
>
> * [MNG-2928] - Null pointer exeception when introducing version
> range [major.minor.build-SNAPSHOT,)
>
> * [MNG-2956] - The documentation refers to system property
> "user.dir" when it should refer to "user.home"
>
> * [MNG-2972] - Ignores version of plugin dependency specified in my
> pom
>
> * [MNG-3086] - NullPointerException in
> ResolutionNode.getTrail(ResolutionNode.java:136)
>
> * [MNG-3099] - Profiles ignored when working with non-projects (such
> as archetype:create)
>
> * [MNG-3111] - Classpath order incorrect
>
> * [MNG-3156] - NullPointerException with mvn dependency:sources
>
> * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
>
> * [MNG-3259] - Regression: Maven drops dependencies in multi-module
> build
>
> * [MNG-3288] - Invalid systemPath allows build to continue--failing
> in later phase.
>
> * [MNG-3296] - mvn.bat looses error code on windows NT type
> platforms
>
> * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
>
> * [MNG-3316] - Barfs at attribues named .*encoding
>
> * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
> with Novell login
>
> * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
> ${pom.build.testSourceDirectory} no longer recognized
>
> * [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
>
> * [MNG-3394] - Plugin versions inherited via <pluginManagement>
> cannot be overriden by <build>.<plugins> section of sub modules
>
> * [MNG-3396] - Managed versions dont affect over constrained ranges
>
> * [MNG-3400] - MavenProject is not extensible
>
> * [MNG-3405] - "Checking for updates from repository" logging should
> not display if WagonManager is offline
>
> * [MNG-3410] - Managed versions in plugins are not considered when
> using them
>
> * [MNG-3415] - Transfer errors cause junk metadata in the local repo
>
> * [MNG-3426] - regression : <dependency> in plugin configuration
> doesn't override plugin classpath
>
> * [MNG-3430] - Toolchain doesn't match Toolchain extensions
>
> * [MNG-3431] - Pom Extensions not supported for Toolchains
>
> * [MNG-3439] - incorrect child dependency selected when parent is
> not selected
>
> * [MNG-3441] - Maven should always retrieve metadata to be updated
> from the deployment repository
>
> * [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
> fails if you use a different local repo
>
> * [MNG-3464] - maven-toolchains missing from final binary.. need to
> update the assembly
>
>
>
> ** Improvement
>
> * [MNG-428] - Japanese message resource
>
> * [MNG-2881] - Improve logging when downloading snapshots in offline
> mode
>
> * [MNG-3119] - Duplicate attached artifacts should not be allowed.
>
> * [MNG-3279] - Support Exception Chaining for MojoFailureException
>
> * [MNG-3318] - ActiveProjectArtifact should have appropriate equals
> and hashCode methods
>
> * [MNG-3331] - Normalize paths to sub modules
>
> * [MNG-3388] - DefaultPluginManager needs to catch LinkageError
>
> * [MNG-3395] - Default core plugin versions in the superpom.
>
> * [MNG-3442] - Add explicit resource bundle for English
>
> * [MNG-3453] - Avoid references to the deprecated expression
> "${project.build.resources}"
>
> * [MNG-3461] - Mirrors should not apply to file:// repositories
>
>
>
> ** New Feature
>
> * [MNG-2664] - Add native support for webdav
>
> * [MNG-3360] - Added the documentation in the Maven release
>
>
>
> ** Task
>
> * [MNG-2883] - Make sure that the network isn't used for snapshots
> in offline mode when legacy repositories are used
>
>
>
>
>
> ** Wish
>
> * [MNG-1491] - Reactor should print out a message if it detects a
> collision of artifact ids
>
>