I changed a class which is under the license Apache License Version 2.0. According to the license - for redistribution of the changed version I should specify changes in a class.

Notification of changes should be stored in block with a copyright? How it should look like?

  • 3
    Closely related to Apache 2.0 license - NOTICE, CHANGELOG, specifically sub-question #2. (The answer there appears to be "Add your own copyright notice to the header". In particular, you only need to note that changes exist in each file, not to enumerate a list of particular changes.) I think this question is specific enough to merit a separate answer and not be closed as a duplicate. – apsillers Sep 2 '16 at 15:39

Notification of changes should be stored in block with a copyright? How it should look like?

The apache license is both clear and a tad vague and not very prescriptive for this:

4. Redistribution. You may reproduce and distribute copies of the
   Work or Derivative Works thereof in any medium, with or without
   modifications, and in Source or Object form, provided that You
   meet the following conditions:
  (b) You must cause any modified files to carry prominent notices
      stating that You changed the files; and

Here if I modify the sources.... a notification comment would not end up in compiled Java class files or course: I would need to handle both source and binaries somehow.

For this, I would do the following to meet both the spirit and the letter of the license (and this may be a tad more than strictly needed):

  1. In the source, I would add a note in the header comment stating that I modified the code, with a rough date and possibly a high level description of the modification. Doing that in a header comment at the top would be rather prominent to me. (Stating a date and the nature of the modification is not strictly needed, but I feel this is the right thing to do). It can look like anyway you want: the license does not say anything on the format (which is a good thing IMHO).

  2. If the source did not had an Apache notice, I would add one as a comment header too. (even though this is may not be clear in the license, if the copyright/notice was missing I would add this for clarity and avoid any ambiguity)

  3. If there was a NOTICE, I would mention there that the code was modified by me too, so this would be even more prominent. (even though this is may not be strictly needed by the license). If there were none, I would create one, so I could bundle it with the source and binaries. (even though this is may not be strictly needed by the license if there was no notice in the first place)

  4. Finally I would ensure the license and notice file both end up in my sources and binaries redistributions (if I were to redistribute them).

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.