Community
Participate
Working Groups
This idea came from bug 426532. When that bug is committed, the category editor will support the specification of a download stats server as well as the artifacts to track. For now, the user has to specify what version of artifact is to be tracked. Is this too restrictive? Should versions be ignored? Or should the user be able to say whether versions matter? If we decide that versions don't matter, there will be a little refactoring to do with the interfaces in org.eclipse.pde.internal.core.ifeature and org.eclipse.pde.internal.core.ibundle. Currently both interfaces implement IVersionable. We would need non-versionable implementations that the download stats could use, and then clients who need versions would add it. If we go down this path, we should also consider whether to drop the URL in the basic feature model (because it is not used for stats tracking either) and use only when needed.
I was hoping the model/interface changes would only affect the site/category models, not core IBundle and IFeature. We need to be a more careful making changes there as they are used throughout PDE.
(In reply to Curtis Windatt from comment #1) > I was hoping the model/interface changes would only affect the site/category > models, not core IBundle and IFeature. We need to be a more careful making > changes there as they are used throughout PDE. That's why I was nervous about doing any refactoring. We can look at this closer once we determine if we want to remove the version support.
Another issue that came up in bug 426532 is whether features should be sorted in the category.xml file. For example, if we no longer used feature URL when writing features for download stats, we would likely sort by id.
