• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • 4.2.0
    • None
    • None
    • None
    • 4.2.1

      When upgrading a JAR, even if a JS is modify in it, the lastmodify date will be 0 => the hashcode of the minimize transformer will remain the same

      We should be able to compute a better lastModified date for such resources... could be the jar file date?
      Or at least sever startupdate?

      (impl could be done using getHashSalt in MinimizeTransformer...)

          [RUNTIME-3173] Cache issue on files in jar

          What I suspected was the hashcash is correctly modified, but the internal reading of the resources in cocoon:// was still loading the old one

          I cannot reproduce this. modifying a jar do change the hash and the modified is present

          Raphaël Franchet added a comment - What I suspected was the hashcash is correctly modified, but the internal reading of the resources in cocoon:// was still loading the old one I cannot reproduce this. modifying a jar do change the hash and the modified is present

          dates are correct in jar and hash code do change when jar is modified

          Raphaël Franchet added a comment - dates are correct in jar and hash code do change when jar is modified

            raphael Raphaël Franchet
            raphael Raphaël Franchet
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: