You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2010/08/12 09:08:32 UTC
[jira] Created: (MWAR-231) Disable webapp cache by default
Disable webapp cache by default
-------------------------------
Key: MWAR-231
URL: http://jira.codehaus.org/browse/MWAR-231
Project: Maven 2.x WAR Plugin
Issue Type: Task
Affects Versions: 2.1-beta-1
Reporter: Stephane Nicoll
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MWAR-231) Disable webapp cache by default
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MWAR-231.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.1-beta-2
webapp cache disabled.
> Disable webapp cache by default
> -------------------------------
>
> Key: MWAR-231
> URL: http://jira.codehaus.org/browse/MWAR-231
> Project: Maven 2.x WAR Plugin
> Issue Type: Task
> Affects Versions: 2.1-beta-1
> Reporter: Stephane Nicoll
> Assignee: Stephane Nicoll
> Fix For: 2.1-beta-2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MWAR-231) Disable webapp cache by default
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MWAR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MWAR-231 started by Stephane Nicoll.
> Disable webapp cache by default
> -------------------------------
>
> Key: MWAR-231
> URL: http://jira.codehaus.org/browse/MWAR-231
> Project: Maven 2.x WAR Plugin
> Issue Type: Task
> Affects Versions: 2.1-beta-1
> Reporter: Stephane Nicoll
> Assignee: Stephane Nicoll
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira