Re: [technology-pmc] Works with dependency and limitations

[Wayne Beaton <wayne@xxxxxxxxxxx>]

I think users must be aware that they are installing those dependencies on purpose and that they are not coming from Eclipse.org.

Agreed. As long as the users are given the opportunity to agree to the license themselves (which is the case via the p2 installer), then you're okay.

They don't do quite the same thing, but I think that this is fundamentally similar to what the Subversive project does.

Wayne

On 18/03/16 05:27 AM, Gunnar Wagenknecht wrote:

Hi Christian,

I probably missed it due to EclipseCon. Thanks for the reminder.

Anyway, I do think that the use case of developing the adapters at Eclipse.org while not distributing the interpreters is intended by works-with dependencies. It's fine to have the dependency in your target platform. You just need to make sure that those dependencies never show up in the project downloads area. I think you also must ensure that they cannot be downloaded from your projects Hudson server, i.e. you would need to revoke anonymous user access to your JIPP build job workspaces.

The remaining question of referencing external p2 repositories in features so that p2 can install dependencies automatically is difficult. I think users must be aware that they are installing those dependencies on purpose and that they are not coming from Eclipse.org. Is that the case?

-Gunnar 

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation