As far as I can see the classpath container for "Maven Dependencies" is only populated for projects build with the maven-bundle-plugin with "Embedded-Artifacts".
I think it should also be populated for real Tycho projects to handle embedded dependencies there.
Our current approach is to add a normal Maven dependency to a Tycho project. Then we use the maven-dependency-plugin to copy the dependencies into a lib/ folder during the validate phase and finally we add them manually to MANIFEST.MF and the build path. This works pretty good. The downside is that neither the sources nor the Javadoc of the JAR files are accessible within Eclipse.
If this plugin would also populate the "Maven Dependencies" for Tycho projects (as for Embedded-Artifacts) then sources and Javadoc would be available and one then can use the maven-dependency-plugin to unpack the dependencies into the target/classes folder during the Maven package phase. Finally we would have a JAR file with embedded dependencies in the same way as we had used the maven-bundle-plugin with its Embed-Dependency functionality.
As far as I can see the classpath container for "Maven Dependencies" is only populated for projects build with the maven-bundle-plugin with "Embedded-Artifacts". I think it should also be populated for real Tycho projects to handle embedded dependencies there.
Our current approach is to add a normal Maven dependency to a Tycho project. Then we use the maven-dependency-plugin to copy the dependencies into a lib/ folder during the validate phase and finally we add them manually to MANIFEST.MF and the build path. This works pretty good. The downside is that neither the sources nor the Javadoc of the JAR files are accessible within Eclipse.
If this plugin would also populate the "Maven Dependencies" for Tycho projects (as for Embedded-Artifacts) then sources and Javadoc would be available and one then can use the maven-dependency-plugin to unpack the dependencies into the target/classes folder during the Maven package phase. Finally we would have a JAR file with embedded dependencies in the same way as we had used the maven-bundle-plugin with its Embed-Dependency functionality.
What do you think?