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

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

You can run mvn -U 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-assembly-plugin</artifactId>
   <version>2.1</version>
</plugin>

Changes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12219&styleName=Text&projectId=11126&Create=Create

* [MASSEMBLY-2] - TAR produces warning messages for over 100 cahrs in path name * [MASSEMBLY-5] - mvn assembly:assembly fails if there is no target directory already present * [MASSEMBLY-8] - Assembly plugin fails to resolve dependency when it tries to package the application * [MASSEMBLY-9] - assembly plugin with jar-with-dependency fails if there is no classes * [MASSEMBLY-11] - In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory * [MASSEMBLY-13] - assembly should automatically include generated artifacts for bin.xml (including all in a reactor)
* [MASSEMBLY-20] - Assembly doesn't work with provided scope
* [MASSEMBLY-29] - Possibility to aggrates sources from other modules
* [MASSEMBLY-33] - document assembly descriptoir in more detail
* [MASSEMBLY-37] - Assembly plugin should have the option not to repeat the build process every <execution>
* [MASSEMBLY-40] - Evaluate project variables within assembly descriptors
* [MASSEMBLY-43] - AbstractUnpackMojo#getDependencies() returns too much
* [MASSEMBLY-46] - artifact   classifier  not used in  outputFileNameMapping
* [MASSEMBLY-49] - InvalidArtifactRTException is thrown when appendAssemblyId=false
* [MASSEMBLY-51] - assembly:attached fails
* [MASSEMBLY-52] - dependencySet is incorrect during multi-module builds
* [MASSEMBLY-55] - Lost ability to attach artifact without classifier
* [MASSEMBLY-64] - jar-with-dependencies has a last-one-copies-wins policy which can fail signed jars
* [MASSEMBLY-65] - source repository on web site incorrect
* [MASSEMBLY-70] - assembly:directory does not honor <fileMode>
* [MASSEMBLY-74] - MANIFEST.MF is not used when specified in configuration.
* [MASSEMBLY-82] - When creating a repository for assembly include transitive requirements * [MASSEMBLY-85] - Parent POMs are not pulled down into the assembled repository
* [MASSEMBLY-89] - outputFileNameMapping broken
* [MASSEMBLY-92] - Assembly plugin fails with fatal error if a particular fileset directory does not exist * [MASSEMBLY-98] - Assembly groupVersionAlignment excludes affects all other groupVersionAlignment
* [MASSEMBLY-54] - Unable to filter files while creating assembly
* [MASSEMBLY-56] - Refactor DirectoryMojo so it can be run either stand-alone or attached
* [MASSEMBLY-57] - Add xsd to the set of modello outputs
* [MASSEMBLY-59] - Patch to the assembly plug-in introduction APT document
* [MASSEMBLY-60] - use DirectoryArchiver component instead of the internal DirectoryArchiver class in the plugin * [MASSEMBLY-61] - Should remove/deprecate AbstractUnpackAssembly's classifier field * [MASSEMBLY-68] - Need method to exclude all child dependencies when creating a jar * [MASSEMBLY-80] - Provide an option to write the artifact metadata to a repository * [MASSEMBLY-81] - Provide an option to use all dependencies in the creation of a repository * [MASSEMBLY-86] - Allow an easy way to exclude an artifact from groupId version alignment
* [MASSEMBLY-62] - Ability to share DependencySets, FileSets, FileItems
* [MASSEMBLY-71] - Allow an archive base directory that accepts variables
* [MASSEMBLY-95] - Support unpacking of tar.gz, tgz, tar.bz2, and tbz2 archivers




Reply via email to