Delayed fetching of eclipse-feature dependencies artifacts?

[lppedd]

In a custom plugin I'm writing, I'm accessing projects' dependencies through MavenProject#getDependencyArtifacts.

In case of eclipse-feature projects, I can see certain artifacts have dummy files wtih the file not yet available name.
I've noticed that in MavenDependencyInjector, the fetch parameter is set to true only for eclipse-plugin, why so?

Ultimately my question is, how do I get the correct dependency Artifact#getFile in my own plugin?

[laeubi]

Features don't have a compile phase so no real dependencies, the question is then what exactly you like to access?
If you want the P2 data you can use org.eclipse.tycho.core.utils.TychoProjectUtils.getDependencyArtifacts(ReactorProject)

[laeubi]

You might want to take a look at org.eclipse.tycho.extras.pde.ListDependenciesMojo, if you like you might want add a copy-goal if text file do not suffice.

But be aware that the "dependencies" of a feature are not necessarily what you see in the feature.xml.

[lppedd]

@laeubi that's interesting. I see that internally it uses the TychoProjectUtils you mentioned.
I'll write a copy goal as a last resort.

Is there a way to access the artifacts through the standard Maven repository system?
Or is all managed by Tycho classes and I necessarily have to depend on Tycho?

[laeubi]

You can try to use the WorkspaceReader from the RepositorySession to fetch the file

[lppedd]

@laeubi this might actually work! I see that at some point TychoWorkspaceReader calls descriptor.getLocation(true /* fetch */).
Now I need to find a utility method to convert org.apache.maven.artifact.Artifact to org.eclipse.aether.artifact.Artifact.

Edit: RepositoryUtils.toArtifacts should do it.

[lppedd]

@laeubi Works!
One can also pass by RepositorySystem#resolveArtifact. It's a bit more verbose but it seems a better way.