[news.eclipse.technology.m2e] Re: Using tycho to build target platform

["Will Horn" <will.horn@xxxxxxxxx>]

> Tycho 0.4.0 is supposed to take Import-Package declarations into account 
> when resolving build target platform in "p2" mode. Please create new 
> bugreport in JIRA [2] and provide sample project we can use to reproduce 
> the problem.
This was my fault, I had accidentally specified a version on the 
import-package which applied to Eclipse 3.5, forgetting the tycho build was 
against an Eclipse 3.4 p2 repository.

> Tycho is not able to use "plain" JAR files from Maven repositories 
> directly because Maven artifacts do not contain enough metadata to 
> reliably construct OSGi bundles from them. We are considering several ways 
> to improve this, but for now you need to "bundalize" Maven artifacts 
> first. You can use Felix/BND plugin or you can use Tycho generate-bundle 
> to do this (and there is a good chance we will merge the two in some time 
> in the future).
I understand this.  But if my maven artifacts are already fully bundalized, 
how do I get them into the target platform? I really like the implicit TP 
feature, but what I would like to do at this point is just specify a TP 
explicitly and have tycho create it, i.e. build a directory that I can use 
in the Eclipse IDE and in a tycho build via  "-Dtycho.targetPlatform=...". 
[1] has a section entitled "TP specification artifact" that seems to address 
this topic somewhat.

I notice m2eclipse uses a shell script to do a similar thing 
(http://svn.sonatype.org/m2eclipse/tycho/trunk/tp-scripts/m2e-e34.sh) but 
I'm trying to automate that.  Is this possible?

Thanks,
Will

> [1] http://docs.codehaus.org/display/M2ECLIPSE/Tycho+0.4.0+plan