| [news.eclipse.technology.m2e] Re: Using tycho to build target platform |
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:
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.