Nabble - Maven Announcements

Maven Help Plugin 2.1 Released

2008-09-04T09:05:09Z

The Maven team is pleased to announce the release of the Maven Help
Plugin, version 2.1

The Maven Help plugin provides goals aimed at helping to make sense
out of the build environment. It includes the ability to view the
effective POM and settings files, after inheritance and active
profiles have been applied, as well as a describe a particular plugin
goal to give usage information.

http://maven.apache.org/plugins/maven-help-plugin/

You should specify the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-help-plugin</artifactId>
<version>2.1</version>
</plugin>

Release Notes - Maven 2.x Help Plugin - Version 2.1

** Bug
* [MPH-42] - Active profiles recursively growing
* [MPH-49] - help:describe no-arg error doesn't mention "cmd"
* [MPH-50] - "mvn help:describe -Dcmd=compiler:compile" describes
entire plugin, not the specific mojo
* [MPH-51] - "help:help -Ddetail" looks better than "help:describe
-Dplugin=help -Dfull"
* [MPH-52] - help:describe never shows "Default Value"

** Improvement
* [MPH-15] - help:describe should accept plugin prefix or prefix:goal
* [MPH-26] - New goal help:help to provide help on how to use
helper plugins in maven
* [MPH-29] - help:describe should be way more helpful when no
arguments are provided
* [MPH-32] - "medium" mode should be the default for help:describe
* [MPH-33] - Help plugin should refer to "goal" not "mojo"
* [MPH-35] - Make -Dfull more discoverable by suggesting it
* [MPH-37] - help:effective-pom - sort the properties list
* [MPH-40] - help:effective-pom emits invalid XML to output file
* [MPH-44] - Hide passwords for effective-settings
* [MPH-46] - Improve the output of help:describe
* [MPH-54] - -Dhelp:describe -Ddetail should not show component requirements

** New Feature
* [MPH-4] - add mojo to projecthelp to describe supported plugin
parameter expressions
* [MPH-12] - Create a Mojo to list all Profiles for a Project
(even those loaded from an external profiles.xml)
* [MPH-28] - New goal to list platform details
* [MPH-30] - help:describe should accept "cmd" argument
* [MPH-47] - Add a new goal to evaluate Maven expressions given by a user

** Task
* [MPH-43] - Create an abstract Help Mojo with output parameter
* [MPH-48] - Review dependencies

Enjoy,

-The Maven team

Maven Dependency Tree 1.2 Released

2008-09-02T07:45:39Z

The Maven team is pleased to announce the release of Maven Dependency
Tree, version 1.2

This component constructs a tree model of a Maven project's dependencies.

http://maven.apache.org/shared/maven-dependency-tree/

You should specify the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-dependency-tree</artifactId>
<version>1.2</version>
</plugin>

Release Notes - Maven Shared Components - Version maven-dependency-tree 1.2

** Improvement
* [MSHARED-5] - Track selectVersionFromRange event in dependency tree nodes

** Various other bug fixes

Enjoy,

-The Maven team

Maven Invoker 2.0.10 Released

2008-08-27T12:50:17Z

The Maven team is pleased to announce the release of the Maven Invoker,
version 2.0.10

This shared component fires up a Maven build in a new JVM.

http://maven.apache.org/shared/maven-invoker/

Release Notes - Maven Shared Components - Version maven-invoker 2.0.10

** New Feature
* [MSHARED-54] - Invoker should provide support for "activateReactor"

Enjoy,

-The Maven team

Maven SCM 1.1 Released

2008-08-27T03:02:27Z

Hi,
The Maven team is pleased to announce the release of the Maven SCM , version 1.1.
http://maven.apache.org/scm
This version includes two new scm providers : AccuRev and Git.

Release Notes - Maven SCM - Version 1.1

** Sub-task
* [SCM-401] - Fix parseHostAndPort() for Bazaar too

** Bug
* [SCM-314] - BazaarScmProviderRepository doesn't work with file URL on Windows
* [SCM-320] - svn: error: cannot set LC_ALL locale
* [SCM-321] - bootstrap does duplicate checkout
* [SCM-323] - generateReleasePoms fails after first release:prepare
* [SCM-331] - bug found in StarteamUpdateCommand when doing a delete-local when a (view)label is used
* [SCM-334] - Faulty svn commandline is generated for passwords containing special chars
* [SCM-338] - NullPointerException when using -DvssDirectory to set ss.exe path
* [SCM-341] - tag is not required for an scm:tag operation
* [SCM-351] - generated client spec name fails if there is a space or tilde in directory name
* [SCM-355] - CVS provider with SSPI transport does not support port number in url
* [SCM-356] - clearcase implementation does not allow id of more than 8 characters.
* [SCM-363] - Perforce Provider ignores p4 errors from stderr
* [SCM-364] - NPE in StarteamChangeLogCommand
* [SCM-374] - maven-scm-providers-git is missing some testdata
* [SCM-379] - SCM URL with query transformed incorrectly on release:prepare
* [SCM-380] - CvsStatusConsumer cannot be used for CvsJavaListCommand and CvsExeListCommand
* [SCM-382] - cleanup dependencies in maven-scm-provider-accurev
* [SCM-385] - AbstractCvsChangeLogCommand create a wrong command for case when startVersion == endVersion
* [SCM-386] - SCM plugin fails on "bootstrap" goal when shell environment has functions definitions
* [SCM-387] - CvsScmProviderRepository returns wrong CVSROOT for local repository
* [SCM-391] - urls without subfolders were not parsed correctly.
* [SCM-394] - git provider tests in trunk are locale aware
* [SCM-402] - scm:checkin doesn't work on OS X 10.5 Leopard
* [SCM-405] - 'cvs' and 'svnadmin' tools are requirements to run tests

** Improvement
* [SCM-322] - SCM plug-in should tell at what revision the source is when it finishes
* [SCM-348] - missing scm:bootstrap in overview
* [SCM-354] - [Patch] Allow attaching a Job to the Perforce changlist on check-in
* [SCM-359] - scm:update goals link not working (update) on Overview -> Introduction
* [SCM-368] - Windows path length limitations can be overcome by feeding an absolute path to SVN
* [SCM-370] - generated client spec contains backslashes leading die problems on unix os
* [SCM-390] - scm:branch gives misleading error when branch name parameter is missing
* [SCM-395] - Add a field in the git setting to be able to commit with the option --no-verify
* [SCM-397] - maven-scm-client should be a standalone app

** New Feature
* [SCM-71] - Implement accurev provider
* [SCM-182] - git provider
* [SCM-393] - Add option to pass in a list of profiles to scm:bootstrap
* [SCM-396] - git provider implements scm update
* [SCM-400] - add a POM that includes the standard providers as a set of dependencies

** Task
* [SCM-377] - upgrade plexus-utils
* [SCM-398] - Review website

Enjoy,

-The Maven team

Maven Javadoc Plugin 2.5 Released

2008-08-27T02:59:38Z

The Maven team is pleased to announce the release of the Maven Javadoc
Plugin, version 2.5

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.5</version>
</plugin>

Release Notes - Maven 2.x Javadoc Plugin - Version 2.5

** Bug
* [MJAVADOC-138] - javadoc:test-javadoc failed if target/classes
not already created
* [MJAVADOC-144] - Cannot generate Javadoc on Mac OS X if path
contains space characters
* [MJAVADOC-162] - javadocExecutable unusable
* [MJAVADOC-168] - Regression: 2.4-SNAPSHOT does not generate docs
for generates sources if run outside a build
* [MJAVADOC-178] - Transitive Dependencies to Taglet Artifacts are
not resolved nor added to the classpath
* [MJAVADOC-180] - aggregation doesn't work for test-javadoc goal
* [MJAVADOC-183] - Aggregate javadoc does not process the
src/main/javadoc directories
* [MJAVADOC-187] - Javadoc jar manifest should contain
Specification and Implementation details
* [MJAVADOC-188] - -top command line argument is passed even when
java version is <1.6, generating a warning
* [MJAVADOC-190] - Javadoc tool -excludedocfilessubdir has no effect
* [MJAVADOC-194] - javadoc 2.4 does not [build-helper:add-source
{execution: add-source}] when aggregating a javadoc for a project
* [MJAVADOC-198] - AbstractJavadocMojo#getClasspath(..) should use
subProject's managedVersionMap
* [MJAVADOC-201] - Links parameter should handle relative links
* [MJAVADOC-210] - Unit tests fail on OS X
* [MJAVADOC-212] -
AggregatorJavadocReport/AggregatorTestJavadocReport are used by
default in aggregator and no reports are generated

** Improvement
* [MJAVADOC-78] - Add a flag to provide standard doclet parameters
to custom ones too
* [MJAVADOC-182] - use ${project.build.sourceEncoding} as default
value for "encoding" parameter
* [MJAVADOC-189] - Allow skipping of javadoc generation
* [MJAVADOC-192] - Bump to a new release of Doxia
* [MJAVADOC-193] - Bump plexus-utils to 1.5.1
* [MJAVADOC-196] - Create AggregatorJavadocMojo similar to
AggregatorSourceJarMojo
* [MJAVADOC-197] - Provide flag to ignore errors
* [MJAVADOC-202] - Links ../apidocs from javadoc:javadoc to
javadoc:test-javadoc
* [MJAVADOC-203] - Test report should have its own config

** New Feature
* [MJAVADOC-191] - Add a new Mojo for test-jar
* [MJAVADOC-204] - Have a way to auto detect tagletClass from a
given tagletArtifact
* [MJAVADOC-206] - use ${project.reporting.outputEncoding} as
default value for "docencoding" and "charset" parameter and default to
UTF-8
* [MJAVADOC-208] - Added bootclasspath javadoc option
* [MJAVADOC-209] - Exclude debug files for javadoc:jar goal

** Task
* [MJAVADOC-199] - Upgrade to plexus-utils:1.5.5

** Wish
* [MJAVADOC-126] - Add the ability to load the stylesheet from a
jar (resource)
* [MJAVADOC-185] - Revert MJAVADOC-165 and default to platform encoding

Enjoy,

-The Maven team

Maven Plugin Tools 2.4.3 Released

2008-08-20T16:29:24Z

The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.4.3

The Maven Plugin Tools contains the necessary tools to be able to
produce Maven Plugins in a variety of languages.

http://maven.apache.org/plugin-tools
http://maven.apache.org/plugins/maven-plugin-plugin

Release Notes - Maven 2.x Plugin Tools - Version 2.4.3

** Sub-task
* [MPLUGIN-134] - Review the support of Mojo's annotations

** Bug
* [MPLUGIN-26] - Parsing issue due to qdox regression
* [MPLUGIN-126] - Report mojo outputs XDoc into wrong directory if
outputDirectory parameter is overriden with a relative path
* [MPLUGIN-130] - PluginDescriptorGenerator doesn't write
deprecated tag for a mojo
* [MPLUGIN-131] - PluginXdocGenerator doesn't handle correctly the
Resource bundles and make typo in some languages
* [MPLUGIN-133] - JavaMojoDescriptorExtractor doesn't handle @requiresReport

** Improvement
* [MPLUGIN-125] - Add deprecation messages to output of help mojo
* [MPLUGIN-128] - Add a line break before writing default value in
description field
* [MPLUGIN-129] - Avoid generation of emtpy plugin report for POM projects
* [MPLUGIN-132] - Don't encourage users to use "mvn -up" to update plugins

Enjoy,

-The Maven team

Maven War Plugin 2.1-alpha-2 Released

2008-08-14T08:22:34Z

The Maven team is pleased to announce the release of the Maven War
Plugin, version 2.1-alpha-2.

The War plugin is responsible for collecting all artifact
dependencies, classes and resources of the web application and
packaging them into a web application archive.

http://maven.apache.org/plugins/maven-war-plugin/

To get the latest version of the plugin, specify the version in your
project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-alpha-2</version>
</plugin>

Release Notes - Maven 2.x War Plugin - Version 2.1-alpha-2

** Bug
* [MWAR-60] - Source Excludes are being applied to WAR file
* [MWAR-62] - The comma separated list of tokens doesn't work with
the property <warSourceExcludes>.
* [MWAR-89] - filtering ${something.url} ignores my property value
and writes http://maven.apache.org/something
* [MWAR-96] - WebResource not filtered with system properties.
* [MWAR-101] - Scoped dependencies are not handled correctly
* [MWAR-109] - Problem using webResources in configuration
* [MWAR-116] - The outputFileNameMapping config creates bad
dependency files in WEB-INF/lib
* [MWAR-120] - Option containerConfigXML doesn't work
* [MWAR-129] - WebRessource not filtered
* [MWAR-133] - Filtering issue: wrong replacement of properties by
values from MavenProject object
* [MWAR-134] - ClasscastException when turning filtering on the
web resources
* [MWAR-136] - Could not overlay two overlays with same groupId
and artifactId (classifier)
* [MWAR-137] - Site's Overlays section doesn't reflect the correct
configuration for zip overlays
* [MWAR-139] - Wrong token replacement (@@ is replaced with
org.apache.maven.project.MavenProject@dedf1473)
* [MWAR-140] - 2.1-alpha-2 head is not compiling because
AbstractWarPackagingTask is trying to catch an IOException that is no
longer thrown
* [MWAR-141] - maven-metadata.xml is not being updated with latest
snapshots for 2.1-alpha-2
* [MWAR-144] - Custom filter list does not work

** Improvement
* [MWAR-30] - I can't build a war-file without a web.xml.
* [MWAR-102] - Upgrade maven-archiver dependency to 2.3
* [MWAR-131] - Ability to deploy the content of WEB-INF/classes as
a classified artifact
* [MWAR-132] - dependencies with same artifactId and != groupId
result is conflicts in WEB-INF/lib
* [MWAR-135] - Add an option to exclude content from the generated
archive to implement the skinny war process
* [MWAR-143] - War Overlays and resources filtering
* [MWAR-159] - Filtering deployments descriptors (web.xml)

** New Feature
* [MWAR-145] - Add a mojo parameter for file extensions which must
not be filtered.

** Task
* [MWAR-152] - mvn clean does not clean up target directories and
build logs from integration tests

** Wish
* [MWAR-118] - jar in lib dir are not cleaned if version of the
changes im pom.xml

Enjoy,
--
Wendy Smoak
on behalf of the Maven team

Maven Invoker Plugin 1.2.1 Released

2008-08-09T15:17:08Z

The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.2.1

This plugin is used to run a set of Maven projects. The plugin can
determine whether each project execution is successful, and optionally
can verify the output generated from a given project execution.

http://maven.apache.org/plugins/maven-invoker-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-invoker-plugin</artifactId>
<version>1.2.1</version>
</plugin>

Release Notes - Maven 2.x Invoker Plugin - Version 1.2.1

** Bug
* [MINVOKER-39] - Spaces are incorrectly handled on command line
* [MINVOKER-40] - Parent POMs are missing in IT repo
* [MINVOKER-41] - NullPointerException in InvokerMojo::runBuild in
case the mvn executable is not at the expected location
* [MINVOKER-43] - Sync repository identifier of custom IT repo with
identifier of real local repository
* [MINVOKER-44] - cloneProjectsTo fails to copy projects with the
same prefix
* [MINVOKER-45] - External properties file is ignored if parameter
testProperties is not defined

** Improvement
* [MINVOKER-42] - Incorrect message "See ...build.log for details'
when noLog is specified

Enjoy,

-The Maven team

Maven Antrun Plugin 1.2 Released

2008-08-09T10:02:27Z

The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.2

This plugin provides the ability to run Ant tasks from within Maven 2.
You can even embed your Ant scripts in the POM!

http://maven.apache.org/plugins/maven-antrun-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.2</version>
</plugin>

Release Notes - Maven 2.x Antrun Plugin - Version 1.2

Bug

* [MANTRUN-32] - ant tasks don't use correct environment in antrun plugin
* [MANTRUN-38] - Messed up maven.dependency.classpath when using
maven-antrun-plugin-1.1
* [MANTRUN-75] - tasks if or unless does not work properly
* [MANTRUN-82] - skip test
* [MANTRUN-85] - Plublic documentation is out of sync with released plugin

Improvement

* [MANTRUN-35] - mvn debug level not passed to ant
* [MANTRUN-43] - Standard ant properties are missing
* [MANTRUN-46] - Move the description of the mojo from
@description to the top of the class's comment block

New Feature

* [MANTRUN-41] - Easy access to dependency jars
* [MANTRUN-44] - No way to skip antrun when -Dmaven.test.skip is set

Task

* [MANTRUN-55] - Review Plugin Documentation

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11125&styleName=Html&version=12210

Enjoy,

-The Maven team

Maven IDEA Plugin 2.2 Released

2008-08-08T14:41:19Z

The Maven team is pleased to announce the release of the Maven IDEA
Plugin, version 2.2

This plugin create/updates an IDEA workspace for the current project
(individual modules are created as IDEA modules).

http://maven.apache.org/plugins/maven-idea-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-idea-plugin</artifactId>
<version>2.2</version>
</plugin>

Release Notes - Maven 2.x IDEA Plugin - Version 2.2

** Bug
* [MIDEA-89] - iml file generation done in the platform encoding,
not UTF-8
* [MIDEA-91] - Incorrect web module definition if repository drive
letter is lowercase
* [MIDEA-98] - Module filepath is generated incorrectly
* [MIDEA-100] - Module file (.iml) is generated in a way that
sources and javadocs are not recognized by Intellij Idea
* [MIDEA-102] - Module filepath is generated incorrectly for
sibling parent
* [MIDEA-103] - Incorrect module paths are generated when parent
project name is prefix in child project names
* [MIDEA-108] - mvn idea:idea should call phases process-sources
and generate-resources

** New Feature
* [MIDEA-99] - Allow the library to define a link to external javadoc.

Enjoy,

-The Maven team

Maven Deploy Plugin version 2.4 Released

2008-08-06T21:55:59Z

The Maven team is pleased to announce the release of the Maven Deploy
Plugin, version 2.4.

This plugin is used to add artifacts and associated metadata to a
remote repository [1].

http://maven.apache.org/plugins/maven-deploy-plugin/

To use this release, specify the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.4</version>
</plugin>

Release Notes - Maven 2.x Deploy Plugin - Version 2.4

** Bug
* [MDEPLOY-45] - Classifier not supported by deploy:deploy
* [MDEPLOY-56] - Parent version ignored when deploying file with
existing pom

** Improvement
* [MDEPLOY-66] - add XML encoding support for POM reading/writing

** New Feature
* [MDEPLOY-63] - Allow disabling deployment for artifacts that
should not be deployed

[1] For more information on managing remote repositories, see
http://maven.apache.org/repository-management.html

Enjoy,
--
Wendy Smoak
on behalf of the Maven team

Maven Filtering 1.0-beta-1 Released

2008-08-06T14:43:31Z

The Maven team is pleased to announce the release of the Maven
Filtering, version 1.0-beta-1

These Plexus components have been built from the filtering process/code
in Maven Resources Plugin. The goal is to provide a shared component for
all plugins which needs to filter resources.

http://maven.apache.org/shared/maven-filtering/

Release Notes - Maven Shared Components - Version maven-filtering-1.0-beta-1

** Improvement
* [MSHARED-46] - Create a common component for files filtering

Enjoy,

-The Maven team

Maven Invoker 2.0.9 Released

2008-08-06T09:30:43Z

The Maven team is pleased to announce the release of the Maven Invoker,
version 2.0.9

This shared component fires up a Maven build in a new JVM.

http://maven.apache.org/shared/maven-invoker/

Release Notes - Maven Shared Components - Version maven-invoker 2.0.9

** Bug
* [MSHARED-21] - Spaces are incorrectly handled on command line

Enjoy,

-The Maven team

Maven DOAP Plugin 1.0 Released

2008-08-01T10:22:12Z

The Maven team is pleased to announce the release of the Maven DOAP
Plugin, version 1.0.

This plugin generates a Description of a Project (DOAP) file from
information in a POM.

http://maven.apache.org/plugins/maven-doap-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-doap-plugin</artifactId>
<version>1.0</version>
</plugin>

Release Notes - Maven 2.x DOAP Plugin - Version 1.0

** Bug
* [MDOAP-6] - Support more repositories
* [MDOAP-13] - 'Examples' section on 'Introduction' page contains
a broken link.

** Improvement
* [MDOAP-1] - DOAP Plugin should support setting of shortdesc and
pmc and the about default should be
http://${project.artifactId}.rdf.apache.org
* [MDOAP-8] - ASF namespace is always include
* [MDOAP-9] - Support more DOAP resource like wikis
* [MDOAP-10] - Supports more DOAP roles for developers/contributors
* [MDOAP-12] - Take care of the xml:lang

** New Feature
* [MDOAP-4] - Handle versions

** Task
* [MDOAP-7] - Add test code
* [MDOAP-14] - Review and update site documentation

Enjoy,

-The Maven team

Maven Project Info Reports Plugin 2.1 Released

2008-07-28T07:50:35Z

The Maven team is pleased to announce the release of the Maven Project
Info Reports Plugin, version 2.1

This plugin generates standard reports for the specified project.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/

You can run mvn -up to get the latest version of the plugin, or 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</version>
</plugin>

Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.1

** Sub-task
* [MPIR-126] - Move PluginManagementRenderer in an inner class of
PluginManagementReport

** Bug
* [MPIR-48] - Internal html references are not generated in the
team-list.html
* [MPIR-49] - team-list.html is not correctly generated when table
is to large
* [MPIR-52] - Wrong text on scm page for svn protocol
* [MPIR-53] - there is no info about project-info-reports:summary
in documentation
* [MPIR-57] - URLs only link if they are FQDNs
* [MPIR-59] - Site generation exception for french language, error
with simple quote in translation "S'inscrire" for mailing list
* [MPIR-60] - Current head throws NPE when generating reports
* [MPIR-65] - Direct report generation breaks on skin version even
though it is specified
* [MPIR-66] - When run standalone, project metadata is missing
* [MPIR-70] - NullPointerException when generating Dependencies report
* [MPIR-75] - Typing mistake in properties file
* [MPIR-76] - Dependencies report is incorrect
* [MPIR-79] - Add explicit resource bundle for English
* [MPIR-81] - DependenciesRenderer logs Exception when it can't
find the artifact being built!!!
* [MPIR-84] - StringIndexOutOfBoundsException when ML archive dont
finish with a /
* [MPIR-89] - Bad spelling in Project Information => Overview =>
Dependencies
* [MPIR-90] - Bad style in text "Access from behind a firewall"
* [MPIR-91] - Bad spelling in text "Access through a proxy"
* [MPIR-92] - Wrong encoding in german properties
* [MPIR-96] - Switched link text and target in license report
* [MPIR-98] - Team list does not contain anchors on user ids
* [MPIR-99] - Strange warnings when generating Plugin Management report
* [MPIR-104] - Regression in 2.1-SNAPSHOT: SVN is no more recognized
* [MPIR-106] - Regression in 2.1-SNAPSHOT, the Project
Dependencies and the Project Transitive Dependencies are the same
* [MPIR-109] - Wrong description of in source repository overview
* [MPIR-119] - Dependency Repository Locations in Dependency
Report doesn't allow snapshot artifacts url from the snapshot
repositories
* [MPIR-122] - Brazilian Portuguese language bundle - encoding
problems and improvements
* [MPIR-123] - Hungarian language bundle - encoding problems and
improvements
* [MPIR-124] - License report is empty in offline
* [MPIR-129] - Duplicate entries of the same artifact in Licenses
section of Dependencies report
* [MPIR-130] - No mark or link to SNAPSHOT artifacts in Dependency
Repository Locations section of Dependencies report

** Improvement
* [MPIR-28] - improve convergence report
* [MPIR-46] - Sample reports are out of date
* [MPIR-47] - Dependency Report does not show origin of transitive
dependency
* [MPIR-54] - Team list table improvement
* [MPIR-56] - Refactor the dependencies report
* [MPIR-58] - The sandbox component Jar has been renamed to JarAnalyzer
* [MPIR-61] - [PATCH] Updated CI Systems
* [MPIR-62] - [PATCH] Dependency File Details : set right
justification for numeric columns
* [MPIR-64] - Korean translation resource file
* [MPIR-67] - Please update the german localization.
* [MPIR-69] - add anchors for developers
* [MPIR-72] - Upgrade to doxia 1.0-alpha-9
* [MPIR-82] - Clarify usage of outputDirectory parameter
* [MPIR-87] - Show repositories an artifact is deployed to as a report
* [MPIR-94] - Change optional label in dependencies site
* [MPIR-108] - Add validation of SCM urls
* [MPIR-110] - Update code due to deprecated classes in
maven-dependency-tree:1.1
* [MPIR-111] - Make Classifier and Optional column in dependencies
report "optional" in the renderer
* [MPIR-112] - Dependency Listings is too big: replace it by
toogle entries in the dependency tree
* [MPIR-113] - Dependency Tree lists all dependencies: needs to
reduce to dependencies used by the project
* [MPIR-115] - Make the Sealed column optional in dependencies report
* [MPIR-116] - Make the classifier column optional in dependencies
management report
* [MPIR-117] - Replaced the table caption in the CI report
* [MPIR-118] - Equalize links to project web site for artifactId
* [MPIR-125] - Create a plugin report

** New Feature
* [MPIR-26] - Could the Dependencies report show the size of the jars/etc...
* [MPIR-55] - Detailed Artifact Information & Repository Location
for each Dependency.
* [MPIR-63] - Allow configuration of scm connection,
developerConnection and url
* [MPIR-83] - Include reports for DependencyManagement and PluginManagement

** Task
* [MPIR-34] - Update the i18n properties file with these new additions
* [MPIR-50] - review plugin documentation
* [MPIR-100] - Use Doxia 1.0-alpha-11
* [MPIR-114] - Validate all generated reports with validator.w3.org
* [MPIR-121] - dependency.locations.enabled should set to true by default

** Test
* [MPIR-43] - Use the plugin testing harness and add tests for the
project-info-report mojos

Enjoy,

-The Maven team

Maven Plugin Testing 1.2 Released

2008-07-23T04:00:28Z

The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 1.2

The Maven Plugin Testing contains the necessary modules to be able to
test Maven Plugins.

http://maven.apache.org/plugin-testing/

Note: This release changes the groupId for the artifacts.

You can specify the version in your project's dependency
configuration, for instance:

<dependency>
<groupId>org.apache.maven.plugin-testing</groupId>
<artifactId>maven-plugin-testing-harness</artifactId>
<version>1.2</version>
<scope>test</scope>
</dependency>

Enjoy,

-The Maven team

Maven Site Plugin 2.0-beta-7 Released

2008-07-02T22:34:30Z

The Maven team is pleased to announce the release of the Maven Site
Plugin, version 2.0-beta-7

The Maven 2 Site plugin is used to generate a site for the project. The
generated site also includes the project's report distributions that was
configured in the <reporting> section of the pom.

http://maven.apache.org/plugins/maven-site-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>2.0-beta-7</version>
</plugin>

Release Notes - Maven 2.x Site Plugin - Version 2.0-beta-7

** Bug
* [MSITE-25] - mvn site:deploy and site:stage-deploy ignores server
configuration in settings.xml
* [MSITE-143] - SCP works for deploy goal, but not for site-deploy
* [MSITE-174] - Default bundle used not correct
* [MSITE-211] - Can't deploy site using site:deploy due to a
ProxyHTTP error
* [MSITE-262] - site.xml not inherited if build run from parent
* [MSITE-270] - site.xml: menus inherited that should not
* [MSITE-271] - Page title reads Introduction to $project.name
* [MSITE-274] - space/newline added after added after anchor, link,
bold, italic and monospaced tags
* [MSITE-304] - site:stage-deploy creates different directory
structure than site:site
* [MSITE-313] - Use proper file encoding when storing site
descriptor in local repo
* [MSITE-316] - Broken links to submodules when staging site
* [MSITE-317] - User proper encoding when interpolating site descriptor
* [MSITE-341] - 'nonProxyHosts' element is not handled when we
deploy a site

** Improvement
* [MSITE-199] - Add publishDate position "none"
* [MSITE-280] - Fix FAQ entry about staging
* [MSITE-281] - Employ consistent typesetting/formatting
* [MSITE-290] - Move logic from AbstractSiteMojo and
AbstractSiteRenderingMojo for Doxia related stuff
* [MSITE-292] - Swedish translation for the site
* [MSITE-303] - Discard invalid characters from directory name
generated for staging site
* [MSITE-314] - use ${project.build.sourceEncoding} as default
value for "inputEncoding" parameter

** New Feature
* [MSITE-212] - Catalan Language
* [MSITE-251] - tr locale support
* [MSITE-328] - Danish internationalization properties file

** Task
* [MSITE-327] - Use Doxia 1.0-alpha-11
* [MSITE-335] - Use maven-doxia-tools 1.0.1

Enjoy,

-The Maven team

Maven Plugin Tools 2.4.2 Released

2008-06-26T03:56:30Z

The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.4.2

The Maven Plugin Tools contains the necessary tools to be able to
produce Maven Plugins in a variety of languages.

http://maven.apache.org/plugins/maven-plugin-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-plugin-plugin</artifactId>
<version>2.4.2</version>
</plugin>

Release Notes - Maven 2.x Plugin Tools - Version 2.4.2

** Bug
* [MPLUGIN-92] - helpmojo resulting mojo requires a project and
performs multiple times
* [MPLUGIN-93] - Use correct encoding for plugin-registry.xml
* [MPLUGIN-94] - Use correct encoding for plugin descriptor
* [MPLUGIN-96] - Handle character encoding properly in makeHtmlValid()
* [MPLUGIN-97] - Use correct encoding for plugin metadata
* [MPLUGIN-99] - Do not document help goal twice
* [MPLUGIN-107] - Escape special characters in string literals used
by HelpMojo
* [MPLUGIN-108] - Incorrect minimum Maven version reported in
plugin documentation
* [MPLUGIN-114] - PluginXdocGenerator NullPointerException
* [MPLUGIN-118] - missing / in closing tag in generated pom snippet
* [MPLUGIN-119] - Regression when generating site (mojo description
pages) for my own maven plugins
* [MPLUGIN-121] - Plugin document report contains invalid XML in
'Usage' section.
* [MPLUGIN-123] - mvn some-plugin:help command requires a valid pom.xml

** Improvement
* [MPLUGIN-95] - Output proper charset name in XDoc report for mojos
* [MPLUGIN-98] - Remove javadoc inline tags from output of help mojo
* [MPLUGIN-112] - Respect line breaks from Javadoc when generating
help goal
* [MPLUGIN-113] - Improve generated help mojo to control output
(indent, width)
* [MPLUGIN-115] - Limit detail help output to a single goal
* [MPLUGIN-116] - Improve XHTML compliance
* [MPLUGIN-117] - Emphasize goal/parameter deprecation

Enjoy,

-The Maven team

Maven Repository Plugin 2.1 Released

2008-06-26T02:34:58Z

The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.1

This plugin is used to create bundles of artifacts that can be uploaded
to the central repository.

http://maven.apache.org/plugins/maven-repository-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-repository-plugin</artifactId>
<version>2.1</version>
</plugin>

Release Notes - Maven 2.x Repository Plugin - Version 2.1

** Bug
* [MREPOSITORY-2] - project.scm.connection should not be required
for bundle-create
* [MREPOSITORY-6] - Don't check for License.txt file, but verify
the licenses element in pom.xml
* [MREPOSITORY-11] - Javadoc not included in the bundle

** Improvement
* [MREPOSITORY-5] - Plugin website needs to be completed
* [MREPOSITORY-10] - add XML encoding support for POM reading/writing

Enjoy,

-The Maven team

Wagon 1.0 beta 3 released

2008-06-13T04:26:36Z

The Maven team is pleased to announce the release of Wagon 1.0-beta-3.

This release includes 59 fixes. You can take a look at the release
notes here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=12544

* Additional Release Notes

The Slide-based webdav and ganymed alternative SSH wagon has been
removed in this release. The previous releases of each remain available.

A new wagon-webdav-jackrabbit has been added which features an
improved WebDAV client.

Wagon SCM has been promoted from the sandbox to be a part of this
release.

Due to classloading constraints, these releases may not work as
extensions in existing Maven versions.

-The Maven team

Maven Checkstyle Plugin 2.2 Released

2008-06-04T14:54:09Z

The Maven team is pleased to announce the release of Maven Checkstyle
Plugin, version 2.2.

The Checkstyle plugin generates a report regarding the code style used
by the developers. For more information about Checkstyle, see
http://checkstyle.sourceforge.net/

http://maven.apache.org/plugins/maven-checkstyle-plugin/

You can run 'mvn -up' to get the latest version of the plugin, or
specify the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.2</version>
</plugin>

Release Notes - Maven 2.x Checkstyle Plugin - Version 2.2

** Bug
* [MCHECKSTYLE-40] - Some checks need the compiled classes (for
instance JavadocMethod)
* [MCHECKSTYLE-41] - Rules summary count of duplicate JavadocMethod
configurations are merged
* [MCHECKSTYLE-48] - regression: report generation doesn't work
while dealing with the header file
* [MCHECKSTYLE-53] - Cannot copy static resources on windows
* [MCHECKSTYLE-54] - checkstyle:check does not see provided scope
dependencies
* [MCHECKSTYLE-55] - Wrong rules summary for GenericIllegalRegexp
when message contains a quote
* [MCHECKSTYLE-58] - Tests fail on non-English JVM
* [MCHECKSTYLE-59] - Checkstyle Report fails if propertyExpansion
contains backslash characters
* [MCHECKSTYLE-63] - The local absolute path to the headerLocation
file is output in the report
* [MCHECKSTYLE-65] - regression in checkstyle 2.2: config locations
seen as null
* [MCHECKSTYLE-67] - settings suppressionsLocation does not set
checkstyle.suppressions.file like suppressionsFile does
* [MCHECKSTYLE-76] - don't check the test code
* [MCHECKSTYLE-81] - Add dedicated resource bundle for locale "en"
* [MCHECKSTYLE-83] - Checkstyle report showing a check as Error
when it is Warning
* [MCHECKSTYLE-85] - Make tests platform-independent
* [MCHECKSTYLE-90] - Checkstyle-2.2-SNAPSHOT not working with Maven
2.0.9

** Improvement
* [MCHECKSTYLE-35] - move rules summary to the bottom
* [MCHECKSTYLE-50] - Sort the files and details in the report
* [MCHECKSTYLE-56] - Use Release 4.2 of Checkstyle
* [MCHECKSTYLE-60] - French localisation of the checkstyle report.
* [MCHECKSTYLE-68] - Use Release 4.3 of Checkstyle
* [MCHECKSTYLE-71] - need a skip flag similar to surefire
* [MCHECKSTYLE-74] - invalid report heading html
* [MCHECKSTYLE-80] - Add german translation
* [MCHECKSTYLE-82] - Clarify usage of outputDirectory parameter
* [MCHECKSTYLE-87] - Use Release 4.4 of Checkstyle
* [MCHECKSTYLE-95] - Allow to configure file encoding for source files

** New Feature
* [MCHECKSTYLE-45] - It should be possible to configure
checkstyle:check to fail on "warnings".
* [MCHECKSTYLE-47] - Allow running checkstyle in test sources

** Task
* [MCHECKSTYLE-69] - Improve documentation related to custom
developed Checkstyle check modules

** Wish
* [MCHECKSTYLE-84] - Disabled "HiddenField" check

Enjoy!

- The Maven Team

Maven Runtime 1.0-alpha-1 released

2008-06-03T02:41:47Z

The Maven team is pleased to announce the release of Maven Runtime,
version 1.0-alpha-1.

This shared component allows introspection of Maven project metadata at runtime.

http://maven.apache.org/shared/maven-runtime/

You can run mvn -up to get the latest version of the component, or specify
the version in your project's dependency configuration:

<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-runtime</artifactId>
<version>1.0-alpha-1</version>
</dependency>

Release Notes - Maven Runtime - Version 1.0-alpha-1

* First release

Enjoy,

-The Maven team

Maven Ant Plugin 2.1 Released

2008-05-29T10:44:20Z

The Maven team is pleased to announce the release of the Maven Ant
Plugin, version 2.1

This plugin generates Ant build files for Ant 1.6.2 or above.

http://maven.apache.org/plugins/maven-ant-plugin/

You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ant-plugin</artifactId>
<version>2.1</version>
</plugin>

Release Notes - Maven 2.x Ant Plugin - Version 2.1

** Bug
* [MANT-4] - Generated ANT contains hardcoded "get" tasks that
look at the "C:\" drive etc... when using a local repository
* [MANT-30] - classcast exception when running ant:ant on
tagtraum.com's gcviewer project
* [MANT-32] - java.lang.ClassCastException when packaging jeuclid-3.0.1
* [MANT-34] - The generated maven-build.xml and
maven-build.properties contains absolute path to local repository
* [MANT-35] - The generated maven-build.xml has paths that contain
\ characters on Windows
* [MANT-36] - Use correct file encoding when writing build files
* [MANT-37] - Wrong path to test resources in maven-build.xml
* [MANT-39] - Always specify source/target options for javac

** Improvement
* [MANT-6] - "test" targets should fail if junit.jar not present
* [MANT-7] - "test" target should support running a single test -
just like mvn test does
* [MANT-22] - Make it possible to run the package target without tests
* [MANT-38] - Use reporting output directory configured in POM
* [MANT-40] - Use includes/excludes configured for Surefire when
running tests

Enjoy,

-The Maven team

Maven Shade Plugin 1.1 released

2008-05-29T08:22:04Z

The Maven team is pleased to announce the release of the Maven Shade
Plugin, version 1.1

This plugin provides the capability to package the artifact in a uber-
jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies.

http://maven.apache.org/plugins/maven-shade-plugin/

You can specify the plugin version in your project's plugin
configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>1.1</version>
</plugin>

This release includes several bug fixes and other improvements:

** Bug
* [MSHADE-23] - ${basedir} is wrong after running shade plugin
* [MSHADE-24] - Use proper file encoding when generating dependency
reduced POM
* [MSHADE-25] - Use proper encoding when reading/writing component
descriptor
* [MSHADE-26] - Fix case-insensitive string comparisions in resource
transformers
* [MSHADE-29] - Documentation has invalid xml
* [MSHADE-31] - When promoteTransitiveDependencies=true, all
<exclusions> are stripped from the dependency-reduced-pom
* [MSHADE-34] - Shade includes both .jar and -test.jars when only
the .jar was needed

** Improvement
* [MSHADE-27] - Allow to configure file encoding for processing of
NOTICE file
* [MSHADE-28] - Add full support for glob patterns in relocator
exclusions

Enjoy,
-The Maven team

Maven PMD Plugin 2.4 released

2008-05-29T08:15:19Z

The Maven team is pleased to announce the release of the Maven PMD
Plugin, version 2.4

This plugin is used to check java sources for potential programming
problems like possible bugs, dead code, suboptimal code, etc...

http://maven.apache.org/plugins/maven-pmd-plugin/

You can specify the plugin version in your project's plugin
configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>2.4</version>
</plugin>

This release includes several bug fixes and other improvements:

** Bug
* [MPMD-61] - When running build using "-f <path_to_pom>/pom.xml"
the site is stored in working directory instead of project directory
* [MPMD-70] - Move hard-coded strings to resource bundle
* [MPMD-75] - PMD plugin unable to exclude groovy-stub files.
* [MPMD-77] - excludeRoots doesn't work with basedir-relative paths

** Improvement
* [MPMD-64] - verbose output not useful for inner classes
* [MPMD-71] - Add german translation
* [MPMD-72] - Add dedicated resource bundles for locale "en"
* [MPMD-74] - Clarify usage of outputDirectory parameter
* [MPMD-76] - use ${project.build.sourceEncoding} as default value
for "sourceEncoding" parameter
* [MPMD-79] - Warn about usage of platform encoding

** Task
* [MPMD-78] - Update to PMD 4.2.1 (actually to 4.2.2)

---
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

Maven Doxia Integration Tools 1.0 Released

2008-05-29T05:57:12Z

The Maven team is pleased to announce the release of the Maven Doxia
Integration Tools, version 1.0. It is a collection of tools to help
the integration of Doxia in Maven plugins.

http://maven.apache.org/shared/maven-doxia-tools

You can specify the version in your project's dependency configuration:

<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-doxia-tools</artifactId>
<version>1.0</version>
</dependency>

Enjoy,

-The Maven team

Maven Doxia and Doxia Sitetools 1.0-alpha-11 Released

2008-05-20T15:11:19Z

The Maven team is pleased to announce the release of Maven Doxia and
Doxia Sitetools, version 1.0-alpha-11.

http://maven.apache.org/doxia/

Release Notes - Maven Doxia - Version 1.0-alpha-11

** Bug
* [DOXIA-189] - newline added after every closing tag

Release Notes - Maven Doxia Sitetools - Version 1.0-alpha-11

** Bug
* [DOXIASITETOOLS-6] - ugly green shadow on breadcrumbs text when
viewed with Konqueror

Enjoy!

- The Maven Team

Maven Surefire 2.4.3 Released

2008-05-15T11:14:29Z

The Maven team is pleased to announce the release of the Maven Surefire,
version 2.4.3.

Maven Surefire is used during the "test" phase of the build lifecycle to
execute your unit tests. It supports JUnit 3 & 4 as well as TestNG, and
generates TXT, XML and HTML reports.

http://maven.apache.org/plugins/maven-surefire-plugin/

You can specify the plugin version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.4.3</version>
</plugin>

Surefire 2.4.3 requires Maven 2.0.6 or higher.

Release Notes - Maven Surefire - Version 2.4.3

** Bug
* [SUREFIRE-264] - XRef links do not work with aggregated reports on
windows
* [SUREFIRE-423] - Output a title for the report
* [SUREFIRE-440] - Fix serialization of File[] into properties for
forked Surefire run
* [SUREFIRE-459] - Integration test using Jetty and JSP 2.1 fails
after update to maven-surefire-plugin 2.4
* [SUREFIRE-460] - surefire-api manifest content is wrong: it is a
copy of commons-lang
* [SUREFIRE-463] - ClassCastException when using testng suiteXmlFile
and forkMode=always
* [SUREFIRE-467] - NoSuchMethodError UrlUtils.getURL when using JDK3
for testing
* [SUREFIRE-481] - java.lang.NoSuchMethodError when forking on a 1.3
JDK
* [SUREFIRE-491] - All system properties from Maven process are copied
to forked Surefire process
* [SUREFIRE-492] - Allow "test" parameter to override suiteXmlFiles
* [SUREFIRE-493] - UrlUtilsTest fails

** Improvement
* [SUREFIRE-422] - Strip "Maven" from report title
* [SUREFIRE-426] - Add german translation
* [SUREFIRE-473] - Documentation for additionalClassPath feature
* [SUREFIRE-474] - Allow TestNG to use its built-in HTMLReporter
* [SUREFIRE-484] - Don't output empty tables
* [SUREFIRE-485] - Support AntUnit XML output
* [SUREFIRE-490] - Provide an option to use simplified classloading

** Task
* [SUREFIRE-488] - Document TestNG listeners/reporters
* [SUREFIRE-489] - Document classpath issues

Enjoy,

-The Maven team

Maven Archetype Plugin 2.0-alpha-3 Released

2008-04-28T15:14:42Z

The Maven team is pleased to announce the release of the Maven
Archetype Plugin, version 2.0-alpha-3

The Archetype Plugin allows the user to create a Maven 2 project from
an existing template called an archetype. It also allows the user to
create an archetype from an existing project.

http://maven.apache.org/plugins/maven-archetype-plugin/

Release Notes - Maven Archetype - Version 2.0-alpha-3

** Bug
* [ARCHETYPE-122] - The defined artifact is not an archetype?
* [ARCHETYPE-124] - custom archetype-catalog.xml not read
* [ARCHETYPE-126] - Site menu is corrupted
* [ARCHETYPE-129] - incorrect error handling in batch mode
* [ARCHETYPE-130] - selecting "N" to "is this correct" question
resets all variables, even those that were input from the command line
* [ARCHETYPE-132] - The create-from-project goal does not work on
windows for multi-module projects
* [ARCHETYPE-137] - Problem when setting default values for
archetype-metadata.xml
* [ARCHETYPE-139] - cannot create archetype for existing project
without pre-existing pom
* [ARCHETYPE-140] - archetype:generate doesn't support inserting a
module into a multi-module build like :create did
* [ARCHETYPE-141] - wrong goal name in docs
* [ARCHETYPE-144] - Fails "archetype:create" when specify archetypeVersion
* [ARCHETYPE-146] - Archetype Resources not being processed on Windows.
* [ARCHETYPE-149] - archetype generate -DarchetypeRepository not working
* [ARCHETYPE-150] - New maven-archetype-plugin ignores the
remoteRepositories system property
* [ARCHETYPE-153] - Multimodule archetype does not propagate the
artifactId in module names.
* [ARCHETYPE-159] - mvn archetype:generate is failing to download
needed archetype artifacts
* [ARCHETYPE-160] - [regression] the default (15) is no longer
present in generate

** Improvement
* [ARCHETYPE-109] - plugins should have a auto-generated goal "help"
* [ARCHETYPE-112] - Allow to configure the filteredExtentions from
the archetype.properties file
* [ARCHETYPE-135] - add a variabl containing package in a path format
* [ARCHETYPE-143] - Add the possibility to generate files at project's root

** Wish
* [ARCHETYPE-154] - Can i ask when will alpha-3 released

Enjoy,

-The Maven team

Maven Ant Tasks 2.0.9 Released

2008-04-17T14:20:24Z

The Apache Maven team is pleased to announce the release of the Maven Ant
Tasks, version 2.0.9.

You can find the binaries here:

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

You can find the release notes here:

http://maven.apache.org/ant-tasks-release-notes.html

Enjoy,

-The Apache Maven team

Maven Changes Plugin 2.0 Released

2008-04-16T14:27:53Z

The Maven team is pleased to announce the release of the Maven Changes
Plugin, version 2.0

This plugin is used to inform your users of the changes that have
occurred 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 can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.0</version>
</plugin>

Release Notes - Maven 2.x Changes Plugin - Version 2.0

** Bug
* [MCHANGES-66] - The changes plugin scatters white space over its
Changes report
* [MCHANGES-75] - Setting maxEntries too high causes a
SAXParseException
* [MCHANGES-88] - NoSuchMethodError with maven 2.0.8 when
generating changes-report
* [MCHANGES-89] - AbstractJiraDownloader throws an exception when
jira returns a circular redirect
* [MCHANGES-91] - Output a title for the reports
* [MCHANGES-96] - Change type of path parameters to java.io.File
* [MCHANGES-100] - Generating the jira-report causes error "The
system cannot find the path specified"
* [MCHANGES-102] - Fix case-insensitive string handling
* [MCHANGES-105] - java.lang.NoSuchMethodError on changes:jira-report

** Improvement
* [MCHANGES-92] - JIRA Report Improvements
* [MCHANGES-93] - Add dedicated resource bundle for locale "en"
* [MCHANGES-94] - Add option to configure the sort order of the
JIRA report
* [MCHANGES-95] - Add german translation
* [MCHANGES-97] - Fix VTL errors
* [MCHANGES-99] - Make it possible to show issues only for the
current release
* [MCHANGES-103] - Allow suffix "ASC" for sort columns

** Wish
* [MCHANGES-101] - Consider changing log outputs to debug

Enjoy,

-The Maven team

Apache Maven 2.0.9 Released

2008-04-10T07:43:07Z

The Apache Maven team would like to announce the availability of Maven
2.0.9.

This release went through a new process that saw 8 release candidates tested
by the user community before the final release and we expect it to be more
robust than previous versions. There are several important fixes and
changes, most notably locking down core plugins in the super pom. You can
read details in the release notes linked below.

You can find the binaries here:

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

You can find the release notes here:

http://maven.apache.org/release-notes.html

You can find the roadmap for future issues here:

http://jira.codehaus.org/browse/MNG?report=com.atlassian.jira.plugin.system.project:roadmap-panel

Thanks,

The Apache Maven Team

[ANNOUNCE] Apache Archiva 1.0.2 Released

2008-04-08T21:07:05Z

The Apache Archiva team is pleased to announce the release of Archiva
1.0.2

Archiva is a build artifact repository manager for use with build
tools such
as Maven, Continuum and Ant.

It has features like repository search and browse, securing
repositories,
identifying unknown artifacts and reporting of repository problems.

Aside from these, it can also act as a nearby (proxy) cache of popular
global repositories.

The latest release is now available here:

http://maven.apache.org/archiva/download.html

If you have any questions, please consult:

- the web site: http://maven.apache.org/archiva/
- the archiva-user mailing list: http://maven.apache.org/archiva/mail-lists.html

New in Archiva 1.0.2
====================

* Configurable Proxy Error Handling
Two new options have been added to the proxy connector configuration
page:

- On remote error - gives control over whether to stop immediately,
continue to try for a successful proxy, or ignore an error
- Return error when - gives control over whether to return an
existing artifact if present or fail regardless if a remote error
occurs when updating an artifact

Change Log for Archiva 1.0.2
============================

* [MRM-159] - should not respond with a 404 if proxying a file
results in a remote error
* [MRM-532] - Unable to specify the location of the index files
through the web ui
* [MRM-598] - Validation error on new repository creation and
other fields under certain conditions
* [MRM-608] - Unable to find project model for [...] if the
initial import of the POM failed
* [MRM-617] - Reporting does not work due to bug in client-side
JavaScript validation
* [MRM-618] - PLEXUS_BASE does not work for local databases
* [MRM-622] - database not being updated with project model
information
* [MRM-626] - ClassCastException when saving proxy connector with
property defined
* [MRM-627] - Archiva doesn't download SNAPSHOTs for proxied
repositories.
* [MRM-642] - archiva-common tests rely on relative paths
* [MRM-655] - The logs are duplicated in the archiva.log and
wrapper.log file.
* [MRM-659] - archiva cannot serve ejb artifacts from a maven1
repository
* [MRM-661] - remote repository removals are not saved after
restart
* [MRM-664] - Cannot download a strut-module artifact in a Legacy
repository
* [MRM-674] - LayoutException when downloading SNAPSHOT test-
sources
* [MRM-683] - Archiva version missing from pages and logs
* [MRM-687] - Project model cannot be added to database if it
inherits groupId and/or version from parent POM
* [MRM-689] - Incorrect war name in example for tomcat
* [MRM-690] - using undefined appserver.base
* [MRM-691] - Can't get any of the consumers to work without
through a NPE
* [MRM-701] - Buggy documentation on "separating the base from
the installation"
* [MRM-703] - Artifacts with extensions longer than fours
characters breaks repository scanning.
* [MRM-713] - extensionPattern in FilenameParser is incorrect
* [MRM-715] - error adding artifacts to Lucene under some
circumstances
* [MRM-719] - NPE during repository scan
* [MRM-725] - /archiva/browse URL does not work on WebSphere
* [MRM-727] - Archiva does not download plugin artifacts in
Geronimo
* [MRM-734] - Unable to update metadata - No versions found for
reference
* [MRM-746] - unable to include *.xml in artifacts list as it
picks up maven-metadata.xml
* [MRM-750] - Adding a network proxy doesn't require an identifier
* [MRM-755] - No content type for .pom files denoted in file
"archiva-mime-types.txt" - workaround included
* [MRM-758] - unable to schedule cron expressions that contain a
comma
* [MRM-761] - Exception when trying to retrieve a Maven 1
artifact of type zip
* [MRM-762] - Footer doesn't stretch across repositoryScanning
and database pages
* [MRM-763] - Default cron expression for database update is
invalid
* [MRM-764] - default policies are not selected in the add proxy
connector page
* [MRM-504] - Find Artifact page needs more onscreen information/
instructions
* [MRM-656] - Admin guide for installing WAR needs updating
* [MRM-666] - Edit Managed Repository page should indicate the
repo id being edited
* [MRM-700] - Review the documentation on deploying to Archiva
for inconsistent repository ids
* [MRM-720] - Upgrade Lucene from 2.0 to 2.3.1

Thanks,
The Apache Archiva team

Maven Eclipse Plugin 2.5.1 Released

2008-04-05T00:09:23Z

The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.5.1

This plugin is used to generate Eclipse IDE files (*.classpath,
*.wtpmodules and the .settings folder) for use with a project.

http://maven.apache.org/plugins/maven-eclipse-plugin/

You can run mvn -up to get the latest version of the plugin, or
specify the version in your project's plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.5.1</version>
</plugin>

This release fixes several bugs.

Release Notes - Maven 2.x Eclipse Plugin - Version 2.5.1

** Bug
* [MECLIPSE-266] - plugin applies java facet to ear project
* [MECLIPSE-411] - manifest property usage is only for ogsi maifests
* [MECLIPSE-412] - Generation of jst.java Facet for EAR packaging
kills my RAD workspace
* [MECLIPSE-413] - EclipseOSGiManifestWriter uses the artifact id
and not the EclipseProjectName

** New Feature
* [MECLIPSE-405] - to-maven target should allow to strip qualifier
when creating artifacts from osgi bundles

Enjoy,

-The Maven team
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

Maven Reporting Impl 2.0.4.1 Released

2008-03-25T19:05:12Z

The reporting implementation is used to render site reports. This release
fixes an incompatibility with newer doxia implementations.

This has just one change from 2.0.4:

http://jira.codehaus.org/browse/MNG-3476

--The Maven Team