[MWAR-231] Disable webapp cache by default

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1-beta-1
• Fix Version/s: 2.1
• Assignee: Stephane Nicoll
• Reporter: Stephane Nicoll
• Created: 12/Aug/10 02:07
• Updated: 07/Apr/15 18:37
• Resolved: 12/Aug/10 02:20

Description

In 2.1-alpha-1, an experimental webapp cache was introduced. The purpose was to save the whole list of dependencies being packaged in the war at each run. That way, reading that cache file again allows to detect which dependencies have changed and perform some smart added values such as removing artifacts that were no longer dependencies of the project. A similar feature would be available for SNAPSHOTs where the timestamp version has changed.

Unfortunately, this system is not yet ready for two main reasons:

1. It seems using XStream in certain environment has weird side effect (see MWAR-187)
2. The logic that checks whether or not an artifiact has changed is flawed, leading to unecessary warnings in the log (stating that the artifact has changed while it has not).

Before going further, I think it's safe to disable the functionality by default. A separate issue will be created to resolve theses issues.

Issue Links

• relates to: MWAR-187 regression running war packaging with maven 2.1