Community
Participate
Working Groups
Hello, I encountered this problem while I was attempting a last correction on an old branch job which dependended on sources that are now archived (@see Bug 560941). I would therefore like to know if, aside from the ignore property there can be a way to let tycho resolve the existing proxies but ignore the redirections from archived sources. Thanks, Quentin
Can you please check whether those repo work in regular Eclipse Platform when using p2 to install content from them? If not, please move the issue to p2. However, it seems more like the issue is a wrong management of p2 repos; not something p2 or Tycho can -nor should- implement workaround for IMO.
(In reply to Mickael Istria from comment #1) > However, it seems more like the issue is a wrong management of p2 repos; not > something p2 or Tycho can -nor should- implement workaround for IMO. Have you read Bug 560941 comment 0? To me it looks like Ed W. has painstakingly followed a lot of rules of good Eclipse citizenship. Why blame him for 'wrong management of p2 repos'?
(In reply to Stephan Herrmann from comment #2) > Have you read Bug 560941 comment 0? To me it looks like Ed W. has > painstakingly followed a lot of rules of good Eclipse citizenship. Why blame > him for 'wrong management of p2 repos'? Surely not Tycho as a technology if it works as expected ;) Tycho is not the entity that does the Eclipse Foundation rules, nor the entity that manages the infra, that, nor that directly maintains p2. And the error seems more on one of those 3 layers. I'm asking for a test against p2 UI to narrow down the list and to identify whether it's a Tycho-specific issue or whether it can be reproduced in other contexts.
(In reply to Mickael Istria from comment #3) > (In reply to Stephan Herrmann from comment #2) > > Have you read Bug 560941 comment 0? To me it looks like Ed W. has > > painstakingly followed a lot of rules of good Eclipse citizenship. Why blame > > him for 'wrong management of p2 repos'? > > Surely not Tycho as a technology if it works as expected ;) Whether or not tycho works as expected will be the result, not the premise of investigation. When saying "it seems more like the issue is a wrong management of p2 repos", do you care to share the reasons why you believe so?
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required. 0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done if issue is still present when latest release: * Create a new issue at https://github.com/eclipse/tycho/issues/ ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience) ** In the GitHub description, start with a link to this bugzilla ticket ** Optionally add new content to the description if it can helps towards resolution ** Submit GitHub issue * Update bugzilla ticket ** Add to "See also" property (up right column) the link to the newly created GitHub issue ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>" ** Set status as CLOSED MOVED ** Submit All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.
