Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355881 - Trouble including fragments in test environment
Summary: Trouble including fragments in test environment
Status: RESOLVED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-25 13:19 EDT by Doug Schaefer CLA
Modified: 2021-04-28 16:55 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Doug Schaefer CLA 2011-08-25 13:19:32 EDT 
The CDT is structured so that the org.eclipse.cdt.core plug-in has a number of platform specific fragments that provide native libraries for the core plug-in. I noticed that the org.eclipse.cdt.core.tests plug-in had a failure because the fragment for the test platform (linux.x86) wasn't included in the test environment.

Igor pointed me to the dependencies capability and I've added that to the core.tests pom.xml. Unfortunately I get maven failures because the p2 resolver can't find the fragments. I've tried numerous different version format, but with 0.0.0 not working, I'm assuming that the resolver isn't looking in the build results of the fragment project. But I'm not sure of that.

The CDT git repo is at:

    git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git

You can run maven at the top level there. The core.tests plug-in is in the core directory off the root.
Comment 1 Doug Schaefer CLA 2011-08-25 13:41:57 EDT 
BTW, I'm using the 0.13.0-SNAPSHOT.
Comment 2 Igor Fedorenko CLA 2011-08-25 14:15:49 EDT 
Please provide standalone sample project that demonstrates the problem. It is not fair to ask Tycho developers to look at the entire CDT source tree, which I assume is neither small nor trivial.
Comment 3 Tobias Oberlies CLA 2011-11-08 08:24:20 EST 
I agree with Igor's last comment. We cannot reproduce the problem if you are just pointing to your source repository - at least the commit ID would be required.