[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] How to use m2e to resolve dependencies in non jdt project?
|
m2e embeds maven runtime, so embedding m2e in command line build will be
very difficult.
My completely uneducated and likely bad advice is
* define common components that use resolved maven dependencies to do
whatever processing is necessary
* for command line build, let maven resolve project dependencies and
invoke the processing components
* for IDE, write a project configurator and corresponding build
participant. m2e will call it with resolved project dependencies and the
same processing components will be usable as well.
--
Regards,
Igor
On 11-06-14 1:17 PM, Matthias Koester wrote:
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
