Hi Piotr,

 "If option a - mean avoid caching svg.js file - It is not a problem I know how
to do this for this file and it can be downloaded for each build."

yes, the idea here was to avoid caching the download in the
maven-download-plugin's own cache. I did not know if there was an option to
do with in the
That sounds great (at least for me, I am not concerned about the caching
aspect, but others might be)

for
" b) We are downloading this file to target/downloads/svg.js - Do you mean
changing that location and patch that file in the new location ?"

I don't mean changing the download location, but copying the downloaded
file to a separate location and patching it in a different location.
The idea is that if the maven-download-plugin is caching the file after it
has been patched (and it does seem to happen sometimes, perhaps only
rarely) from the original download location, then copying and patching it
in a different location would avoid the possibility of caching a patched
file from the original download location.

There may be other options to fix the problem I observed  Another option
might be to delay the patching of the downloaded file (maven has build
phases and I notice the patch is in 'validate', same as the download) I did
wonder if it might be possible to defer the patch to a later phase
(assuming any caching activity might then always happen first), but I do
not know enough about this.


Also it looks like we are using version 1.2.1 of the download plugin, and
current version is 1.3.0. I checked the commit history between releases and
there was at least one cache-related commit [1]. A plugin version change
might be worth considering as well, but I am not sure if it will address
the issue.

-Greg



1.
https://github.com/maven-download-plugin/maven-download-plugin/compare/1.2.1...master



On Fri, Jun 16, 2017 at 1:39 AM, piotrz <piotrzarzyck...@gmail.com> wrote:

> Hi Greg,
>
> In your points "a" and "b" I'm not sure what do you mean.
>
> If option a - mean avoid caching svg.js file - It is not a problem I know
> how to do this for this file and it can be downloaded for each build.
>
> Option b) We are downloading this file to target/downloads/svg.js - Do you
> mean changing that location and patch that file in the new location ?
>
> Thanks,
> Piotr
>
>
>
> -----
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.2333347.n4.nabble.com/VOTE-Release-Apache-Flex-
> FalconJX-0-8-0-RC1-tp62271p62410.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Reply via email to