[MASSEMBLY-725] Fix phase ordering

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.5.2
• Assignee: Kristian Rosenvold
• Reporter: Kristian Rosenvold
• Created: 31/Oct/14 01:45
• Updated: 11/Nov/14 02:48
• Resolved: 09/Nov/14 06:45

Description

The execution order of the phases is random based on maven version and possibly java version. Documentation on site seems to indicate there is a given precedence, which is wrong.

Fix precedence of phases; this will only affect resolution of "duplicate" elements in the archive

Issue Links

• is depended upon by: MASSEMBLY-478 allow overwriting newer files with older files contained within fileset
• is depended upon by: MASSEMBLY-565 jar-with-dependencies: class from the source in project does NOT override the class in jar dependency
• is depended upon by: MASSEMBLY-373 Support overriding a file found in successive fileSet/dependencySet/file entries
• relates to: MASSEMBLY-655 Archive file resolution does not work as documented
• relates to: MASSEMBLY-726 Fix artifact inclusion/exclusion filtering