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

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

I don't have use of dependencyManagement by Tycho documented anywhere 
yet. The best I can offer is Tycho integration test of this 
functionality [1]. build01 installs a number of artifacts to maven local 
repo. build02 uses dependencyManagement to add these artifacts to build 
target platform.

Tycho development environment setup is explained in [2]. Steps to build 
tycho from CLI are explained in [3].

To materialize target platform, you will need to grab TargetPlatform 
associated with a project and then copy bundles/features from the target 
platform to the destination folder. There are currently couple of places 
that perform similar logic (product export and test runtime creation). 
If you can consolidate this logic in one place this will be much 
appreciated ;-)

Let me know if you have any questions.

--
Regards,
Igor


[1] 
https://svn.sonatype.org/m2eclipse/tycho/trunk/tycho-its/projects/tycho164
[2] http://docs.codehaus.org/display/M2ECLIPSE/Tycho+development+environment
[3] http://docs.codehaus.org/display/M2ECLIPSE/Building+tycho



Will Horn wrote:
> "Igor Fedorenko" <igor@xxxxxxxxxxxxxx> wrote in message 
> news:gu05jf$lfs$1@xxxxxxxxxxxxxxxxxxxx
> > At this moment we do not plan to support target platform 
> > materialization in Tycho. However, this should be next to trivial to 
> > implement (maybe 50 lines of code), so if you are interested I can 
> > provide pointers to help you start.
> I am interested.  Curently I am using the maven-dependency-plugin.  The 
> copy-dependency goal works for bundalized maven artifact dependencies.  
> For the eclipse components, I don't use dependencyManagement, but just 
> upload the distribution zips (like the SDK and delta pack) to our own 
> maven repo and use the unpack goal.  I'd like to avoid this second piece 
> (manually uploading eclipse zips and maintaining a full list of plugins) 
> and take advantage of tycho's understanding of public p2 repos and 
> transative osgi dependencies.
>
> > Aslo, do you know that you can define build target platform using 
> > <dependencyManagement/> pom.xml element and Tycho will use configured 
> > Maven2 repositories to source these dependencies?
> My bundalized maven artifacts are in "dependencyManagement".  But how do 
> I specify a p2 dependency, like org.eclipse.ui?  I tried using a groupId 
> of p2:
>    <dependency>
>      <groupId>p2</groupId>
>      <artifactId>org.eclipse.ui</artifactId>
>      <version>3.4.2.M20090204-0800</version>
>    </dependency>
>
> > Also, we plan to add build target platform management to Sonatype 
> > Studio (commercial M2E derivative). From user standpoint it will work 
> > similar to how M2E manages content of Maven Dependencies classpath 
> > container, where dependencies are added/removed according to changes 
> > to pom.xml file automatically.
> Sounds like a great feature, especially in conjunction with nexus pro's 
> p2 proxying.  My product is open source so we try to have no 
> dependencies on paid commercial products for the development 
> environment.  But I will keep it in mind.
>
> Thanks,
> Will