The Maven team is pleased to announce the release of the Maven Doxia
and Doxia Site Tools version 1.1.2
Doxia is a content generation framework which aims to provide its
users with powerful techniques for generating static and dynamic
content: Doxia can be used in web-based publishing context to generate
static sites, in addition to being incorporated into dynamic content
generation systems like blogs, wikis and content management systems.
Doxia supports markup languages with simple syntaxes. Lightweight
markup languages are used by people who might be expected to read the
document source as well as the rendered output.
http://maven.apache.org/doxia
You should specify the version in your project's plugin configuration:
Release Notes - Maven Doxia - Version 1.1.2
** Bug
* [DOXIA-338] - Section numbering and links
* [DOXIA-343] - FO: links broken if link target contains dot
* [DOXIA-353] - IText sink: Definition Lists are not formatted correctly
* [DOXIA-357] - FO: NoSuchElementException with a table caption
* [DOXIA-359] - Xdoc parser doesnt make the difference for <title/>
* [DOXIA-360] - Unable to specify table cell/row alignment
* [DOXIA-362] - Entities in attribute values are not escaped
* [DOXIA-363] - FO: Nested tables are not allowed
* [DOXIA-364] - Guarantee the state of sinks and parsers impl
* [DOXIA-366] - Wrong TOC when styles
** Improvement
* [DOXIA-358] - avoid to store in memory the full generated FO
document when only table content is needed
Release Notes - Maven Doxia Sitetools - Version 1.1.2
** Bug
* [DOXIASITETOOLS-29] - PathUtils.getRelativePath returns
different results on Windows and Linux
* [DOXIASITETOOLS-35] - wrong model inheritance for text-only
banners (without image)
** Improvement
* [DOXIASITETOOLS-21] - Add Velocity support to DocRenderer
* [DOXIASITETOOLS-33] - Add an option to include or not the TOC
* [DOXIASITETOOLS-36] - add lastModification to DecorationModel to
track last modification time of site.xml
** New Feature
* [DOXIASITETOOLS-7] - site.xml <item target=> attribute no more working
* [DOXIASITETOOLS-31] - Allow images in the menu items of the site.xml
** Task
* [DOXIASITETOOLS-32] - Deployed decoration-1.0.1.xsd
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Ant Tasks,
version 2.1.0
The Maven Ant Tasks allow several features of Maven to be used in an Ant build.
This includes dependency management, reading and writing pom files, and
deployment to a Maven repository. More information is available at the project
site.
http://maven.apache.org/ant-tasks
The current version of the Maven Ant Tasks can be downloaded from the project
downloads page.
http://maven.apache.org/ant-tasks/download.html
Release Notes - Maven Ant Tasks - Version 2.1.0
** Bug
* [MANTTASKS-4] - System scope not working properly in Maven Antlib
* [MANTTASKS-152] - Mvn task omit localRepository param
* [MANTTASKS-153] - Properties defined in Ant are not passed to Maven
* [MANTTASKS-155] - Dependency fileset should set the current ant project
* [MANTTASKS-159] - Wrong credentials used for mirrored repositories
* [MANTTASKS-160] - Wrong metadata files created for mirrored remote
repositories
* [MANTTASKS-167] - Generated ant build file should save version list for
version mapper
** Improvement
* [MANTTASKS-117] - Setting Maven user-properties not possible
* [MANTTASKS-169] - Dependencies "verbose" option should be deprecated in
favor of standard ant verbose option
** New Feature
* [MANTTASKS-151] - Support for artfacts that are 'classified' from birth
* [MANTTASKS-156] - Add feature to dependencies task to write file paths to
a file.
* [MANTTASKS-168] - New task to write a pom file
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-5.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source and binary distributions are already available on
the central Maven repository and various Apache download mirrors and
will be listed soon in our download section once the updated site gets
synced to the live server:
http://maven.apache.org/download.html
A major goal of Maven 3.0 is to be compatible with existing plugins and
projects designed for Maven 2.x. Users interested in testing this alpha
release should have a glance at the compatibility notes for known
differences between Maven 3.0 and Maven 2.x:
http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
If you encounter unexpected problems while using Maven 3.0-alpha-5,
please feel free to contact us via the Maven developer list:
http://maven.apache.org/mail-lists.html
Release Notes - Maven 2 - Version 3.0-alpha-5
** Bug
* [MNG-4450] - [regression] Stub project for missing dependency
POMs is not properly created
* [MNG-4454] - Incomplete <parent> element causes NPE
* [MNG-4459] - [regression] Effective settings as visible to
plugins contain plain text passwords
* [MNG-4461] - [regression] No transfer progress during artifact
deployment
** Improvement
* [MNG-4440] - error message should clearly indicate the module
that failed, and how to continue
* [MNG-4456] - Deprecate fully qualified pathnames in system path
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 1.2.2.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies. See the plugin's site for more
details:
http://maven.apache.org/plugins/maven-shade-plugin/
To use the updated plugin in your projects, you need to add the
following snippet to the plugins or plugin management section of your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>1.2.2</version>
</plugin>
Release Notes - Maven 2.x Shade Plugin - Version 1.2.2
** Bug
* [MSHADE-47] - Shade misses class references stored as strings
during relocation
* [MSHADE-53] - Shade createDependencyReducedPom ignores artifacts
with classifier
* [MSHADE-54] - <finalName> not respected when generating the package
* [MSHADE-60] - [PATCH] maven shade plugin fails if artifact
dependencies contain artifacts that cannot be opened with JarFile class
* [MSHADE-64] - Relocating does not work, when an annotation
references an enum
* [MSHADE-66] - Creation of dependency reduced POM fails for
project with uninstalled local parent using Maven 3
** Improvement
* [MSHADE-58] - Add sample configuration for AppendingTransformer
in docs
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Doxia
Tools shared component, version 1.1
This shared component has some utilities that are useful when
integrating Doxia in Maven, mainly for site generation and report
creation. The main entry point is the SiteTool Plexus component.
http://maven.apache.org/shared/maven-doxia-tools/
Release Notes - Maven Shared Components - Version maven-doxia-tools 1.1
** Bug
* [MSHARED-102] - The modules menu is not inherited to sub-modules
* [MSHARED-116] - If module has no site.xml then the decoration
model is set equal to the parent instead of inheriting from it
* [MSHARED-117] - Parent menu item is not inherited if no url in parent
** Task
* [MSHARED-115] - Upgrade to doxia 1.1.1
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven JAR
Plugin, version 2.3
This plugin provides the capability to build jars. Signing is deprecated
starting with this version. Please use Maven Jarsigner Plugin if you
need to sign JARs.
http://maven.apache.org/plugins/maven-jar-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.3</version>
</plugin>
Release Notes - Maven 2.x JAR Plugin - Version 2.3
** Bug
* [MJAR-28] - Using the jar plugin with addClasspath and snapshots
can create manifest classpath with incorrect jar versions
* [MJAR-105] - Regression: Build fails for an empty main jar with 2.2
* [MJAR-118] - Upgrade maven-archiver dependency to 2.4
** Task
* [MJAR-127] - Deprecate jarsigner related goals in favor of
dedicated maven-jarsigner-plugin
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Changes
Plugin, version 2.2
This plugin is used to inform your users of the changes that have
occured between different releases of your project. The plugin can
extract these changes, either from a changes.xml file or from the JIRA
issue management system, and present them as a report. You also have the
option of creating a release announcement and even sending this via
email to your users.
http://maven.apache.org/plugins/maven-changes-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.2</version>
</plugin>
Release Notes - Maven 2.x Changes Plugin - Version 2.2
** Bug
* [MCHANGES-116] - FileNotFoundException and NullPointerException if
src/changes/changes.xml is missing
* [MCHANGES-143] - Specifying sender email address using
fromDeveloperId is no longer working.
* [MCHANGES-147] - MavenProject object not initialize due to
mispelling into the declaration
* [MCHANGES-156] - An empty table is shown for a <release> which
doesn't have any <action> in it
* [MCHANGES-166] - Problem with issueLinkTemplatePerSystem
* [MCHANGES-185] - Output special characters like < and > in the
JIRA report
** Improvement
* [MCHANGES-177] - Allow specification of report columns in Trac report
* [MCHANGES-178] - Make the url parameter non-required
* [MCHANGES-179] - Improve the announcement template reference
documentation
* [MCHANGES-181] - Add Swedish translation
* [MCHANGES-183] - Add French translations
* [MCHANGES-184] - Add German translation for the Trac report
** New Feature
* [MCHANGES-161] - Add limited properties interpolation
** Task
* [MCHANGES-157] - Update to Doxia 1.0
* [MCHANGES-158] - Document how to use the XML schema for changes.xml
* [MCHANGES-170] - Review the Doxia Sink calls
* [MCHANGES-171] - Fix Modello build warning
* [MCHANGES-180] - Update to Maven Reporting Impl 2.0.4.3
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 2.0-alpha-1.
This harness assists in creating unit or integration tests for Maven
plugins. See the component's site for more details:
http://maven.apache.org/plugin-testing/
This new version of the harness targets Maven 3.0.
Release Notes - Maven 2.x Plugin Testing - Version 2.0-alpha-1
** Bug
* [MPLUGINTESTING-11] - plugin-testing-mvn-3.x branch does not
compile/work with latest maven 3.0-SNAPSHOT
* [MPLUGINTESTING-16] - update to build with latest maven 3.0-SNAPSHOT
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven
Checkstyle Plugin, version 2.4.
This plugin generates a report on violations of code style and
optionally fails the build if violations are detected.
http://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.4</version>
</plugin>
Release Notes - Maven 2.x Checkstyle Plugin - Version 2.4
** Improvement
* [MCHECKSTYLE-105] - Update to Checkstyle 5.0
* [MCHECKSTYLE-122] - Add Portuguese (Brazil) translation
* [MCHECKSTYLE-124] - Add Swedish translation
** Task
* [MCHECKSTYLE-119] - Review the Doxia Sink calls
* [MCHECKSTYLE-120] - Bump to Doxia 1.0
* [MCHECKSTYLE-125] - Update to maven-reporting-impl-2.0.4.3
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-4.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source and binary distributions are already available on
the central Maven repository and various Apache download mirrors and
will be listed soon in our download section once the updated site gets
synced to the live server:
http://maven.apache.org/download.html
A major goal of Maven 3.0 is to be compatible with existing plugins and
projects designed for Maven 2.x. Users interested in testing this alpha
release should have a glance at the compatibility notes for known
differences between Maven 3.0 and Maven 2.x:
http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
If you encounter unexpected problems while using Maven 3.0-alpha-4,
please feel free to contact us via the Maven developer list:
http://maven.apache.org/mail-lists.html
Release Notes - Maven 2 - Version 3.0-alpha-4
** Bug
* [MNG-4361] - [regression] command line option "-update-snapshots"
does not work
* [MNG-4433] - [regression] command line option "-update-snapshots"
does not work for parent POMs
* [MNG-4436] - [regression] Singleton components can get
instantianted multiple times
** Improvement
* [MNG-4439] - apache-maven project should not deploy a source JAR
or JAR, as it is only a distribution module
** Task
* [MNG-3913] - Figure out why MavenEmbedderExampleTest fails on the
grid and reenable when fixed.
* [MNG-4412] - Make legacy entry points to repository system pick
offline mode from session
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-3.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of source and binary distributions are already available on
the central Maven repository and various Apache download mirrors and
will be listed soon in our download section once the updated site gets
synced to the live server:
http://maven.apache.org/download.html
A major goal of Maven 3.0 is to be compatible with existing plugins and
projects designed for Maven 2.x. Users interested in testing this alpha
release should have a glance at the compatibility notes for known
differences between Maven 3.0 and Maven 2.x:
http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
As of this writing, we already know about one regression in Maven
3.0-alpha-3 that prevents the forced update of SNAPSHOT POMs via the
command line flag -U. If you encounter unexpected problems while using
Maven 3.0-alpha-3, please feel free to contact us via the Maven
developer list:
http://maven.apache.org/mail-lists.html
Release Notes - Maven 2 - Version 3.0-alpha-3
** Sub-task
* [MNG-3013] - The plugin manager incorrectly caches plugin
versions between embedder calls
* [MNG-3862] - Remove all plugin configuration manipulation from
the plugin manager
* [MNG-3932] - Remove all mirror, authentication, and proxy
handling out of WagonManager and into a neutral Maven implementation
* [MNG-4163] - Deprecate all methods in MavenProject that relate to
reporting.
* [MNG-4215] - Review and fix hashCode/equals methods of
ArtifactRepository implementations
** Bug
* [MNG-1943] - MavenProject::getParent() returns a MavenProject
that is NOT interpolated
* [MNG-2098] - Artifact resolver incorrectly selects repository
which doesn't contain the selected version
* [MNG-2140] - Mojo in forked lifecycle invoked in reactor build
cannot find reactor dependency
* [MNG-2174] - <pluginManagement><plugins><plugin><dependencies>
do
not propogate to child POM plugins (potentially scoped to only affecting
child POM plugins that live within a <profile>)
* [MNG-2363] - <profile><activation><file><exists/> does not
work
in a multi-project build
* [MNG-2693] - Error executing post-site:
java.util.MissingResourceException: Can't find bundle for base name
site-plugin, locale en
* [MNG-2720] - Multiproject dependencies not accurate for
project.compileClasspathElements when run from root project
* [MNG-3018] - pluginManagement configurations are not honoured
when plugin is silently included
* [MNG-3043] - Allow 'mvn test' to work with test-jar dependencies
in a reactor
* [MNG-3139] - The skin does not exist: Unable to determine the
release version
* [MNG-3260] - 2.1: aggregating plugins in submodules of the
reactor return all projects causing a chicken/egg issue
* [MNG-3265] - maven-model Extension.equals causes NPE when any
field is uninitialized
* [MNG-3281] - Revisit backwards compat of extensions (IT 0114)
* [MNG-3391] - StackOverflowError in DefaultMavenProjectBuilder
* [MNG-3401] - Plugin parameters must be specified outside an
execution block when they are invoked from the command line
* [MNG-3483] - merging managed dependencies should ONLY work when
scope == import explicitly
* [MNG-3543] - readProjectWithDependencies take very long time for
some projects
* [MNG-3567] - pluginManagement from parent POM not used in child
* [MNG-3607] - Class loaders employed by Maven return invalid URLs
to resources
* [MNG-3641] - Lack of error checks on profiles
* [MNG-3683] - [regression] Help plugin does not work
* [MNG-3732] - [regression] project.getActiveProfiles() has not the
same behaviour
* [MNG-3757] - Setting M2_HOME to nothing and running ant delets
contents of the current folder
* [MNG-3803] - [regression] System properties not working any more
* [MNG-3807] - Maven is not interpolatin Properties at plugin
configuration
* [MNG-3814] - Reactor builds fail due to erroneous cycle in
project sorting which does not consider versions
* [MNG-3819] - [regression] Plugins that don't declare dependency
on plexus-utils no longer get plexus-utils:1.1
* [MNG-3836] - [regression] Inherited collection from plugin
configuration is merged with configuration from child whereas child
config should completely override collection
* [MNG-3848] - [regression] Inheritance of project/site/scm URLs
does not take child's relative location to parent into account
* [MNG-3853] - [regression] Distribution Management injected by
profile is not reflected by MavenProject
* [MNG-3872] - Profiles not being activated for relocated POMs
* [MNG-3877] - Reporting output directory not basedir aligned when
queried from MavenProject
* [MNG-3885] - Modules of Maven projects are deployed with
Timestamp during reactor build when uniqueVersion is set to false in
parent profile
* [MNG-3900] - [regression] Properties defined by active profiles
are not used for POM interpolation
* [MNG-3918] - NPE in CLIReportingUtils
* [MNG-3919] - NPE in DefaultLifecycleBindingManager
* [MNG-3925] - [regression] Wrong order of plugin executions after
merge with executions inherted from parent
* [MNG-3927] - [regression] Configuration of custom plugin
execution using default id pollutes configuration of default plugin
executions introduced by packaging
* [MNG-3941] - Execution project is accessible to later mojo executions
* [MNG-3947] - [regression] Configuration of plugin execution with
id "default" pollutes configuration of standalone plugin execution from CLI
* [MNG-3991] - POM validator allows <scope>optional</scope> but it
is not valid.
* [MNG-3995] - Configuration Property Lost In Join of
PluginManagement/Plugin
* [MNG-4008] - [regression] Build filters are collapsed
* [MNG-4009] - [regression] Effects of active profiles from parent
are not inherited by children.
* [MNG-4027] - [regression] Injection of dependencies from profiles
crashes project builder
* [MNG-4034] - [regression] dependency version is not inherited
from parent dependencyManagement
* [MNG-4035] - Cannot find setter nor field in
org.apache.maven.plugin.plugin.metadata.AddPluginArtifactMetadataMojo
for 'extractors'
* [MNG-4036] - [regression] Maven 3.x can't resolve parent POMs
from repositories defined in settings.xml
* [MNG-4040] - Tycho build fails with PluginDescriptor for the
plugin was not found
* [MNG-4041] - embedder returns stale maven project state
* [MNG-4050] - Bootstrap fails since the commons-parent pom has
empty repo URL
* [MNG-4052] - import scope dependencies prefer to download pom
rather than find it in the current project
* [MNG-4053] - [regression] XML attributes in plugin configuration
get duplicated to other elements in combination with plugin management
* [MNG-4055] - wrong error on mvn install in folder without pom.xml
* [MNG-4068] - [regression] Use proper id for mirrored repository
* [MNG-4070] - [regression] Parent POMs cannot be resolved when
their id values are surrounded by whitespace
* [MNG-4072] - [regression] Repositories from inactive profiles are
used for artifact resolution
* [MNG-4078] - [regression] Plugin metaversion RELEASE no longer
resolved
* [MNG-4102] - [regression] Properties used for interpolation of
inherited properties can't be customized by child
* [MNG-4106] - [regression] Interpolation does not use properties
from dominant settings profile if other profile defines same property
* [MNG-4107] - [regression] User settings can't override properties
used for POM interpolation
* [MNG-4109] - When running a plugin, project builder does not pick
up settings profiles
* [MNG-4116] - [regression] Effective POM contains invalid URLs
upon usage of percent-encoded characters
* [MNG-4129] - Execution's inherited is not working as expected.
* [MNG-4172] - Project POM artifact returned as dependency if
project has no dependencies
* [MNG-4180] - [regression] Dependency exclusions are applied globally
* [MNG-4187] - dependency:trunk doesn't work with mvn trunk rev 782332
* [MNG-4190] - same remote repo is referecned multiple times
* [MNG-4191] - separate plugin and artifact repositories
* [MNG-4196] - [regression] Exclusions in project-level plugin
dependencies are ignored
* [MNG-4197] - relocation doesn't work in trunk (rev 784345)
* [MNG-4199] - [regression] Dependency resolution for compile and
runtime scope misses provided&system dependencies
* [MNG-4201] - Custom packaging break in trunk (rev 784628)
* [MNG-4203] - [regression] Dependency exclusions are not applied
transitively
* [MNG-4208] - [regression] CLI properties can't override project
properties during interpolation
* [MNG-4214] - [regression] Parent POMs cannot be resolved from
mirrored repos
* [MNG-4217] - trunk create a directory with %20 in name (trunk rev
787409)
* [MNG-4227] - DefaultArtifactVersion equals implementation does
not handle null
* [MNG-4231] - Snapshots are not checked for updates
* [MNG-4239] - NoSuchMethodError
org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
* [MNG-4245] - can't access protected mirrors with latest
3.0-SNAPSHOT (rev 795227)
* [MNG-4246] - plugin resolution failures during pom-less execution
(like archetype:generate)
* [MNG-4256] - [regression] The gwt-maven-plugin is using
ActiveProjectArtifact to get hold of sources in the reactor
* [MNG-4261] - site plugin doesn't generate reports
* [MNG-4262] - Make-like reactor mode fails to find projects
selected by relative paths with leading dots
* [MNG-4266] - Missing method ArtifactUtils.isSnapshot used in the
release plugin
* [MNG-4269] - [regression] Invocation of just installed plugin on
its plugin project can fail with ComponentLookupException for mojo class
* [MNG-4272] - Error found in code: wrong order of parameters in
createRepository for repo in a profile in settings.xml
* [MNG-4273] - [regression] Internal utility classes of core leak
into plugin realm
* [MNG-4274] - Plugins with an undeclared but transitive dependency
on plexus-utils via a core artifact get wrong version of p-u
* [MNG-4276] - Plugins with indirect dependency on plexus-utils are
stuck with plexus-utils:1.1
* [MNG-4280] - [regression] Direct CLI invocation of goal causes
"default-cli" config to be processed twice, duplicating list values
* [MNG-4281] - remote snapshots are prefered over locally installed
snapshots in maven3 svn rev 800808
* [MNG-4283] - [regression] Parent POM with packaging other than
"pom" is not rejected
* [MNG-4291] - [regression] @requiresOnline mojo annotation is ignored
* [MNG-4304] - [regression] MavenProject.getDependencyArtifacts()
not set
* [MNG-4305] - [regression] ${localRepository.basedir} is not a
proper path
* [MNG-4312] - Magic expressions injected by
PluginParameterExpressionEvalutor conflict with expressions used by
plugins to access system properties
* [MNG-4313] - Plugin descriptor builder ignores deprecation
message for mojo
* [MNG-4314] - [regression] Direct invocation of aggregator plugin
causes plugin to run on each project
* [MNG-4317] - [regression] g:a level metadata is not properly
processed when resolving plugin version
* [MNG-4318] - MavenProject.executionRoot is not set correctly
* [MNG-4320] - [regression] Aggregators invoked from CLI no longer
resolve dependencies for all reactor projects
* [MNG-4321] - [regression] Plugin-level configuration from plugin
management is not applied to goals invoked from CLI
* [MNG-4325] - [regression] Lifecycle overlay configuration of
aggregator mojos is not properly processed when forking reactor
* [MNG-4327] - [regression] Forking mojos that are bound to a
lifecycle phase that gets forked execute multiple times
* [MNG-4328] - [regression] plugin parameters of primitive types
can't be populated from expression
* [MNG-4332] - [regression] Default plugin executions contributed
by packaging execute after executions from plugin management
* [MNG-4334] - maven core caches settings.xml
* [MNG-4335] - [regression]
<settings><offline>true</offline</settings> is not honored
* [MNG-4338] - Unexepceted "Unknown packaging: bundle" error for
plugins with custom lifecycle mapping that defines optional mojos
* [MNG-4341] - [regression] Plugins are not executed in POM order
* [MNG-4342] - [regression] Multiple goals within single execution
with equally named parameter get configured with wrong default values
* [MNG-4343] - maven always checks missing release artifacts
* [MNG-4344] - [regression] Managed executions of plugins
introduced by default lifecycle bindings execute before explicitly
defined plugins
* [MNG-4345] - [regression] Plugin executions contributed by
default lifecycle mapping execute after other plugin executions bound to
the same phase
* [MNG-4348] - [regression] Unnecessary remote repo access for POMs
while execution plugin that does not require dependency resolution
* [MNG-4349] - [regression] Maven hangs in endless loop if POM of
relocated artifact is invalid
* [MNG-4350] - [regression] Multiple goals bound to the same phase
in a lifecycle mapping get executed out of order
* [MNG-4353] - [regression] Plugin dependencies are not downloaded
from repos given in the plugin's POM
* [MNG-4355] - [regression] Extensions without version in the POM
are not resolved to the RELEASE artifact
* [MNG-4356] - [regression] Active component maps with stateful
per-lookup components broken
* [MNG-4357] - [regression] Custom packagings from build extensions
are not reliably loaded during a reactor build
* [MNG-4359] - [regression] Locally reachable parent POMs outside
of reactor are not found during dependency resolution
* [MNG-4360] - [regression] wagon-webdav-jackrabbit doesn't work
with Maven 3.x
* [MNG-4363] - [regression] Dependency artifacts injected by
plugins aren't included in class paths
* [MNG-4365] - XmlPullParserException while parsing XML with
encoded entities within attributes
* [MNG-4378] - Maven wants to create meta data files with invalid
file names
* [MNG-4383] - Uninterpolated expressions should cause an error for
dependency versions
* [MNG-4385] - [regression] Custom lifecycle mappings from build
extension leak into other projects in the reactor without extension
* [MNG-4386] - [regression] Debug logging can't be activated
* [MNG-4387] - [regression] Quiet logging can't be activated
* [MNG-4393] - [regression] Parent POMs resolved from repository
are parsed in strict mode
* [MNG-4396] - [regression] Ant plugin fails with Maven-3
* [MNG-4400] - [regression] Repository order from settings.xml is
not respected during artifact resolution
* [MNG-4401] - [regression] central repository is tried before
explicitly declared repositories during parent POM resolution
* [MNG-4408] - Missing settings.xml is silently ignores
* [MNG-4409] - NPE when reporting command line error for
non-existent option
* [MNG-4410] - [regression] Maven execution does not end after
showing usage help
* [MNG-4411] - [regression] Maven execution does not stop after
showing version
* [MNG-4413] - [regression] Repositories discovered in dependency
POMs are not subject to mirroring
* [MNG-4415] - [regression] Plugins are not properly ordered after
merging with inherited parent plugins
* [MNG-4416] - [regression] Plugins are not properly ordered after
merging with profile plugins
* [MNG-4426] - Some javac errors not shown in console when error
stacktraces are turned on
* [MNG-4427] - Bad error message with duplicate dependencies that
don't declare a version
* [MNG-4429] - [regression] jspc plugin works in Maven 2.2.1, fails
in 3.0
* [MNG-4430] - [regression] Presence of distribution management
status in POM of local project does not cause validation error
** Improvement
* [MNG-2391] - improve validation of POM elements
* [MNG-3402] - MavenArtifactFilterManager needs to not filtering
doxia-sink-api
* [MNG-3631] - Introduce new MavenEmbedder.getPluginConfiguration
method
* [MNG-3714] - Allow specification of the toolchains.xml location
on the command line
* [MNG-3834] - Improve error message when dependency with
classifier is missing version
* [MNG-3951] - Hide drive-relative paths from plugins
* [MNG-3969] - replace maven-ant with mercury-ant in the bootstrap
* [MNG-4005] - Throw Validation Error if pom contains a dependency
with two different versions.
* [MNG-4037] - Include Java home in version information
* [MNG-4048] - Allow to resolve dependencies using version range
from reactor
* [MNG-4057] - Propose checking of plugin artifact when plugin
descriptor cannot be found
* [MNG-4186] - Provide an exact pointer to documentation specific
to each known exception that can occur
* [MNG-4193] - Throw validation error upon multiple repository
declarations with the same id
* [MNG-4224] - maven lifecycle participant
* [MNG-4244] - Allow to select project for make-like reactor by
artifact id
* [MNG-4247] - Displaying which artifacts are downloaded and from
which repo
* [MNG-4292] - Support Enum-type parameters in mojos
* [MNG-4293] - Extend Mojo API to allow resolution of both compile
and runtime dependencies
* [MNG-4296] - allow core extensions configure new classrealms
* [MNG-4298] - Build MavenProject instances incrementally
* [MNG-4368] - DefaultArtifactInstaller should only overwrite files
if timestamp has changed
* [MNG-4390] - Make parsing of settings.xml lenient with respect to
unrecognized tags
* [MNG-4402] - Improve duplicated modules error
* [MNG-4404] - Throw validation error upon duplicate profile id
* [MNG-4405] - Uninterpolated expressions should cause an error for
plugin versions
* [MNG-4421] - Warn regarding old-style references when used in a
project build
* [MNG-4423] - Allow to query session data via plugin parameter
expressions
** New Feature
* [MNG-553] - Secure Storage of Server Passwords
* [MNG-3760] - Support property ${baseurl} to get RFC-compliant URL
of project base directory
* [MNG-4033] - Introduce password encryption to the trunk
* [MNG-4331] - Add new mojo annotation
@requiresDependencyCollection to grab dependency tree without files
* [MNG-4367] - Consider layout for mirror selection
* [MNG-4381] - Allow extension plugins to contribute non-core
components to be reused by other plugins
* [MNG-4398] - Provide an extension point to track artifact
additions to the local repository
** Task
* [MNG-2387] - <active> on <proxy> in settings is misleading
* [MNG-2765] - Refactor DefaultPluginManager
* [MNG-2766] - Refactor DefaultLifecycleExecutor
* [MNG-3850] - Integrate new Profile Activators
* [MNG-3901] - Merge all project building code into a single component
* [MNG-3903] - Create a Maven specific abstraction for Artifact use
within Maven
* [MNG-3935] - Get the Maven Integration Testing Hudson plugin
installed on the grid
* [MNG-4059] - Remove support for non-unique SNAPSHOT deployments
* [MNG-4060] - Remove support for profiles.xml
* [MNG-4062] - Evaluate possibility to cache parents during multi
module build
* [MNG-4069] - Remove support for plugin metaversion LATEST
* [MNG-4169] - Remove invocation of
maven-plugin-plugin:updatePluginRegistry from default lifecycle bindings
* [MNG-4204] - Remove support for legacy style repositories
* [MNG-4205] - Remove support for plugin metaversions RELEASE and
LATEST
* [MNG-4206] - Prefer RELEASE over LATEST when resolving plugin
versions
* [MNG-4216] - Remove all direct usage of DefaultArtifactRepository
* [MNG-4221] - Push all repository/artifact related code into a
legacy module and create a backward compat layer for external consumers
* [MNG-4259] - Create a new name for the current PluginManager and
create a backward compatible PluginManager implementation in
maven-compat which delegates to the new implementation
* [MNG-4260] - Remove old-school reactor mode
* [MNG-4277] - Remove core artifacts from ${plugin.artifacts}
* [MNG-4287] - Make ToolchainManagerPrivate session-aware
** Wish
* [MNG-4056] - Relax resolution of active project artifacts from
the reactor with regard to artifact type
* [MNG-4425] - Restore support for resume-from (-rf flag)
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.2.
This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build output) that
are the subject of an ASF release vote.
The new version of the descriptor fixes the erroneous exclusion of some
file types like IDE files from the source archive even if those files
are located in the src/ directory tree of a project, i.e. denote actual
project sources (e.g. required for unit testing).
http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/
This new descriptor will eventually be incorporated into the Apache
Parent POM. If you want to try out the source-release descriptor in the
meantime, you can include a configuration like the following:
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>
<dependencies>
<dependency>
<groupId>org.apache.apache.resources</groupId>
<artifactId>apache-source-release-assembly-descriptor</artifactId>
<version>1.0.2</version>
</dependency>
<dependency>
<!-- NOTE: The fix for PLXUTILS-120 is crucial for the new
assembly descriptor -->
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-utils</artifactId>
<version>2.0.1</version>
</dependency>
</dependencies>
<executions>
<execution>
<id>source-release</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>source-release</descriptorRef>
</descriptorRefs>
<tarLongFileMode>gnu</tarLongFileMode>
<runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Enjoy,
The Maven Team
The Maven team is pleased to announce the release of the Maven Ant
Plugin, version 2.3.
This plugin generates build files for Ant from a POM. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-ant-plugin/
To use the updated plugin in your projects, you need to add the
following snippet to the plugins or plugin management section of your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ant-plugin</artifactId>
<version>2.3</version>
</plugin>
Release Notes - Maven 2.x Ant Plugin - Version 2.3
** Bug
* [MANT-60] - Generated "package" task for EAR/WAR is missing
transitive dependencies
** Improvement
* [MANT-61] - Classpath generation should honour system-scope.
** New Feature
* [MANT-59] - Add support for generating build files when
<packaging>bundle</bundle>
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven
Reporting Impl, version 2.0.4.3.
This shared component contains abstract classes to manage report generation..
http://maven.apache.org/shared/maven-reporting-impl/
Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.4.3
** Bug
* [MSHARED-120] - No single report generated with latest
maven-reporting-impl
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of Maven Runtime, version 1.0-alpha-2. Maven Runtime allows introspection of Maven project metadata at runtime. http://maven.apache.org/shared/maven-runtime/ You should specify the dependency in your project's POM: <dependency> <groupId>org.apache.maven.shared</groupId> <artifactId>maven-runtime</artifactId> <version>1.0-alpha-2</version> </dependency> Release Notes - Maven Runtime - Version 1.0-alpha-2 - Added support for introspecting URLs to MavenRuntime - Added url to parsing exception messages Enjoy, -The Maven team
The Maven team is pleased to announce the release of the Maven Toolchains Plugin, version 1.0 This plugin allows sharing configuration across plugins. For example to make sure the plugins like compiler, surefire, javadoc, webstart etc. all use the same JDK for execution. http://maven.apache.org/plugins/maven-toolchains-plugin/ You should specify the version in your project's plugin configuration: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-toolchains-plugin</artifactId> <version>1.0</version> </plugin> Release Notes - Maven 2.x Toolchains Plugin - Version 1.0 Enjoy, -The Maven team
The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.1.
This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build output) that
are the subject of an ASF release vote.
The new version of the descriptor fixes the erroneous inclusion of some
build output in the source archive. Please see
http://jira.codehaus.org/browse/MASSEMBLY-446 for more details on the issue.
http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/
This assembly descriptor should be coming to a parent POM near you, and
should eventually be an automatic part of every ASF release. For now, it
has been configured into the release process for Maven projects that
inherit from maven-parent version 14 (also recently released). If you
want to try out the source-release descriptor in the meantime, you can
include a configuration like the following:
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>
<dependencies>
<dependency>
<groupId>org.apache.apache.resources</groupId>
<artifactId>apache-source-release-assembly-descriptor</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<!-- NOTE: The fix for PLXUTILS-120 is crucial for the new
assembly descriptor -->
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-utils</artifactId>
<version>2.0.1</version>
</dependency>
</dependencies>
<executions>
<execution>
<id>source-release</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>source-release</descriptorRef>
</descriptorRefs>
<tarLongFileMode>gnu</tarLongFileMode>
<runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Enjoy,
The Maven Team
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.5
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-invoker-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-invoker-plugin</artifactId>
<version>1.5</version>
</plugin>
Release Notes - Maven 2.x Invoker Plugin - Version 1.5
** New Feature
* [MINVOKER-95] - Add a selector script to allow for flexible
skipping specific projects
* [MINVOKER-96] - Add a selector for the Maven Version
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.6.1
This plugin uses the javadoc tool for generating javadocs for the
specified project.
http://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.6.1</version>
</plugin>
Release Notes - Maven 2.x Javadoc Plugin - Version 2.6.1
** Bug
* [MJAVADOC-244] - Javadoc plugin: java files under
src/main/javadoc and doc-files directory are being compiled
* [MJAVADOC-246] - ExceptionInInitializerError with
maven-site-plugin:2.1-SNAPSHOT and mvn > 2.1
* [MJAVADOC-251] - Configuration of javadoc:javadoc fails with NPE
upon disadvantageous order of config injection
* [MJAVADOC-252] - javadoc link : nonproxyhosts not used
* [MJAVADOC-257] - maven-javadoc-plugin 2.5, 2.6 and mojo: Error
extracting plugin descriptor
* [MJAVADOC-259] - Resource copying from javadoc dir is incomplete
* [MJAVADOC-262] - Parameters like sourcepath depend on system
path separator (colon/semicolon)
* [MJAVADOC-268] - performance problem in
AbstractJavadocMojo.getModulesLinks()
** Improvement
* [MJAVADOC-258] - Grouping example could show multiple packages per group
* [MJAVADOC-266] - META-INF directory copied from resource artifacts
* [MJAVADOC-267] - Allow changing the reportOutputDirectory from
the commandline
** Task
* [MJAVADOC-248] - Site 'Usage' page references 2.5 version of m-javadoc-p
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.4
This new release brings compatibility for Java EE 6 and a few bug fixes.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.4</version>
</plugin>
Release Notes - Maven 2.x EAR Plugin - Version 2.4
** Bug
* [MEAR-75] - Incorrect file name in class path (in manifest) if
specifying different bundleFileName for module
* [MEAR-103] - Filtered MANIFEST not added to generated EAR
* [MEAR-104] - wrong jboss-app.xml
* [MEAR-105] - Unable to set some properties for jboss-app.xml
** New Feature
* [MEAR-112] - support for java ee 6 missing
Enjoy,
-The Maven team
Hi, The Maven team is pleased to announce the release of the Maven Source Plugin, version 2.1.1 The Source Plugin creates a jar archive of the source files of the current project. http://maven.apache.org/plugins/maven-source-plugin/ You should specify the version in your project's plugin configuration: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <version>2.1.1</version> </plugin> Release Notes - Maven 2.x Souce Plugin - Version 2.1.1 ** Bugs fixed : * [MSOURCES-44] - If project doesn't contain sources (contains only test sources) source:jar will fail * [MSOURCES-47] - test-jar goal fails if no source files exist Enjoy, -The Maven team # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.5.1.
This plugin assists authors of Maven plugins in the creation of a plugin
descriptor and documentation by scanning the plugin sources for mojo
annotations. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-plugin-plugin/
To use the updated plugin in your projects, you need to add the
following snippet to the plugins or plugin management section of your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-plugin-plugin</artifactId>
<version>2.5.1</version>
</plugin>
Release Notes - Maven 2.x Plugin Tools - Version 2.5.1
** Bug
* [MPLUGIN-148] - PluginXdocGenerator generates poorly formed
output when default values contain XML
* [MPLUGIN-149] - ParseException with annotation @XmlType in
JavaDocBuilder
* [MPLUGIN-151] - ParseException on enum members with annotations
that have values
* [MPLUGIN-152] - QDox choking on some generics
* [MPLUGIN-161] - plugin:xdoc generates an incomplete description
about the execution of another plugin goal
** Task
* [MPLUGIN-150] - Update to QDox 1.9.2
* [MPLUGIN-156] - Stabilize ordering of configuration and
requirements in generated plugin descriptor
* [MPLUGIN-157] - Review the Doxia Sink calls
* [MPLUGIN-158] - Bump to Doxia 1.0
* [MPLUGIN-162] - Update to QDox 1.10
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.3
This plugin assists the user in creating archived bundles that are
designed to meet all requirements for upload to the central Maven
repository.
http://maven.apache.org/plugins/maven-repository-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-repository-plugin</artifactId>
<version>2.3</version>
</plugin>
Release Notes - Maven 2.x Repository Plugin - Version 2.3
** Improvement
* [MREPOSITORY-19] - Require SCM information to help tooling for
project materialization from the repository
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Resources
Plugin, version 2.4.1
This plugin filters non-Java resource files, replacing expressions with
values from the POM or any of the filtering properties files you choose
to configure.
http://maven.apache.org/plugins/maven-resources-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>2.4.1</version>
</plugin>
Release Notes - Maven 2.x Resources Plugin - Version 2.4.1
** Bug
* [MRESOURCES-105] - Custom Delimiters does not work as expected -
NPE with ${*} and comments in property file does break replacement
* [MRESOURCES-106] - Plugin does not respect escapeWindowsPaths
default-value
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.2.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant to supercede the existing jar:sign and
jar:sign-verify goals from the Maven Jar Plugin which will be deprecated
in a future release.
To use the updated plugin in your projects, you need to add the
following snippet to the plugins or plugin management section of your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<version>1.2</version>
<executions>
...
</executions>
</plugin>
Release Notes - Maven 2.x Jar Signer Plugin - Version 1.2
** New Feature
* [MJARSIGNER-8] - Allow to exclude specific attachments from
signing/verification
** Wish
* [MJARSIGNER-7] - jarsigner plugin to support all "types" of zip files
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.4.
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-invoker-plugin/
To use the updated plugin in your projects, you need to add the
the following snippet to the plugins or plugin management section of
your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-invoker-plugin</artifactId>
<version>1.4</version>
</plugin>
Release Notes - Maven 2.x Invoker Plugin - Version 1.4
** Bug
* [MINVOKER-69] - Filter token "basedir" no longer interpolated
* [MINVOKER-70] - invoker:install does not properly handle
versioned dependencies
* [MINVOKER-71] - Usage of <setupIncludes> can result in duplicate
project invocation
* [MINVOKER-78] - Throwing subclasses of java.lang.Error from hook
script aborts main build with "FATAL ERROR"
* [MINVOKER-84] - Staging of snapshot dependencies is incomplete
* [MINVOKER-88] - Staging of existing artifacts from the local
repository triggers transformations on them
* [MINVOKER-93] - Filtering all POMs that are relevant to the
forked build needs to consider child modules added by profiles
** Improvement
* [MINVOKER-68] - Enable accessibility for non-public members from
BeanShell scripts
* [MINVOKER-73] - Support filter token @baseurl@
* [MINVOKER-75] - Trigger further builds upon any indexed invoker
property
* [MINVOKER-76] - Have invoker:run generate report files to allow
reporting on the results of running invoker
* [MINVOKER-92] - Add support for show version option (
-V,--show-version)
** New Feature
* [MINVOKER-72] - Allow to configure network mode for sub builds
* [MINVOKER-74] - Allow to specify alternative POMs during
multi-module builds
* [MINVOKER-77] - Add a invoker report mojo which display invoker
its result
* [MINVOKER-79] - Allow to easily pass data from the pre-build hook
script to the post-build hook script
* [MINVOKER-81] - provide a flag to skip the execution of all
invoker steps
* [MINVOKER-83] - Allow to configure different system properties
for multi-invocation builds
* [MINVOKER-91] - Decouple test execution from build failure
* [MINVOKER-94] - Allow to skip projects based on JRE version or OS
family
** Wish
* [MINVOKER-85] - Don't treat null return value from hook scripts
as error
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.4.
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
http://maven.apache.org/plugins/maven-invoker-plugin/
To use the updated plugin in your projects, you need to add the
the following snippet to the plugins or plugin management section of
your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-invoker-plugin</artifactId>
<version>1.4</version>
</plugin>
Release Notes - Maven 2.x Invoker Plugin - Version 1.4
** Bug
* [MINVOKER-69] - Filter token "basedir" no longer interpolated
* [MINVOKER-70] - invoker:install does not properly handle
versioned dependencies
* [MINVOKER-71] - Usage of <setupIncludes> can result in duplicate
project invocation
* [MINVOKER-78] - Throwing subclasses of java.lang.Error from hook
script aborts main build with "FATAL ERROR"
* [MINVOKER-84] - Staging of snapshot dependencies is incomplete
* [MINVOKER-88] - Staging of existing artifacts from the local
repository triggers transformations on them
* [MINVOKER-93] - Filtering all POMs that are relevant to the
forked build needs to consider child modules added by profiles
** Improvement
* [MINVOKER-68] - Enable accessibility for non-public members from
BeanShell scripts
* [MINVOKER-73] - Support filter token @baseurl@
* [MINVOKER-75] - Trigger further builds upon any indexed invoker
property
* [MINVOKER-76] - Have invoker:run generate report files to allow
reporting on the results of running invoker
* [MINVOKER-92] - Add support for show version option (
-V,--show-version)
** New Feature
* [MINVOKER-72] - Allow to configure network mode for sub builds
* [MINVOKER-74] - Allow to specify alternative POMs during
multi-module builds
* [MINVOKER-77] - Add a invoker report mojo which display invoker
its result
* [MINVOKER-79] - Allow to easily pass data from the pre-build hook
script to the post-build hook script
* [MINVOKER-81] - provide a flag to skip the execution of all
invoker steps
* [MINVOKER-83] - Allow to configure different system properties
for multi-invocation builds
* [MINVOKER-91] - Decouple test execution from build failure
* [MINVOKER-94] - Allow to skip projects based on JRE version or OS
family
** Wish
* [MINVOKER-85] - Don't treat null return value from hook scripts
as error
Enjoy,
-The Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
The Maven team is pleased to announce the release of the Maven Invoker,
version 2.0.11.
This component allows to programmatically invoke Maven. See the
component's site for more details:
http://maven.apache.org/shared/maven-invoker/
To use this component in your projects, add the following to the
dependency section of your POM:
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-invoker</artifactId>
<version>2.0.11</version>
</dependency>
Release Notes - Maven Invoker 2.0.11
** Improvement
* [MSHARED-123] - Add support for show version option (
-V,--show-version)
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Remote
Resources Plugin, version 1.1
This plugin uses configurable sets of template files stored in the Maven
repository, combined with project and dependency POM information, to
generate files such as DEPENDENCIES or LICENSE statements that are
specific to your project.
http://maven.apache.org/plugins/maven-remote-resources-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-remote-resources-plugin</artifactId>
<version>1.1</version>
</plugin>
Release Notes - Maven 2.x Remote Resources Plugin - Version 1.1
** Bug
* [MRRESOURCES-11] - Resource filtering for overridden resources
* [MRRESOURCES-35] - ClassCastException
* [MRRESOURCES-37] - embedded error with
maven-remote-resources-plugin; maven build order?
* [MRRESOURCES-38] - Remove inadvertent dependency on
MavenReportException in maven-reporting-api
* [MRRESOURCES-39] - Unnecessary fondness for inceptionDate
** Improvement
* [MRRESOURCES-31] - Add an "alternative" apache-jar-resource-bundle
** New Feature
* [MRRESOURCES-36] - ${project.build.sourceEncoding} not honoured.
* [MRRESOURCES-41] - add support for multi-module dependencies
listing and other top-of-tree calculations on sub-modules
* [MRRESOURCES-43] - Add ability to specify artifacts to search for
supplementalModels
** Task
* [MRRESOURCES-42] - Incorporate fix for PLXCOMP-145: problem with
JarResourceLoader.initialize() never being called
* [MRRESOURCES-44] - Document usage of runOnlyAtExecutionRoot and
supplemental model features.
* [MRRESOURCES-45] - Stage releases for dependencies that have changed
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Artifact
Resolver, version 1.0
This is a shared library that aims to simplify as much as possible the
task of resolving dependency artifacts for one or more projects
(MavenProject instances) all at once.
http://maven.apache.org/shared/maven-artifact-resolver/
To use the resolver library, add the following to your POM's
dependencies section:
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-artifact-resolver</artifactId>
<version>1.0</version>
</dependency>
Release Notes - Maven Shared Components - Version
maven-artifact-resolver-1.0
** Improvement
* [MSHARED-127] - Consider all projects in the reactor AND projects
in the specified collection when dealing with
MultipleArtifactsNotFoundException
** New Feature
* [MSHARED-126] - Create shared api to resolve project dependencies
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Verifier,
version 1.2
This is a shared library for use in testing various Maven components. It
allows the user to execute Maven builds as part of the testing process,
with methods supporting test preparation and assertion of results.
http://maven.apache.org/shared/maven-verifier/
To use the verifier, add the following to your POM's dependencies section:
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-verifier</artifactId>
<version>1.2</version>
<scope>test</scope>
</dependency>
Release Notes - Maven Shared Components - Version maven-verifier 1.2
** Bug
* [MSHARED-73] - Verifier doesn't throw VerificationException upon
non-zero exit code of mvn.bat on Windows
* [MSHARED-76] - Verifier executeGoal method is OS-dependent in
case of failure
** Improvement
* [MSHARED-72] - Use current local repo for forked Maven
invocations by default
** New Feature
* [MSHARED-75] - Add convenience method to clean (target) directory
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Resources
Plugin, version 2.4.
The Resources Plugin provides support for copying and filtering files in
the standard resource locations in a Maven build (configured using the
project/build/resources and project/build/testResources sections in the
POM).
It also provides similar support for additional, ad-hoc resource
definitions using the copy-resoures mojo.
http://maven.apache.org/plugins/maven-resources-plugin/
You should specify this version in your project's plugin configuration:
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.4</version>
</plugin>
Release Notes - Maven 2.x Resources Plugin - Version 2.4
** Bug
* [MRESOURCES-44] - ${settings.localRepository} is not expanded by
resource filtering
* [MRESOURCES-48] - Failed to copy full contents from
* [MRESOURCES-77] - Filters for copy-resources goal in plugin
configuration section are ignored
* [MRESOURCES-78] - change in @ translation behavior in
maven-resources-plugin 2.3
* [MRESOURCES-79] - <resources> are filtered by test filters
* [MRESOURCES-81] - 2.3 escapes characters when filtering properties
** New Feature
* [MRESOURCES-60] - delimiter configuration
Enjoy,
The Maven team
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
The Maven team is pleased to announce the release of Maven Filtering,
version 1.0-beta-3.
Maven Filtering is an API that allows plugin developers to filter
text-based resources using values supplied by a MavenProject instance, a
MavenSession instance, and an arbitrary set of properties files.
Filtering based on MavenProject values aims to replicate support for
POM-interpolation expressions, while filtering based on the MavenSession
aims to support filtering of system properties and command-line
properties used to execute Maven.
http://maven.apache.org/shared/maven-filtering/
To use this API, you should add the following dependency to your project:
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-filtering</artifactId>
<version>1.0-beta-3</version>
</dependency>
Release Notes - Maven Shared Components - Version maven-filtering-1.0-beta-4
** Bug
* [MSHARED-121] - FilteringUtils.escapeWindowsPath doesn't handle
paths that leave out the drive letter.
** Improvement
* [MSHARED-78] - FilteringUtils escapeWindowsPath() doesn't work on
Windows
Enjoy,
The Maven Team
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.1.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant to supercede the existing jar:sign and
jar:sign-verify goals from the Maven Jar Plugin which will be deprecated
in a future release.
To use the updated plugin in your projects, you need to add the
the following plugin configuration to your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<version>1.1</version>
<executions>
...
</executions>
</plugin>
Release Notes - Maven 2.x Jar Signer Plugin - Version 1.1
** New Feature
* [MJARSIGNER-5] - Allow to unsign JARs before re-signing
* [MJARSIGNER-6] - Allow batch signing of multiple JARs
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of Apache Maven,
version 2.2.1
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads are available here:
http://maven.apache.org/download.html
Release notes are available at (they are also included below):
http://maven.apache.org/release-notes.html
---
Release Notes - Maven 2 - Version 2.2.1
** Bug
* [MNG-3265] - maven-model Extension.equals causes NPE when any
field is uninitialized
* [MNG-3506] - Custom ArtifactHandler not resolved for project when
an additional plugin with extensions is defined in parent pom
* [MNG-3753] - ArtifactResolverDiagnoser.diagnose() fails with NPE
if nested IOException has no detail message
* [MNG-4189] - Maven not picking up specific timestamped version
dependency when a later timestamped version was downloaded and already
present in the local repository
* [MNG-4218] - NPE in AbstractArtifactResolutionException if
DefaultArtifactResolver.resolveTransitively is interrupted
* [MNG-4228] - [regression] Authorization failed: Not authorized by
proxy.
* [MNG-4235] - [regression] Maven 2.2.0 produces invalid checksums
during deployment to secured HTTP repo
* [MNG-4236] - [regression] http wagon uploads files twice with
Maven 2.2.0 when preemptive auth is disabled (default setting)
* [MNG-4238] - Custom ArtifactHandler provided by build extension
isn't used for project artifact
* [MNG-4240] - Direct dependencies with scope == provided will not
have their transitive dependencies resolved for compiling and testing
* [MNG-4270] - ArtifactHandler, LifecycleMapping from plugin
dependency is not used when plugin extensions are enabled
* [MNG-4275] - [regression] Direct relocations no longer log at
WARNING level : MNG-3380 conflicts with MNG-1689
** Improvement
* [MNG-4254] - Support selection of wagon implementation for a
particular protocol
* [MNG-4279] - wagon provider selection should fail gracefully and
use protocol for roleHint if protocol-provider roleHint isn't available.
** Task
* [MNG-4290] - Update guide-http-settings to reflect the fact that
sun-based http has been restored as the default for the http/s wagons.
Enjoy,
-The Maven team
Re-sending, I used the wrong from address...
---
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.2
This plugin simplifies the task of creating upload bundles for adding
artifacts to Maven's central repository.
http://maven.apache.org/plugins/maven-repository-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-repository-plugin</artifactId>
<version>2.2</version>
</plugin>
Release Notes - Maven 2.x Repository Plugin - Version 2.2
** Improvement
* [MREPOSITORY-18] - Repository bundles don't include .asc files or
attached artifacts other than sources and javadocs
** New Feature
* [MREPOSITORY-3] - Please add support for multi-module projects in
repository:bundle-create mojo
Enjoy,
-The Maven team
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.6.
The Maven Javadoc Plugin is a plugin that uses the javadoc tool for
generating javadocs for the specified project.
http://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.6</version>
</plugin>
Release Notes - Maven 2.x Javadoc Plugin - Version 2.6
** Sub-task
* [MJAVADOC-239] - Helpfile loaded from classpath
** Bug
* [MJAVADOC-181] - Javadoc report not generated for multi-module
project if run from parent level.
* [MJAVADOC-215] - warning proxyHost' is deprecated since 2.4
* [MJAVADOC-219] - skip parameter is ignored in aggregate goal
* [MJAVADOC-220] - ArrayIndexOutOfBoundsException in
JavadocUtil.getIncludedFiles
* [MJAVADOC-230] - aggregate report requires to have
aggregate=true configuration parameter
* [MJAVADOC-231] - tagletpath does not seem to work
* [MJAVADOC-232] - copied doc-files folder contains svn meta files
* [MJAVADOC-238] - No timeout set for URLConnection which can
cause build to get stuck
** Improvement
* [MJAVADOC-216] - Stylesheet file loaded from classpath
* [MJAVADOC-222] - Documentation Issues
* [MJAVADOC-225] - The plugin should be able to generate a jar of
the aggregated javadoc
* [MJAVADOC-226] - Add a new goal to fix Javadoc tags
* [MJAVADOC-240] - Add default Javadoc link depending the values
of maven-compiler-plugin configuration
** New Feature
* [MJAVADOC-97] - enable internal/external dependency references as links
** Task
* [MJAVADOC-217] - Update "Aggregating Javadocs" example
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Reporting
Implementation, version 2.0.4.2
This shared component contains abstract classes to manage report generation.
http://maven.apache.org/shared/maven-reporting-impl/
You should specify the version in your project's dependency configuration:
<dependency>
<groupId>org.apache.maven.reporting</groupId>
<artifactId>maven-reporting-impl</artifactId>
<version>2.0.4.2</version>
</dependency>
Release Notes - Maven Shared Components - Version maven-reporting-impl
2.0.4.2
** Improvement
* [MSHARED-108] - Add an ASF-compliant source release assembly
** Task
* [MSHARED-106] - Update to Doxia 1.0
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.1.2
The Maven Project Info Reports plugin is used to generate reports
information about the project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.1.2</version>
</plugin>
Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.1.2
** Bug
* [MPIR-136] - French properties file reference inexistent unicode char
* [MPIR-160] - Dependency report ignores local repository and always
re-fetches artifacts from remote repos
* [MPIR-162] - Grammar incorrect for empty Notifiers section
** Improvement
* [MPIR-155] - Spanish Translation for maven-reports-plugin
* [MPIR-165] - Add an ASF-compliant source release assembly
** Task
* [MPIR-138] - Complet Polish translation
* [MPIR-152] - Update to Doxia 1.0
* [MPIR-153] - Update to maven-doxia-tools 1.0.2
* [MPIR-164] - Complete the German translation
Enjoy,
-The Maven team
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.0.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
The new plugin is meant to supercede the existing jar:sign and
jar:sign-verify goals from the Maven Jar Plugin which will be deprecated
in a future release.
To use the new plugin in your projects, you need to add the
the following plugin configuration to your POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<version>1.0</version>
<executions>
...
</executions>
</plugin>
Release Notes - Maven 2.x Jar Signer Plugin - Version 1.0
(none - initial release)
Enjoy,
-The Maven team