[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [tycho-user] Tycho is not compiling against pom dependencies
 | 
Clay, I think the idea behind Tycho is "manifest-first", so that you only have one place (and the "correct" place) to define your dependencies. 
Beat, I think I am using the same 'setup'. Could you confirm this? At the moment my eclipse workspace (folder structure in the file system) looks like this: 
- targets 
   - targetplatform1 
   - targetplatform2 
   - targetplatform1.target 
   - targetplatform2.target 
- 3rdPartyLib-Xy                      <- for example log4j, imported via the eclipse wizard, build via tycho 
- TopLevelComponent               <- some collection of bundles that go in a feature (with parent pom) 
   - TopLevelComponent-Bundle1 <- actual bundle 
   - TopLevelComponent-Feature <- Feature definition 
   - TopLevelComponent-Update  <- Update site 
   - TopLevelComponent-Tests    <- Tests 
Every "TopLevelComponent" has a .pom which has a link to a target platform, so I can build the update sites via a simple maven:install. 
I got two questions: 1. how do you define the target platform? Because at the moment, "TopLevelComponent" in its pom would have a <tycho.targetPlatform>../targets/targetplatform1</tycho.targetPlatform> 
(I use the .target files in eclipse only) 
2. Could you give a concrete example of how to import a third-party jar, for example, how would you import OpenJPA (A jar with OSGi-Metadata is here: http://www.apache.org/dyn/closer.cgi/openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip))? Would you import the main .jar and all the lib-jars independently? 
Greetings from Uster