Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] tycho-surefire-plugin and general rules to define dependency-resolution in target-platform-configuration?

Can you show us the log file and the definition of your target platform ?


On Fri, Apr 10, 2015 at 6:08 PM, Sam Z <zhou3r@xxxxxxxxx> wrote:
We need to run SWTBot test cases for a complex project, which consumes many upstream projects' P2 repositories.

I followed guideline in these locations:

But still get dependencies cannot be resolved when running SWTBOT test cases. I'm wondering what's the general guideline to define target platform in pom.xml:


I saw some Eclipse demo and actual projects, some doesn't define it at all; but some only include one or two features in the dependency.

I'm wondering what is the consistent way to define dependencies in tag <dependency-resolution>?

Should I define all features I'm building from source in my workspace + all features in my target runtime?
Should I define just all the plugins exactly same as my launch (which is validated by IDE no unresolved plugins)?

I tried both, still doesn't work.

Do we have a general rules how to define it in a systematic way so no guess around what should be depended on?


tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

Back to the top