see inline -- Regards, Igor
On 11-10-28 1:17 PM, [email protected] wrote:
Hi m2eclipsers, We're trying to use m2e core (a couple of extension points and some classes) in a command-line application, and have discovered that at least in an older version that m2e.core bundle has a dependency on org.eclipse.search, which has a number of dependencies on UI code (org.eclipse.ui, swt, jface I think, etc). For our command-line application, we don't want all this UI code (for size, load time, etc). First question: Is there any way that the m2e.core dependency on org.eclipse.search be removed?...and/or isolated in a m2e.core.ui plugin? What would be required to get this to happen? Bug/enhancement request, etc?
We have not looked at running m2e in headless mode and I am curious to understand the use case behind this requirement (m2e is about integration with maven, which is a headless command line tool...) Regardless of the use case, I think it is generally a good idea to make m2e.core independent of eclipse ui and will be willing to review and apply a patch. If download size your main concern, I think it would make sense to decompose m2e.core even further, in particular, integration with nexus indexer and archetyper can probably move into their own bundles.
Second (unrelated) question: I've seen that the m2e git repo doesn't seem to have Eclipse project structure (so they can't be imported into an Eclipse workspace). Are there some instructions/procedure for getting the current m2eclipse source code into an Eclipse workspace?
m2e 1.1 development environment is documented here http://wiki.eclipse.org/M2E_Development_Environment -- Regards, Igor _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
