I've used another email not subscribed to this list so forwarding it.

---------- Forwarded message ---------
From: Александър Куртаков <[email protected]>
Date: Mon, Feb 8, 2021 at 10:40 AM
Subject: Re: [eclipse-dev] Is anyone still using Copyright tool?
To: General development mailing list of the Eclipse project. <
[email protected]>
Cc: issues, Cross <[email protected]>


Let's move any discussion to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=571007 actually to not spam
everyone.

On Mon, Feb 8, 2021 at 10:38 AM Aleksandar Kurtakov <[email protected]>
wrote:

> So far single user. We are about to proceed with removal. It can still be
> installed from old Eclipse releases p2 sites.
> Ed, let me know if you have alternative proposal how to progress on the
> other topics or if you want to move the code to one of your repos and need
> few days for it.
>
> On Fri, Feb 5, 2021 at 6:59 PM Aleksandar Kurtakov <[email protected]>
> wrote:
>
>> Question is about [1] being still used by anyone. I haven't seen anyone
>> using it/running it on git repos like it has been in the past. Changing
>> copyright year in every file is not mandatory for Eclipse TLP since 2016
>> [2] and has never been mandatory for other projects AFAIK.
>> What I look for is removing this part of Eclipse Releng plugin to gain
>> the following benefits:
>> 1. Drop dependency on EGit in Eclipse Platform and thus circular build
>> dependency.
>> 2. Point 1 will allow to to build Eclipse Platform p2 repo in a way that
>> includes all transitive dependencies [3]
>> 3. Point 2 will allow to switch third-party dependencies to require
>> rather than include and thus support version ranges.
>> 4. Point 3 will allow updates of third party dependencies for security
>> reasons to be far simpler as currently it's a terrible experience [4]
>> 5. Point 3 will simplify updates of third party dependencies in Eclipse
>> Platform releng as touching features should be far less frequent event just
>> cause exact version is hardcoded in includes.  e.g. [5]
>>
>> The potential benefit is quite big so please come up with proposals
>> how/what to do and still improve our procedures.
>>
>> [1]
>> https://wiki.eclipse.org/Development_Resources/How_to_Use_Eclipse_Copyright_Tool
>> [2] https://wiki.eclipse.org/Eclipse/PMC/Minutes_2016
>> [3]
>> https://www.eclipse.org/tycho/sitedocs/tycho-p2/tycho-p2-repository-plugin/assemble-repository-mojo.html#includeAllDependencies
>> [4] https://www.eclipse.org/lists/tycho-user/msg08879.html
>> [5]
>> https://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/?id=58e5c221bfc493e40d499f58c93a17cc14d061ac
>>
>> --
>> Alexander Kurtakov
>> Red Hat Eclipse Team
>>
>
>
> --
> Aleksandar Kurtakov
> Red Hat Eclipse Team
> _______________________________________________
> eclipse-dev mailing list
> [email protected]
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/eclipse-dev
>
_______________________________________________
eclipse-dev mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-dev


-- 
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to