You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Phillips (JIRA)" <ji...@codehaus.org> on 2010/08/03 11:12:32 UTC
[jira] Updated: (MANTTASKS-200) cacheDepedencyRefs not compatible
with ant or antcall tasks
[ http://jira.codehaus.org/browse/MANTTASKS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Phillips updated MANTTASKS-200:
-------------------------------------
Attachment: build_with_antcache.xml
I've just found the cache attribute on path (new in ant 1.8). This therefore allows the path to be cached in ant instead. Attached is an example (build_with_antcache.xml) showing that usage - caching the artifact:dependencies path.
Since this is a good workaround I would change the priority to minor if I could!
> cacheDepedencyRefs not compatible with ant or antcall tasks
> -----------------------------------------------------------
>
> Key: MANTTASKS-200
> URL: http://jira.codehaus.org/browse/MANTTASKS-200
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
> Affects Versions: 2.1.1
> Reporter: Peter Phillips
> Attachments: build.xml, build_with_antcache.xml, build_with_cache.xml
>
>
> Adding cacheDependencyRefs to the artifact:dependencies task changes the scope of declared references.
> Attached are two ant build files identical apart from the first (build.xml) has no caching, the second (build_with_cache) with cache set to true.
> With caching turned off the test.path is set correctly for the build2 antcall, set to log4j.
> With caching turned on, the test.path is not remembered for the build2 antcall, even though inheritRefs is set to true. Instead it reverts to the original test.path fileset declaration instead.
> Unfortunately I have found that cacheDependencyRefs is required, as otherwise the permanent generation requirements get huge (in my case I gave up after allocating 500mb of perm gen to ant).
--
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