One can specify an exact version, 2.0.2.v20181016-2210, or one can
restrict the update site from which you fetch it:
https://download.eclipse.org/cbi/updates/license/2.0.2.v20181016-2210/
So one need not automatically update to any hypothetical future versions...
On 29.11.2023 16:15, Ed Willin
Hi
Yes Ed M's example is much simper and you never have to worry about
updating again.
license-feature="org.eclipse.license"
license-feature-version="0.0.0"
BUT you automatically track every EF license upgrade, so if you need to
review such upgrades you need to reference your own
It's better to use the common license feature (not how Oomph or EMF are
doing it with their own license feature) which is more historical...
I recently improved the README for this:
https://github.com/eclipse-cbi/epl-license-feature
So it's better to look at a simple example like this one:
ht
On Tue, Nov 28, 2023 at 4:30 PM Christian Pontesegger via
cross-project-issues-dev wrote:
> Hi,
>
> I would like to get my license links right in my feature definitions an
> wonder how that works for other projects.
>
> Eg Oomph:
>
> https://github.com/eclipse-oomph/oomph/blob/master/features/org
Hi,
I would like to get my license links right in my feature definitions an
wonder how that works for other projects.
Eg Oomph:
https://github.com/eclipse-oomph/oomph/blob/master/features/org.eclipse.oomph.all-feature/feature.xml
uses %licenseURL and %license
which I expected to be defined in
ht
