You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@maven.apache.org by John Casey <jd...@apache.org> on 2008/03/01 01:04:20 UTC

[ANN] Maven Assembly Plugin 2.2-beta-2 Released

The Maven team is pleased to announce the release of the Maven  
Assembly Plugin, version 2.2-beta-2

This plugin is used to build custom archives, such as those used to  
distribute project releases.

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

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

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-assembly-plugin</artifactId>
  <version>2.2-beta-2</version>
</plugin>


Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-2

(See: http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=11126&styleName=Text&version=14027)


** Bug
     * [MASSEMBLY-121] - Custom manifest attributres are ignored.
     * [MASSEMBLY-129] - BaseDirectory Ignored When Including a  
Repository
     * [MASSEMBLY-156] - appendAssemblyId cannot be false
     * [MASSEMBLY-162] - In a multiproject environment, assembly  
takes wrong dependencies
     * [MASSEMBLY-163] - In a multiproject environment Assembly  
causes many unneded rebuilds
     * [MASSEMBLY-178] - filtering doesn't read filter files
     * [MASSEMBLY-179] - Assembled jar includes artifact names in path
     * [MASSEMBLY-180] - A bug in artifact filtering ( maven-common- 
artifact-filters )
     * [MASSEMBLY-183] - assembly:attached does not work with filter-  
ERROR: Cannot override read-only parameter
     * [MASSEMBLY-184] - components are not interpolated - i.e., $ 
{params} are not substituted
     * [MASSEMBLY-188] - manifestEntries are not set in resulting jar
     * [MASSEMBLY-189] - plugin not correctly interpolating POM  
variables like project.build.directory
     * [MASSEMBLY-194] - unnecessary dependency expansion regression
     * [MASSEMBLY-195] - unpackOptions ignored
     * [MASSEMBLY-197] - 2.2-beta-1 regression, project artifact no  
longer included in
     * [MASSEMBLY-208] - Assembly plugin does not resolve version  
ranges correctly
     * [MASSEMBLY-210] - repository does not include the parent pom
     * [MASSEMBLY-212] - Assembly Descriptor Schemas (XSD) have wrong  
targetNamespace
     * [MASSEMBLY-214] - java.lang.NullPointerException: version was  
null for junit:junit
     * [MASSEMBLY-221] - Filtering doesn't work when a file matches  
both a <fileSet> and a <file>
     * [MASSEMBLY-222] - 2.2-beta-1 regression in assembly descriptor  
interpolation
     * [MASSEMBLY-223] - 2-nd <exclude> element of  
<dependencySets>:<excludes> doesn't work
     * [MASSEMBLY-225] - Not a v4.0.0 POM
     * [MASSEMBLY-226] - Filters as read-only parameter can break the  
assembly build of a multi-module project
     * [MASSEMBLY-232] - NPE - MASSEMBLY-222 fix broken?
     * [MASSEMBLY-233] - Custom ContainerDescriptorHandler  
integration tests don't work in Maven 2.0.7
     * [MASSEMBLY-234] - Artifacts not deployed
     * [MASSEMBLY-235] - dependencySet ignores dependency management
     * [MASSEMBLY-250] - Trunk of assembly plugin broken and not in  
synch with deployed 2.2-beta2-SNAPSHOT ?
     * [MASSEMBLY-254] - Not a v4.0.0 POM Still an Issue
     * [MASSEMBLY-257] - OutOfMemoryError when assembling large  
binary file
     * [MASSEMBLY-262] - unit fail in trunk on windows (need upgrade  
of plexus-utils)
     * [MASSEMBLY-266] - Property expansion does not work for $ 
{project.build.finalName} in descriptor file
     * [MASSEMBLY-277] - NullPointerException
     * [MASSEMBLY-282] - Fix failing IT no-appendAssemblyId-no- 
classifier

** Improvement
     * [MASSEMBLY-136] - outputDirectory to support absolute paths
     * [MASSEMBLY-142] - Should be able to use artifact version as  
variable in <outputDirectory>
     * [MASSEMBLY-152] - Support Ant token
     * [MASSEMBLY-154] - FileSet does not support filtering
     * [MASSEMBLY-182] - document behavior when two sources selected  
for single archived file
     * [MASSEMBLY-258] - Sync usage guide with Maven standard  
directory layout
     * [MASSEMBLY-261] - Use plexus-archiver 1.0-alpha-10
     * [MASSEMBLY-267] - Configure surefire to redirect test output  
to file
     * [MASSEMBLY-274] - descriptorSourceDirectory should only scan  
for xml files.
     * [MASSEMBLY-275] - Use properties to select IT pom includes
     * [MASSEMBLY-278] - Do not fail on missing descriptors
     * [MASSEMBLY-279] - Small improvement to error messages

** New Feature
     * [MASSEMBLY-73] - Sharing a default assembly descriptor across  
sub modules
     * [MASSEMBLY-243] - Support for patching

** Task
     * [MASSEMBLY-283] - Fix IT dependencySet-unpackedExcludingMetaInf



Enjoy,

-The Maven team

---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john



Re: [ANN] Maven Assembly Plugin 2.2-beta-2 Released

Posted by Mark Diggory <md...@gmail.com>.
We are having problems with mavenn 2.0.8 and maven-assebly-plugin-2.2-beta-2
we can't seem to resolve the new ${modules.artifactId} properties...

for instance...

    <moduleSets>
        <moduleSet>
            <includes>
                <include>*:war:*</include>
            </includes>
            <excludes>
                ....
                <exclude>org.dspace:dspace-oai-webapp</exclude>
            </excludes>
            <binaries>
                <includeDependencies>false</includeDependencies>
                <outputDirectory>webapps</outputDirectory>
               <outputFileNameMapping>${module.artifactId
}</outputFileNameMapping>

fails to return the name of the current module being processed. This is with
a fresh download of maven 2.0.8 and a fresh recreation of my local
repository that I tested today.  All the modules get dumped over top of
eachother and are not separated by their artifactId.  If I remove the
outputFileNameMapping, they do get separated and the documented default

 ${module.artifactId}-${module.version}${dashClassifier?}.${module.extension
}.

gets used appropriately.

thanks for any advice,
-Mark

On Fri, Feb 29, 2008 at 4:04 PM, John Casey <jd...@apache.org> wrote:

> The Maven team is pleased to announce the release of the Maven
> Assembly Plugin, version 2.2-beta-2
>
> This plugin is used to build custom archives, such as those used to
> distribute project releases.
>
> http://maven.apache.org/plugins/maven-assembly-plugin/
>
> You can run mvn -up to get the latest version of the plugin, or specify
> the version in your project's plugin configuration (recommended):
>
> <plugin>
>  <groupId>org.apache.maven.plugins</groupId>
>  <artifactId>maven-assembly-plugin</artifactId>
>  <version>2.2-beta-2</version>
> </plugin>
>
>
> Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-2
>
> (See: http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11126&styleName=Text&version=14027)
>
>
> ** Bug
>     * [MASSEMBLY-121] - Custom manifest attributres are ignored.
>     * [MASSEMBLY-129] - BaseDirectory Ignored When Including a
> Repository
>     * [MASSEMBLY-156] - appendAssemblyId cannot be false
>     * [MASSEMBLY-162] - In a multiproject environment, assembly
> takes wrong dependencies
>     * [MASSEMBLY-163] - In a multiproject environment Assembly
> causes many unneded rebuilds
>     * [MASSEMBLY-178] - filtering doesn't read filter files
>     * [MASSEMBLY-179] - Assembled jar includes artifact names in path
>     * [MASSEMBLY-180] - A bug in artifact filtering ( maven-common-
> artifact-filters )
>     * [MASSEMBLY-183] - assembly:attached does not work with filter-
> ERROR: Cannot override read-only parameter
>     * [MASSEMBLY-184] - components are not interpolated - i.e., $
> {params} are not substituted
>     * [MASSEMBLY-188] - manifestEntries are not set in resulting jar
>     * [MASSEMBLY-189] - plugin not correctly interpolating POM
> variables like project.build.directory
>     * [MASSEMBLY-194] - unnecessary dependency expansion regression
>     * [MASSEMBLY-195] - unpackOptions ignored
>     * [MASSEMBLY-197] - 2.2-beta-1 regression, project artifact no
> longer included in
>     * [MASSEMBLY-208] - Assembly plugin does not resolve version
> ranges correctly
>     * [MASSEMBLY-210] - repository does not include the parent pom
>     * [MASSEMBLY-212] - Assembly Descriptor Schemas (XSD) have wrong
> targetNamespace
>     * [MASSEMBLY-214] - java.lang.NullPointerException: version was
> null for junit:junit
>     * [MASSEMBLY-221] - Filtering doesn't work when a file matches
> both a <fileSet> and a <file>
>     * [MASSEMBLY-222] - 2.2-beta-1 regression in assembly descriptor
> interpolation
>     * [MASSEMBLY-223] - 2-nd <exclude> element of
> <dependencySets>:<excludes> doesn't work
>     * [MASSEMBLY-225] - Not a v4.0.0 POM
>     * [MASSEMBLY-226] - Filters as read-only parameter can break the
> assembly build of a multi-module project
>     * [MASSEMBLY-232] - NPE - MASSEMBLY-222 fix broken?
>     * [MASSEMBLY-233] - Custom ContainerDescriptorHandler
> integration tests don't work in Maven 2.0.7
>     * [MASSEMBLY-234] - Artifacts not deployed
>     * [MASSEMBLY-235] - dependencySet ignores dependency management
>     * [MASSEMBLY-250] - Trunk of assembly plugin broken and not in
> synch with deployed 2.2-beta2-SNAPSHOT ?
>     * [MASSEMBLY-254] - Not a v4.0.0 POM Still an Issue
>     * [MASSEMBLY-257] - OutOfMemoryError when assembling large
> binary file
>     * [MASSEMBLY-262] - unit fail in trunk on windows (need upgrade
> of plexus-utils)
>     * [MASSEMBLY-266] - Property expansion does not work for $
> {project.build.finalName} in descriptor file
>     * [MASSEMBLY-277] - NullPointerException
>     * [MASSEMBLY-282] - Fix failing IT no-appendAssemblyId-no-
> classifier
>
> ** Improvement
>     * [MASSEMBLY-136] - outputDirectory to support absolute paths
>     * [MASSEMBLY-142] - Should be able to use artifact version as
> variable in <outputDirectory>
>     * [MASSEMBLY-152] - Support Ant token
>     * [MASSEMBLY-154] - FileSet does not support filtering
>     * [MASSEMBLY-182] - document behavior when two sources selected
> for single archived file
>     * [MASSEMBLY-258] - Sync usage guide with Maven standard
> directory layout
>     * [MASSEMBLY-261] - Use plexus-archiver 1.0-alpha-10
>     * [MASSEMBLY-267] - Configure surefire to redirect test output
> to file
>     * [MASSEMBLY-274] - descriptorSourceDirectory should only scan
> for xml files.
>     * [MASSEMBLY-275] - Use properties to select IT pom includes
>     * [MASSEMBLY-278] - Do not fail on missing descriptors
>     * [MASSEMBLY-279] - Small improvement to error messages
>
> ** New Feature
>     * [MASSEMBLY-73] - Sharing a default assembly descriptor across
> sub modules
>     * [MASSEMBLY-243] - Support for patching
>
> ** Task
>     * [MASSEMBLY-283] - Fix IT dependencySet-unpackedExcludingMetaInf
>
>
>
> Enjoy,
>
> -The Maven team
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
> rss: http://feeds.feedburner.com/ejlife/john
>
>
>