>
> It IS possible to customize execution request through existing public API.
Maybe I missed something but as much as I saw this is only possible if we
leave out the part where M2E pre-configures the MavenExecutionRequest.
If an M2E extension executes a MojoExecution without using the workspace
It IS possible to customize execution request through existing
public API.
What isn't possible though existing public API, is to customize
execution request AND use m2e workspace dependency resolution at the
same time. Like I said in the bugzille, I don't understand all
implications of this and wo
Hi Igor,
thanks for the answer!
There are no plans to expose internal workings of workspace dependencies
> resolution to m2e extensions at this point.
I understand and agree. This is a special functionality that is rarely
necessary.
The solution I proposed in my second mail is a bit more gener
There are no plans to expose internal workings of workspace
dependencies resolution to m2e extensions at this point. I suggest you
use m2e internal classes, but retest your code still work each time you
upgrade m2e.
--
Regards,
Igor
On Thu, Aug 25, 2016, at 04:34 AM, Balázs Zsoldos wrote:
> Hi,
Hi,
I have managed to solve my use-case but it is a bit tricky and it calls
internal API. Here is the solution:
@SuppressWarnings("restriction")
public static IMavenExecutionContext createExecutionContext(final
IMavenProjectFacade facade,
final IProgressMonitor monitor) throws CoreExcep
Hi,
I would like to have the following steps in my Eclipse plugin:
- Get the dependency tree of a project (done)
- Flatten the dependency tree to a list that can be used to find out
build order (done)
- Iterate through the flattened dependency list and call every "mvn
package" on
