[
http://jira.codehaus.org/browse/MNG-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179385#action_179385
]
Milos Kleint commented on MNG-4041:
-----------------------------------
it would be nice to have an option to put a custom caching strategy in place.
With the old 2.1 snapshots, there was a Workspace*someting* component. it was
purged after each call to project resolution. Changing it to timed weak
references I was able to speed up the loading of multiple projects
significantly, while cleaning up in the long run..
> embedder returns stale maven project state
> ------------------------------------------
>
> Key: MNG-4041
> URL: http://jira.codehaus.org/browse/MNG-4041
> Project: Maven 2
> Issue Type: Bug
> Components: Embedding
> Affects Versions: 3.0-alpha-2
> Reporter: Igor Fedorenko
> Fix For: 3.0-alpha-3
>
> Attachments: MNG-4041.diff, staleproject.zip
>
>
> Embedder returns stale maven project state after project's pom.xml changed
> and re-read. This is extremely common scenario when using embedder in IDE
> like m2e. See attached sample project that demonstrates one of many possible
> ways to trigger this problem.
> The problem appears to be related to static (!) MavenProject cache in
> DefaultMavenProjectBuilder, which means that even recreating embedder
> instance is not going to purge state cache entries.
> Also note that using artifact#getId does not provide enough context to
> uniquely identify cached MavenProject instances. This is particularly true
> for IDEs where the same embedder instance is likely to be used to process
> unrelated projects. Cached MavenProject instances should be identified at
> least by the following attributes
> * project artifact id
> * values of all properties
> * all active profiles
> * content of all pom.xml files directly and indirectly involved in
> construction of maven project instance
> * IDE specific state, like m2e "enable workspace dependency resolution"
> * likely more...
--
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
