Community
Participate
Working Groups
Some further processing (like API Tools) would require a listing of all the content of the target platform to work well. It would be great if Tycho allows -as an extra plugin or even directly as part of default resolver- to dump the depedencies as a .target that could be reused afterwards. We can also imagine other use-cases (such as someone willing to focus on a single bundle and who wants a TP ready for this single bundle) where this 'focused' target file can be also useful.
Actually, there is no suitable target platform location type to just list jars/folders. Some support needs to be added to PDE directly.
The maven-dependency-plugin can already somehow do the work <plugin> <artifactId>maven-dependency-plugin</artifactId> <executions> <execution> <id>list-dependencies</id> <goals> <goal>list</goal> </goals> <phase>verify</phase> <configuration> <outputAbsoluteArtifactFilename>true</outputAbsoluteArtifactFilename> <outputScope>false</outputScope> <outputFile>${project.build.directory}/dependencies.txt</outputFile> </configuration> </execution> </executions> </plugin> It seems much simpler that downstrean usage (like bug 547206 ) just learn to read such output to build a local target platform rather than hacking some mojo and specific target location to have this in a .target file.
The maven-dependency-list suffers from the fact that nested jars inside bundles make that the path to the inner jar is listed, and not the actual bundle. It causes bug 548242
New Gerrit change created: https://git.eclipse.org/r/144002
Gerrit change https://git.eclipse.org/r/144002 was merged to [master]. Commit: http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/commit/?id=b16c71c39de22127603cc0c25aca50ccdcabf16d