Community
Participate
Working Groups
All builds that are named "platform"[0][1] as well as the corresponding features [2] should be renamed to filetransfer. The original naming stems from the initial consumer (Platform/Equinox), but there is no reason why consumption should be limited to Equinox/Platform only. Hence the rename to the more fitting "filetransfer". This has also implication WRT the p2 repo URL [3]. [0] https://build.ecf-project.org/hudson/job/C-HEAD-platform.feature/ [1] https://build.ecf-project.org/hudson/job/I-HEAD-platform.feature/ [2] http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/releng/features/org.eclipse.ecf.platform-feature?h=origin [3] http://download.eclipse.org/rt/ecf/integration/platform/v${BUILD_ID}
Adding Kim as the contact for Platform/Equinox
While at it, we might wanna discuss comment #7 on bug #314901 [0] too. [0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=314901#c7
changing component
I don't see how the filename prohibits anyone from consuming it. It's not Platform Equinox anyways, it's Runtime Equinox.
(In reply to comment #4) > I don't see how the filename prohibits anyone from consuming it. It's not > Platform Equinox anyways, it's Runtime Equinox. But potential consumers don't see that org.eclipse.ecf.platform.feature is in fact org.eclipse.ecf.filetransfer.feature from a functionality point of view.
I thought this was a platform releng bug but I see it's in the ecf bucket. It's up to the ECF team to determine how they want to name their features. I just manage the RT Equinox build, not ECF so I'm going to remove myself from this bug.
Kim, I initially added you (Equinox/p2) as a consumer of this feature. If we do the change outlined in this bug, we will have to change our how ECF contributes filetransfer to platform.
Fix released to master
Created attachment 180932 [details] mylyn/context/zip