|Re: [cross-project-issues-dev] Migrate to EPL 2.0|
Hi,I used https://github.com/javaee/copyright-maven-plugin several times on various repos (including some with 20k+ files). Main benefit of this plugin which I see is that it can be plugged into the build, so once headers are correct, the build can be told to fail if some newly added file contains wrong or no copyright.
thanks, --lukas On 6/25/18 5:43 PM, Ed Merks wrote:
Hi,I wonder if anyone started seriously looking at migrating their project from EPL 1.0 to EPL 2.0?The FAQ says we should: https://www.eclipse.org/legal/epl-2.0/faq.php#h.60mjudroo8e5Also, Wayne suggested that there will be pressure applied, e.g., perhaps a release train participation requirement.But the FAQ doesn't say much about how to do this: https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgwThe instructions are "So, a project can use the new version by simply updating the file headers and notices." But how simple is that really? Just changing all the copyright headers in all the files sounds simple at face value.https://www.eclipse.org/legal/epl-2.0/faq.php#h.q72cnghf29k0 But I have several thousand files!Is everyone doing this or planning to do this manually, or via various forms of scripts that we each author ourselves? Of course we'll all diligently increment every bundle and feature version (by the appropriate amount) remembering to keep the POMs in sync. And we won't overlook the copyright element in each feature. Nor will we overwrite each about.html with the new one (where is the definitive version of that anyway?), accidentally replacing any Third Party Content sections. To me it seems like a lot of work, made error prone by the sheer tedium involved.Perhaps someone else already has some experience to share? Regards, Ed _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top