[m2e-dev] How to use m2e to resolve dependencies in non jdt project?

[Matthias Koester <matthias.koester@xxxxxxxxxxxxx>]

Hi,

We're developing our own _javascript_ IDE based on DLTK and we also have a headless eclipse application to run our compiler headless in a maven based build. Our maven build already uses dependencies to further process our _javascript_ libraries, but up until now we didn't had to resolve any maven dependencies in our eclipse applications. But now we have to do this and the question is if it makes sense to use m2e for that purpose. Our maven build packages our _javascript_ files with additional metadata as a jar file, which then gets installed/ deployed to our local maven repository/nexus. We basically have to support two usecases:

1. Our headless compiler - which is a headless version of our IDE - needs to be able to resolve dependencies and needs to add them to the DLTK build path.
2. Our IDE should resolve the dependencies against projects checked out in the workspace. Missing projects should be resolved against our nexus repository.

As far as I understand maven/m2e/aether, usecase 1 can be implemented by just using aether, but we hope that by using m2e it would also be possible to implement usecase 2. What do you think?

Regards,

Matthias