Re: aede-policy vs. new years

My case is a little more complex in that I do on my development on a
local test machine then upload it (via aedist -bl [due to there being
many changesets in between updates]) to a demo server and once
approved by the client to there production server.... it would be hard
(not impossible I guess [I should look at doing some sed calls maybe])
to do the upload/build/etc. outside of aegis/cook (there are machine
dependent configs, URL user/group names etc {Java makes hard to
externalize this in some cases}, in the code)... the result being that
when I do the first uploads of the year for projects I get aede-policy
complaining about all the source files not just the actually modified
ones and usually due to being lazy/under time pressure I only fix it
in the aedist'ed change and not the development baseline.

A small side question has anyone had problems with "set fingerprint"
and cook not reconizing that implicitly compiled files [javac silently
compiles any referenced classes that are not already compiled]?  If so
is there a way of (without a implicity dependancy scanner like c_incl)
around this without setting  build_time_adjust=true in aegis.conf ?

On Wed, Jan 2, 2013 at 1:18 PM, Pendergraft, Jerry <[email protected]> wrote:
> It will only complain about files modified in a change which of course should have their copyright updated. I set up my projects so an aede-policy run is part of a build and thus catches em early on. And yes Jan is annoying
>
> Sent from my iPhone
>
> On Dec 31, 2012, at 23:33, "Aryeh Friedman" <[email protected]> wrote:
>
>> Does anyone have a easy way of making sure that aede-policy does not
>> complain in mass on copyright years right after new years (I do not
>> want to do aefa foreign-copyright=true either... I prefer to actually
>> have the right copyright notice)
>> _______________________________________________
>> Aegis-users mailing list
>> [email protected]
>> http://lists.auug.org.au/listinfo/aegis-users
>
> This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system.