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:
https://github.com/eclipse-orbit/orbit-legacy/tree/main/features/org.eclipse.orbit.legacy-feature
On 28.11.2023 15:29, 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.eclipse.oomph.all-feature/feature.xml
uses %licenseURL and %license
which I expected to be defined in
https://github.com/eclipse-oomph/oomph/blob/master/features/org.eclipse.oomph.all-feature/feature.properties
but they are not. Also a license.html file is missing in the repo which
I remember was needed (at least some time ago)
Are these files patched by tycho somehow? If yes, how does this work?
thanks
Christian
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev