[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Is this a case for a m2e extension ?
|
Hi Anton, sure.
in our case the main generated artifact will be composed by nested
dependencies (it is just a zip file containing other zip files plus its
descriptor file). There is no need for any compilation.
I've implemented an incremental building for the descriptor file
generation mojo since it needs only informations that exists in its
pom.xml. I did the same in the mojo that builds the zip but it is not
working well when it is inside eclipse workspace because the problem stated.
the main archive artifact will be consumed by an OSGi service provided
by an bundle that may exists in the workspace or in the current target
platform.
For now we are using the artifact URL to point to the latest archive. At
development time we are using a FILE URL being set as a VM argument
(equinox launcher). And at production we use a Gogo command that
receives the URL pointing to the artifact at a maven repository.
We are not using classifiers for while.
