Hi all,

I'd like to propose that we release both the assembly plugin and one of its shared-component dependencies: maven-repository-builder. See below for more information on what's included in these releases. I have two staging repositories for these projects:

maven-assembly-plugin:


maven-repository-builder:



You can try them out using the following settings.xml snippet:

  <profiles>
    <profile>
      <id>maven-assembly-plugin.stage</id>
      <repositories>
        <repository>
          <id>mrb.stage</id>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
        <repository>
          <id>map.stage</id>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>map.stage</id>
          <snapshots>
            <enabled>false</enabled>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
  <activeProfiles>
    <activeProfile>maven-assembly-plugin.stage</activeProfile>
  </activeProfiles>


Let the voting begin! +1/+0/-1, 72 hrs.

Thanks,

John



------

The main improvement in the repository builder is inclusion of parent POMs, and some improvements to snapshot handling (though this may not be complete yet). I'm attaching the SVN log for more information about these changes.

As for the assembly plugin, there have been quite a few changes in the last nine months or so:



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


** 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-256] - Regression: pom properties are no longer expanded in descriptor.
    * [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




---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org

------------------------------------------------------------------------
r487848 | fgiust | 2006-12-16 13:16:50 -0500 (Sat, 16 Dec 2006) | 1 line

[maven-release-plugin] prepare for next development iteration
------------------------------------------------------------------------
r525357 | brianf | 2007-04-03 22:21:14 -0400 (Tue, 03 Apr 2007) | 1 line

setting the svn:ignore to match the plugins config folder
------------------------------------------------------------------------
r543255 | jdcasey | 2007-05-31 16:57:44 -0400 (Thu, 31 May 2007) | 1 line

[MASSEMBLY-210] Including the ancestry of the current project in the repository.
------------------------------------------------------------------------
r546941 | jdcasey | 2007-06-13 12:07:43 -0400 (Wed, 13 Jun 2007) | 1 line

Bumping plexus-maven-plugin version to get component requirements without the 
'default' role hint when role-hint is unspecified...this is necessary to work 
with maven-artifact, which doesn't specify a role-hint for 
DefaultArtifactFactory's definition in its components.xml
------------------------------------------------------------------------
r547146 | brett | 2007-06-14 02:41:58 -0400 (Thu, 14 Jun 2007) | 3 lines

align parents to latest release (snapshot has nothing significant other than 
SCM adjustments)
manually set all SCM locations since inheriting from a release will position it 
under the tag which is not correct

------------------------------------------------------------------------
r548374 | jdcasey | 2007-06-18 10:56:37 -0400 (Mon, 18 Jun 2007) | 1 line

Attempting to fix assembly of snapshot artifacts and use POM files from parent 
MavenProject instances where possible. This may not be complete, but wanted to 
get this in before it gets stale.
------------------------------------------------------------------------
r548510 | jdcasey | 2007-06-18 18:25:41 -0400 (Mon, 18 Jun 2007) | 4 lines

OPEN - issue MASSEMBLY-210: repository does not include the parent pom 
http://jira.codehaus.org/browse/MASSEMBLY-210

Fixing NPE when copying a parent-POM whose MavenProject.getFile() returns null.
------------------------------------------------------------------------
r548524 | jdcasey | 2007-06-18 19:00:21 -0400 (Mon, 18 Jun 2007) | 1 line

Adding the beginnings of a testing infrastructure for MASSEMBLY-210.
------------------------------------------------------------------------
r548535 | jdcasey | 2007-06-18 19:52:17 -0400 (Mon, 18 Jun 2007) | 1 line

Adding new unit test for MASSEMBLY-210. It doesn't work yet, even to the extent 
that it should without fixing MASSEMBLY-210, so I've excluded it in the POM's 
surefire config.
------------------------------------------------------------------------
r550033 | snicoll | 2007-06-23 08:20:54 -0400 (Sat, 23 Jun 2007) | 1 line

Fixed the name of the test to exclude.
------------------------------------------------------------------------
r550042 | snicoll | 2007-06-23 09:24:54 -0400 (Sat, 23 Jun 2007) | 1 line

Fixed john's test with the remote repository. Still need to resolve the maven 
project properly.
------------------------------------------------------------------------
r553960 | jdcasey | 2007-07-06 13:10:55 -0400 (Fri, 06 Jul 2007) | 1 line

first unit tests succeeds now.
------------------------------------------------------------------------
r553974 | jdcasey | 2007-07-06 13:59:03 -0400 (Fri, 06 Jul 2007) | 1 line

Adding unit test that is failing...it's commented out in the unit test source, 
so it won't run.
------------------------------------------------------------------------
r554077 | jdcasey | 2007-07-06 18:19:23 -0400 (Fri, 06 Jul 2007) | 1 line

[MASSEMBLY-210] This fixes inclusion of parent poms, for the current project 
and dependencies...both in cases where the current pom's parent is in the 
repository, and in the filesystem.
------------------------------------------------------------------------
r555863 | jdcasey | 2007-07-13 00:00:07 -0400 (Fri, 13 Jul 2007) | 1 line

Fixing problem with a field in the project builder that isn't there in 
2.1-snapshot...just trapping the NoSuchFieldException.
------------------------------------------------------------------------
r564256 | jdcasey | 2007-08-09 12:12:37 -0400 (Thu, 09 Aug 2007) | 1 line

Adding managed-version map, taken from maven 2.0.7 source. We can remove this 
once again, once we don't have to support maven < 2.0.7.
------------------------------------------------------------------------

Reply via email to