[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] build-before-launch ? background m2e task ?
|
Yes, m2e long running operations are expected to honour
IProgressMonitor.isCanceled flag. Keep in mind that raising cancelled
flag on progress monitor does not guarantee immediate return from the
long running operation so it may be some time before operation actually
returns. If you find that some operations cannot be cancelled at all,
please open bugreport(s) and, of course, quality patches significantly
increase likelihood of the fix ;-)
I still think that working with core debug framework developers to
directly support this usecase will provide better long-term solution,
but this is obviously up to you.
--
Regards,
Igor
On 11-10-13 4:53 PM, Andrei Pozolotin wrote:
Igor:
-------- Original Message --------
Subject: Re: [m2e-dev] build-before-launch ? background m2e task ?
From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
To: m2e-dev@xxxxxxxxxxx
Date: Thu 13 Oct 2011 03:36:51 PM CDT
I honestly believe this is a bad idea and will cause problems.
1) I agree! :-)
but what is a good idea for my use case?
2) I put together a quick hack for b/g job; it seems to work so far;
now I just need to test maven abort on job cancel; is it possible in m2e
context?
thank you;
Andrei.
--
Regards,
Igor
On 11-10-13 12:08 PM, Andrei Pozolotin wrote:
Igor:
if I take the "background job" route,
what is the correct way to abort currently running maven invocation?
I am trying to do the following:
a) each incremental build checks if there is already a maven build
job running;
b) if so, cancel it and start a new one;
Thank you,
Andrei.
-------- Original Message --------
Subject: Re: [m2e-dev] build-before-launch ? background m2e task ?
From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
To: m2e-dev@xxxxxxxxxxx
Date: Wed 12 Oct 2011 05:19:15 PM CDT
See inline.
--
Regards,
Igor
On 11-10-12 5:17 PM, Andrei Pozolotin wrote:
Hello;
1) I am developing a m2e extension on the lines of:
http://wiki.eclipse.org/M2E_Extension_Development
2) In need to cover 2 executions:
a) http://felix.apache.org/site/apache-felix-maven-scr-plugin-use.html
org.apache.felix:maven-scr-plugin:scr
b)
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
org.apache.felix:maven-bundle-plugin:manifest
QUESTIONS:
A) I need to run both of the above goals right before java
application launch via eclipse launcher;
(I do not want to run them on incremental build)
how m2e gives access to "build-before-launch" JDT event?
Can you provide some documentation pointers or other information that
explains how to implement build-before-launch "handler"?
B) if there is no m2e access to "build-before-launch" JDT event,
can I run these goals on background, in async thread pool w/o
blocking m2e builder invocation?
(so incremental build just serves as a trigger for background rebuild)
This really depends on what you need to do. If your project
configurator
needs access to workspace, especially change any workspace
resources, it
will likely be easier to run this code as part of a builder. If the
code
does not make any changes to workspace, it is probably be okay to run
this as a background job.
C) maven-bundle-plugin life cycle is already mapped by some other
m2e extension;
(I receive "conflicting life cycle mappings" error)
how can I override that? how can I find which other extension is
doing that?
m2e-tycho provides mapping for maven-bundle-plugin bundle and manifest
goals. Either uninstall m2e-tycho project configurator or force use of
your project configurator from pom.xml file.
[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
Thank you,
Andrei
