Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
[MASSEMBLY-446] apache-source-release-assembly DOES NOT exclude target/** in maven-remote-resources-plugin build
upgrade parent version to ensure source-release is automatic.
bump to new parent POM, and remove one-off source-release assemblies
[MASSEMBLY-385] upgrading file/fileset filtering to use maven-filtering
o Used a less subtle workaround for MNG-1323
o Added workaround for MNG-1323 that affects maven-eclipse-plugin during CI builds on the grid
merging changes from maven-assembly-plugin-2.2-beta-4 branch through r780691 (the release on that branch).
bumping the trunk. the beta-4 release will be from the branch that was copied from the beta-3 tag.
used http://maven.apache.org/xsd/* for schema location
o Inherited from maven-plugins:13
use the latest parents
Removed the contributors section. Petar Tahchiev used to be contributor, but was voted a developer.
Adding Petar Tahchiev to contributors. He added a lot of patches that made 2.2-beta-3 possible.
o Updated all plugins to use maven-invoker-plugin:1.3 to workaround MNG-3284 and bogus CI failures
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.2-beta-3
bumping to staged release versions of maven-archiver and maven-common-artifact-filters.
update plexus-archiver and plexus-io versions.
[MASSEMBLY-151][MASSEMBLY-159] Cleaning up documentation, especially as it relates to differences between mojos and for dealing with moduleSet/binaries.
[MASSEMBLY-75][MASSEMBLY-285][MASSEMBLY-238] fixing and adding integration tests. The only potentially outstanding issue of these might be MASSEMBLY-75, which will have a test added to plexus-archiver to check it.
updated plexus-io to 1.0-alpha-3-SNAPSHOT since it is a dependency of plexus-archiver 1.0-alpha-11-SNAPSHOT
o Use released version of plexus-interpolation.
o Formatted/reordered POM
o Inherited from maven-plugins:12
[MASSEMBLY-306] Adding integration test to verify that NPE is fixed.
[MASSEMBLY-285] Update to latest snapshot of plexus-archiver (1.0-alpha-11-SNAPSHOT), and enabled the integration test.
[MASSEMBLY-354] Fix behavior concerning useTransitiveFiltering == true and include patterns that contain wildcards.
[MASSEMBLY-351] Realign assembly-descriptor interpolation with outputDirectory/outputFileNameMapping interpolation, and use reflective interpolator instead of model serialization/deserialization (based on 2.1.0-M1 work, but generalized into plexus-interpolation). This fixes project.xxx expression interpolation. Also including an integration test.
[MASSEMBLY-331] Fixing order of operations for expression interpolation in outputDirectory and outputFileNameMapping. Patches applied, with minor modifications. Also, replaced deprecated plexus-utils interpolator references with updated library from plexus-interpolation v1.5. Submitted by: Petar Tahchiev
o Re-enabled help mojo generation
Remove aspectj dependency.
Correcting excludes for massembly-285
Removing the sub-project for the handlers and lifecycle mappings, as this isn't needed for now (it was never released). Also, cleaning up the integration tests to work without the component-it-plugin, which has never graduated the sandbox and may not be the best way to setup plugin testing environments.
o Added SCM information (compare http://www.nabble.com/Re%3A-%3Cscm%3E-element-in-plugin-POMs-p18934198.html)
o Added project description
o Reordered POM
o Synced id and activation of integration-tests with core ITs
Remove plugins versions already defined in parent
Align activation properties for integration-tests profile because we cannot setup it in the parent (see MNG-3228)
Use the same activation rule for all integration-tests in plugins builds (-Dintegration-tests=true)
o Removed distribution management section (to be inherited from parent to allow customization for CI)
o Disabled helpmojo generation to workaround failures during IT preparation
Try to use the 12-SNAPSHOT parent
[MASSEMBLY-245] Manifest Section configuration does not work properly o Upgrade to latest maven-archiver.
Bumping all parent versions to 11, to allow deployment to alternative locations.
[MASSEMBLY-256] Adding support for 'project.' expressions in outputDirectory, outputFileNameMapping, and outputDirectoryMapping.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.2-beta-2
Bumping to released versions for plexus snapshot deps.
[MASSEMBLY-267] Applied surefire config to limit test output to the console. Submitted by: Paul Gier
[MASSEMBLY-275] Configuration to make it easier to narrow the set of ITs to run, for debugging purposes. Submitted by: Paul Gier
[MASSEMBLY-212] Fixing this, though the namespaces need to be filtered for ${mdoVersion} in the future, and I'm not completely sure why it didn't work when I tried to run the resources plugin over the src/main/mdo directory to do this...will have to investigate further.
put the integration-test patterns back to normal...
[MASSEMBLY-282] Check for the case where an artifact to be added to the assembly points to the same file that the assembler is meant to create. This happens when appendAssemblyId == false and classifier == null, in cases where the assembly is meant to re-create the standard output artifact from a build, but that standard output artifact should be included in the assembly. Patch submitted by: Paul Gier NOTE: I modified the patch to copy the conflicting file to a temporary location, then include it from there, rather than skipping it.
Fixing ITs, bumping plexus-archiver to 1.0-alpha-10 so I could fix a problem exposed by the ITs that was in the chmod command in p-a, and removing default file modes in the .mdo files, so files are only altered if the file mode is provided (at least that's the theory, though I think p-a brute-forces this atm).
Fixing two of the failing ITs.
Use released versions of maven-shared-io and maven-common-artifact-filters.
o fixed license header o removed mailing list
[MASSEMBLY-262] unit fail in trunk on windows (need upgrade of plexus-utils) upgrade to last p-u 1.4.9 upgrade prerequisites to maven 2.0.6 upgrade surefire version to ensure unit used this p-u version
[MASSEMBLY-233] Fixing by splitting the IT builds to separate the handle-def build from the assembly build using two executions of the invoker plugin fired from the IT parent pom.
Removing some sysout statements from the main codebase, and adding some debugging aspects for performance, stats, and tracing info, which can be enabled by building with -Paspects (the aspects profile enabled). You'll also have to use various system properties (currently the fastest solution I could find) to trigger the various types of output.
[MASSEMBLY-194] Adding useTransitiveDependencies flag to dependency-sets, set to try by default (process transitive dependencies, or subject them to useTransitiveFiltering flag).
Fixing unit test for new debug output (still making these things more resilient to this sort of change), and disabling the custom componentDescriptorHandler stuff until I can get it to build in maven 2.0.x.
Setting integration tests to run with debug == true, so we can tell what messed up from the build logs.
[MASSEMBLY-222] Sorry for the huge commit. This rearranges the integration tests to pull from local repo to the testing local repo where possible, and copies the test projects to target/test-classes before running, to avoid pollution of the sources. It also changes the interpolation of outputDirectory and outputFileNameMapping, such that pom.artifactId refers to the main project being built, while artifact.artifactId refers to the dependency currently being processed (and module.artifactId is a synonym for artifact.artifactId when processing modules. Also adjusted the unit tests to be less fragile in the face of minor changes in the call structure to things like Artifact instances, to reduce the rippling failures from minor debug statements.
Updated to use newest snapshot of maven-common-artifact-filters.
Adding distributionManagement...apparently, it's missing in the POM hierarchy.
Fixing assembly-descriptor and assembly-component handlers/lifecycles to once again have a classifier, and changing the associated attach mojos to attach these descriptors to the main project artifact, which is now the pom itself...rather than setting the main project artifact to the descriptor, which leaves off the classifier.
Bumping plexus-archiver to 1.0-alpha-9 (released).
Fixing filtering of file entries and mixed environments of files and fileSets.
Test and implementation of a custom container-descriptor processor.
Bumping plexus-archiver version for [MASSEMBLY-213] testing.
Adding another repository test, which is not yet working...so it's also excluded explicitly in the integration-test build until we can fix the maven-repository-builder.
All ITs run, and I'm including a new feature to allow assembly descriptors and assembly-components to be deployed then resolved again as artifacts. This enables reuse of standard assembly descriptors/components. There is a new IT to test it, and all other ITs pass, including the repository-assembly now (due to fixes in the maven-repository-builder).
[MASSEMBLY-121] Applying fix from Paul Gier.
Adding snapshot repo for integration-testing.
bumping version of the plexus-maven-plugin to fix an issue with this build not working with maven-2.1-snapshot.
Updating maven-repository-builder dep so it'll include the ancester POMs of the current project.
Fixing resolution of dependencies that have legacy POMs, and excluding the repo-assembly IT until it can be fixed.
Fixing repository-assembly IT so it runs correctly...though it now fails (this is related to a new JIRA).
Fixing deps according to dependency:analyze.
[MASSEMBLY-194] Adding useTransitiveFiltering flag to dependencySets (default value == false). When false, includes/excludes apply only to the current artifact, not to the list of artifacts that bring this artifact in transitively. When true, the transitive path of the current artifact is taken into account for filtering includes/excludes. By default, backward compatibility with version 2.1 of the assembly plugin means we have to set this to false.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.2-beta-1
Fixing plexus-archiver 1.0-alpha-8 to not pollute the classpath with plexus-component-api, and avoid IncompatibleClassChangeError on getLogger().
setting a p-c-d dep to 1.0-alpha-9 to try to force the issue.
Adding utility from plexus-utils 1.4 so I can revert the dep on plexus-utils to 1.1 for maven 2.0.x compat.
Update parent version to 8, as 8-SNAPSHOT is never deployed and 8 is released
Update dep on plexus-archiver from 1.0-alpha-8-SNAPSHOT to released 1.0-alpha-8 ('latest snapshot')
o Update the dependency on modello so that MASSEMBLY-169 can make use of the new features in there.
- move plugin-plugin out of 'reporting' for plugins. It's a required part of the site, and does not cause any issues with the reactor or site generation - update to snapshots
o updating to latest released parent
o updating to latest release parent
updated testing and shared components that have been released
updated file management to 1.1 from 1.1-SNAPSHOT because it was released.
plexus-utils version 1.4-alpha-1 released, remove snapshot
Adding proper staging of the plugin to a test-only local repository.
Split out artifact filters and repository builder into separate projects for reuse elsewhere, and started using maven-test-tools over the original mock controls developed here.
[MASSEMBLY-143] Removing classifier from being added to the filename unless it's specified as part of the expression...this was effectively adding the classifier twice when it was specified in the expression...
Added project descriptor-ref, which is a project's sources including pom.xml etc...also, added tests for bin and src descriptorRefs. I think documentation is all that's left before a release.
Remove svn:executable from xml files
update all parents
Fixing component.xml merging and inclusion into the assembly.
Fixing jar-with-dependencies descriptor-ref to include the current project's classes.
Fixing jar-with-dependencies descriptorRef, and adding IT to verify that it's correct.
Adding more integration tests for default excludes, along with modifications to restore some backward-compat in moduleSources.
Update to latest maven-archiver
Bumping plexus-utils dep version up to 1.3-SNAPSHOT to handle envars in a case-insensitive manner.
Fix plexus component descriptor generation
Adding aliasing for sar dependencies, along with simple copying of pom deps
Adding ability to specify <dependencySets/> within a <moduleSet/> to satisfy MASSEMBLY-99, and also enabling skipping of pom dependencies when adding binaries to the assembly.
Adding codehaus snapshots repository for plexus-archiver resolution.
Adding profile to do integration testing, using two new plugins in the sandbox: the invoker plugin, and the plugin-test plugin (which stages a plugin into the local repo for ITs to run).
Adding another functional/integration test.
working some kinks out of the system, and adding a new IT, for eventual use with the new maven-invoker-plugin.
Forgot to include the plexus CDC in the build.
Fixing artifactId from the one I was using in the refactor branch.
[MASSEMBLY-128] Merging from refactor branch.
PR: MASSEMBLY-122 - made the plugin docck-compliant - edited the descriptions inside the modello files - edited some of the parameter descriptions - added an faq page - added some single project examples
MNG-2460: Incorrect POM inheritance for plugins Added missing <issueManagement/> and <mailingLists/> tags in pom.xml
update archiver version
Remove exclusion as it prevents compiling
[MASSEMBLY-120] Added implementation of filtering for <binaries/> inside of <moduleSet/> in the assembly descriptor. Correct usage is same as for dependencySet includes/excludes. Also, altered the pom.xml to use maven-archiver 2.0.4, to enable development to continue prior to the release of Maven 2.1. It seemed to build fine with tests, despite a comment to the contrary in the pom.
[MWAR-34, MJAR-38] use the latest archiver to correct issues with the extension in the manifest
Adding documentation...not quite ready to publish yet.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.1
PR: MASSEMBLY-88 Updated the pom to require 2.0.4 for the repository to work. Finished moduleSet test cases and added a repository test case
use the released testing harness
Updating plexus-archiver version to 1.0-alpha-6.
[MASSEMBLY-29] Re-adding module-source archiving alongside module-binary archiving...had to modify the binary aspect of the moduleSet into a sub-element called <binaries/>, which is a sibling of the new <sources/> sub-element.
workaround bug in Maven
changed the version plexus-utils from 1.2-SNAPSHOT to 1.1
put back writer
another writer to remove
- fix bug in the classifier appendage when there is no extension - clone the artifact filters so that they can include/exclude with a full dependency conflict ID as well - remove generated xpp3 writer for model
Fixing tests, and adding code for module source inclusion back to the plugin, in a different way...will add tests next.
PR: MASSEMBLY-88, MASSEMBLY-14 Fixed MASSEMBLY-14 by introducing a new assembly element <moduleSet> which works like a <dependencySet>. I deleted unused methods/parameter and need not deprecate them bec they have not been released yet. Added some test harness classes for testing the processing of <dependencySet>.
[MASSEMBLY-89] Adding unit tests. Cannot reproduce error (yet).
PR: MASSEMBLY-88 Added test harness in pom and added one passing min configuration test for the unpack goal. Also, fixed a bug when there are more than 3 chars in an artifact file's extension.
[MASSEMBLY-77] add the ability to assemble a maven repository
PR: MASSEMBLY-64, MASSEMBLY-74
Submitted By: Napoleon Esmundo Ramirez
Reviewed By: Allan Ramirez
-when assembling a 'jar-with-dependencies', it strips the security files (*.RSA, *.DSA, *.SF) and updates the uberjar's MANIFEST.MF with the something the user provided (using ${project.build.plugins.plugin.configuration.achive.manifestFile}) or as specified in the configuration (${project.build.plugins.plugin.configuration.achive.manifest}). If no MANIFEST.MF is specified, a default is generated by plexus.
remove duplicate entries
adjust parent POMs
PR: MASSEMBLY-40 -Interpolate project expressions in the assembly descriptor
o Upgrading to the latest plexus-archiver snapshot to get the chmod'ing directory archiver.
Allow multiple descriptors to share sub-assemblies. MASSEMBLY-62
PR: MASSEMBLY-57 Add XSD to Modello generation, documentation edits
[MASSEMBLY-53] upgrade plexus-archiver for a fix
PR: MASSEMBLY-1 allow specification of a manifest for jar/war assemblies
Updating poms to change dependencies on 2.0.1-SNAPSHOT info to 2.0.1 (parent-poms, and a couple references to maven-archiver).
Move download report to plugin\sandbox according this thread: http://www.nabble.com/svn-commit%3A-r322514---in-maven-components-trunk-maven-plugins-maven-assembly-plugin%3A-.-src-main-java-org-apache-maven-plugin-assembly-src-main-resources-src-site-apt-src-test-src-test-projects-src-test-projects-assembly-plugin-test1-src-test-pr...-t413831.html#a1625891 Deleted project test case.
move plugins
PR: MNG-1274 Submitted By: Jerome Lacoste Reviewed By: John Casey Applied patch. Thanks, Jerome!
rolling back version of plugin parent, to keep this compatible with 2.0 release of maven-project...any API changes for maven-project will have to go in a later release of the assy plugin.
Bumping Plugin-Parent version to 2.0.1-SNAPSHOT to reference API changes to MavenProjectHelper, and changing maven-assembly-plugin's pom to reference that new parent POM.
MNG-796: Added a download report
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.0
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.0-beta-2
update snapshot
update versions in plugins
set necessary prereqs and exclusions
PR: MNG-962 unify defaults excludes
o update group o update site.xml
PR: MNG-940 Submitted by: Dan Tran Reviewed by: Brett Porter use the plexus archiver manager for unpacking and packing to simplify and expose all archivers
use released versions
better exception handling
PR: MNG-916 ensure RELEASE is not selected as is
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release maven-assembly-plugin-2.0-beta-1
update dependency and parent versions
o Put modello-maven-plugin under dependencyManagement and chose version 1.0-alpha-5-SNAPSHOT for all so they're all the same. o Updated modello plugin invocations in all poms to by adding execution elements and fixing goals section to get rid of deprecated notation. o Removed dependency on modello-core in maven-plugin-tools; it seems it was there because maven-plugin-tools-java used StringUtils from modello - changed that to use the plexus-utils version. o Reversed commons-cli version back to 1.0 (brett asked me to, a few days back). o Updated all models to use fully qualified classnames - do not assume java.util.* is included! (it won't be anymore from modello 1.0-alpha-5-SNAPSHOT onward). o Added some <?xml processing instructions to some models that didn't have them - vim now recognizes these files as XML (so I get syntax highlighting :))
o Fixed tabs -> spaces (sorry, makes diff hard to read) and some codingstyle issues. o Modified model: added a 'BaseSet' type as a basetype for DependencySet and FileSet; it contains fileMode and directoryMode to work with the new plexus-archiver. o Bumped plexus-archiver version to 1.0-alpha-2-SNAPSHOT. o Added support for actually using fileMode and directoryMode. (tested this with a modified maven-core assembly descriptor, not committed as a test though).
Applying patch from Jason Grant for unpacking assemblies and for attaching assemblies as attached artifacts - Thanks, Jason
MNG-477: Trying to unpack none jar file
PR: MNG-596 add XSD definition to m2 poms and archetypes
Update all versions to beta-1-SNAPSHOT
Resolving: MNG-495 o Pressing [ENTER] at a plugin update prompt should result in the plugin being registered, as indicated by the prompt. o Use CLI switch '--no-plugin-updates' to suppress usage of the plugin registry o Use CLI switch '--update-plugins' to force updated/resolved plugin versions to be registered o Neither of these has a short CLI option, since we're starting to run out of sensible char options for these types of things.
refactoring of the resolveTransitiveDependencies call. simplified by removing a bunch of duplicated code in addArtifacts - no need to merge, you have the full list. separated the original artifacts (dependency artifacts) from the resolved artifacts (getArtifacts)
update parent references to get access to the ci settings
bump versions
use released versions
update to released versions
set consistent versions
update to latest modello plugin versions
update for the times
revert version of plugin
remove unused classes, identical to others in configurator
add back packaging
Initial revision
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |