search

eclipse-cbi / targetplatform-dsl

Target Platform Definition DSL and Generator
Eclipse Public License 2.0
76 stars 38 forks source link

Not working in Eclipse 2020-06 #113

Closed mheydem closed 2 years ago

mheydem commented 3 years ago

After installing in Eclipse 2020-06 via "Install new Software" using the update-site http://download.eclipse.org/cbi/tpd/3.0.0-SNAPSHOT the expected context menu entries for tpd files are missing. Additionally some PDE features are missing: Target Platform in Preferences and Eclipse Application launch configurations. Unfortunately uninstalling the tpd stuff from eclipse does not recover the PDE features.

mbarbero commented 3 years ago

Thanks for the report. I don't have time currently to dig into the issue. Would you be willing to investigate? I could provide assistance.

mheydem commented 2 years ago

It is working in Eclipse 2021-12. I guess this won't be fixed.

akurtakov commented 2 years ago

This functionality is clearly looking for new maintainer. There are already multiple ways to declare target platforms and with latest enhancements to be able to refer to Maven artifacts directly this one is becoming even more outdated. If no one steps up to take over there are multiple paths forward - plain PDE target files, M2E extension to use Maven artifacts in the target file and Oomph targlets. All these are well maintained.

merks commented 2 years ago

This .tdp stuff is quite widely used because it's really very nice. See this recent forum thread about Targlets and .tdp:

https://www.eclipse.org/forums/index.php/mv/msg/1101039/1854375/#msg_1854375

One reason why .tdp is so popular is because the PDE editor is, how to say it nicely, kind of horrible. I thought about how to fix that, but the problem is that the PDE design is focused on downloading all the plugins and features in order to provide information about them in the editor. So the editing experience isn't just based on using p2 metadata from the repositories while editing, as is the case for .tdp and Oomph's targlets. I.e., org.eclipse.pde.core.target.ITargetLocation.getBundles() which provides org.eclipse.pde.core.target.TargetBundle.getBundleInfo() where the only implementation is org.eclipse.equinox.internal.p2.publisher.eclipse.GeneratorBundleInfo so it just relies on published info from bundle and feature artifacts. Maybe where are ways to improve this in PDE, but right now, in general, you open the PDE editor and it starts to download everything, which takes long, might not be successful, and fills up the disk; it is simply not an ideal experience...

But yes, your point *.tdp needing maintainers is a good one. Far too many people assume that all these technologies are just a free ride and somehow must learn the painful way when it stops working that they personally need to do something to keep it working...