Bugzilla – Full Text Bug Listing
| Summary: | Trouble including fragments in test environment | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Doug Schaefer <cdtdoug> |
| Component: | Tycho | Assignee: | Project Inbox <tycho-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | igor, malaperle |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
BTW, I'm using the 0.13.0-SNAPSHOT. 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. 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. |
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.