This package actually has no proper source "code", since it's purely an aggregate to pull in other Apache Batik Maven modules. The source therefore is the pom file:
https://repo1.maven.org/maven2/org/apache/xmlgraphics/batik-all/1.17/batik-all-1.17.pom
I'm not entirely sure why this feature suddenly shows up in Dash, as it is not being used/referenced at all. This is the result of a dependency bump of Tycho from 4.0.4 to 4.0.6, so it might be related to https://github.com/eclipse/dash-licenses/issues/318
In any case this dependency is from modeling.ecp
(https://github.com/eclipse-ecp/org.eclipse.emf.ecp.core/tree/master/features/org.eclipse.emf.ecp.license.feature) and as such shouldn't be an issue.
Hi @rahulmohang thanks for checking the package. The info.json is moved to git/github/chromium/chorimium, as I've changed the data source to the official Github mirror of Chromium. That allows us to open these issues directly from a corresponding Github PR via Eclipse Dash (https://github.com/eclipse-set/browser/pull/61 in this case).
Prior Version: #11486 (closed)
I've updated the project id to refer to the official Github mirror of Chromium, so that Eclipse Dash can create the requests for us.
Hi @rahulmohang,
thanks for checking this update. Could you please also update the corresponding info.json [0], so that Dash considers the license approved. That'd stop our build job complaining at me [1]
Project: Eclipse Signalling Engineering Toolbox
Project: Eclipse Signalling Engineering Toolbox
To avoid users unintentionally connecting to the internet (e.g. from the about page), we want to filter outgoing requests to limit allowed remote addresses.
Tasks
[ ] The browser component supports filtering requests [ ] Requests in SET are filtered to prevent external network requests
Separate comment in hope not to confuse the automation.
This has mostly been worked on internally while we were getting our legal info prepared and the internal development processes changed for making the project an official Eclipse project. As that has been completed successfully and as we plan to expand significantly on the component in the near future, we would like to migrate it into Eclipse SET. As it is a lot larger than 1000 lines, we need an extra review per the EDP.
git diff-tree --no-commit-id --name-only HEAD -r
Project: Eclipse Signalling Engineering Toolbox
Hi @rahulmohang,
Yes, that is the case.
The three fonts files are identical (except for the license text included). As the LGPL3+FE is the only license of the three that's compatible to the EPL2.0, we only intend to use that file.
This is obviously a bit hard for the automation to handle as different licenses apply to different files. Per the readme, osifont is available in three variants:
License
Osifont is available in 3 different licenses:
- osifont.ttf - GNU GPL licence version 3 with font exception
- osifont-gpl2fe.ttf - GNU GPL licence version 2 with font exception
- osifont-lgpl3fe.ttf - GNU LGPL licence version 3 with font exception
We only intend to use the osifont-lgpl3fe.ttf
variant in Eclipse SET.
I'm not entirely sure why this showed up during the Dash scan rather than being approved as modeling.ecp
similar to all other bundles from Eclipse EMF Client Platform.
Dash Output (from Eclipse SET): https://github.com/eclipse-set/set/blob/1eed2c1a9e288abe82633a016886db34d26f0b50/DEPENDENCIES#L1043
@jmazanek4ep Thank you. The repository import (mostly) worked, the main set
repository was missing tags & branches other than main, but I've manually pushed those over. The other repositories imported with their branches and tags intact, so that's a bit odd.
One missing thing is that Github Actions seems to be enabled only for the main set
repository. model
, toolboxmodel
, browser
and build
do not show the feature for me. I suspect that might be due to the GitLab CI feature only being enabled for that one repository earlier in this ticket.
Could you please enable Github Actions for the remaining repositories? Sadly otterdog doesn't support that yet.
Great. Let's move forward with otterdog then.
Configuration seems fairly straightforward to me, so a demo PR should be sufficient for us.
Hi @netomi, that looks like something that could be very useful for us. How would we enable/start using otterdog for eclipse-set
?
@fgurr While I don't think anyone on the team currently has 2FA enabled, we might as well enforce it now while we're moving things. Please enforce 2FA for the eclipse-set
GitHub org.
Migrated to https://github.com/eclipse-set/set/pull/2
Migrated to https://github.com/eclipse-set/set/pull/1