Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361161

Summary: p2 repository aggregation should fail on problems
Product: z_Archived Reporter: Tobias Oberlies <t-oberlies>
Component: TychoAssignee: Project Inbox <tycho-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: gunnar, tonny.madsen
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 372780    
Bug Blocks:    

Description Tobias Oberlies CLA 2011-10-17 11:42:00 EDT
In order to support feature patches (bug 347825), the error handling in the p2 repository aggregation step for eclipse-repository was made less strict [1], with the hope that this doesn't lead to hidden problems. This has shown to be wrong: in case of bug 359090, the lenient error handling was hiding the actual problem and made error analysis harder.

This structural problem should be resolved. Tycho should fail in case of aggregation problems, while not breaking the support for feature patches. This may be fixed in the p2 mirror tool used for aggregation.

[1] https://github.com/sonatype/sonatype-tycho/commit/09d71aa2f895d94bb002b7e6c6bdf299a740c224
Comment 1 Tobias Oberlies CLA 2012-05-31 11:39:28 EDT
*** Bug 381044 has been marked as a duplicate of this bug. ***
Comment 2 Mickael Istria CLA 2021-04-08 18:11:14 EDT
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.