Closed Daubinrue closed 12 months ago
Update on this one. So it turns out that the manifest is not being read correctly. I tried deleting it and using a blank manifest and the plugin was pulled into the update site this time. Still looking into the root cause.
Could it be that the dynamic dependency version is an issue? Does it make a difference if you use a concrete version?
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed due to inactivity. If it is still valid, please post a comment.
It seems that there may be a bug where certain plugins are not being added to the bundle, but the parent plugin's transitive dependencies are. Ex:
platform{ feature(id: 'platform.plugins', name: 'P2 update site Plugins') { plugin (group: 'eclipse.plugins', name: 'manager-handle', version: '+') }
When the updatesite task is run, the plugin 'manager-handle' shows in build/plugins as expected. When I dive into the build/updatesite/plugins dir it is not there. However, all of it's transitive dependencies are. I also checked the artifact.xml and it is not showing there as well, just the transitive dependencies. No errors display on build. This behavior does not occur with every plugin, but certain ones have this issue. I have checked POMS and do not notice any difference between them. I know you may not have time to fix or look into this issue, but it would be greatly appreciated if you could lend me some ideas or point me to somewhere to look into for this issue. Thanks a lot for the help!