| How to stop jetty:run from q4e 0.9? [message #18834] |
Wed, 13 May 2009 23:20  |
Eclipse User |
|
|
|
I can launch my web app via the jetty:run goal from within q4e OK.
But it shows as a non-terminating task in Eclipse's Progress view.
Canceling the task using the red button in progress view is ineffective.
If I subsequently attempt goal jetty:stop (the "right way"), the launch of
this goal appears to block on the previous jetty:run goal.
Does q4e/IAM serialize maven goal execution?
If so, this seems to be a big obstacle to it supporting common usage
patterns.
-Ben
PS I expect I can workaround issue from Maven command line. However, to
some extent this defeats purpose of having Eclipse integration, if one
must regularly drop out of it.
|
|
|
| Re: How to stop jetty:run from q4e 0.9? [message #18880 is a reply to message #18834] |
Thu, 14 May 2009 09:40  |
| Eclipse User |
|
|
|
Hello Ben,
Ben Hutchison wrote:
> I can launch my web app via the jetty:run goal from within q4e OK.
> But it shows as a non-terminating task in Eclipse's Progress view.
> Canceling the task using the red button in progress view is ineffective.
> If I subsequently attempt goal jetty:stop (the "right way"), the launch of
> this goal appears to block on the previous jetty:run goal.
> Does q4e/IAM serialize maven goal execution?
Yes. IAM uses an single instance of the maven embedder, which is not
thread safe... so all calls are serialized.
We expect users to take advantage of WTP integration (which, if I am not
mistaken, already supports Jetty).
> If so, this seems to be a big obstacle to it supporting common usage
> patterns.
I think this deserves a bugzilla entry.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=IAM
> -Ben
> PS I expect I can workaround issue from Maven command line. However, to
> some extent this defeats purpose of having Eclipse integration, if one
> must regularly drop out of it.
As a workaround, you can setup some External Tool Configurations (Run >
External Tools >...) in Eclipse for your typical use cases to run a
locally installed maven, so you do not need to leave the IDE (and, for
launching the jetty case, it will require you fewer clicks/keystrokes).
Thanks!
--
Abel Muiño
|
|
|
|
| Re: How to stop jetty:run from q4e 0.9? [message #569009 is a reply to message #18834] |
Thu, 14 May 2009 09:40 |
| Eclipse User |
|
|
|
Hello Ben,
Ben Hutchison wrote:
> I can launch my web app via the jetty:run goal from within q4e OK.
> But it shows as a non-terminating task in Eclipse's Progress view.
> Canceling the task using the red button in progress view is ineffective.
> If I subsequently attempt goal jetty:stop (the "right way"), the launch of
> this goal appears to block on the previous jetty:run goal.
> Does q4e/IAM serialize maven goal execution?
Yes. IAM uses an single instance of the maven embedder, which is not
thread safe... so all calls are serialized.
We expect users to take advantage of WTP integration (which, if I am not
mistaken, already supports Jetty).
> If so, this seems to be a big obstacle to it supporting common usage
> patterns.
I think this deserves a bugzilla entry.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=IAM
> -Ben
> PS I expect I can workaround issue from Maven command line. However, to
> some extent this defeats purpose of having Eclipse integration, if one
> must regularly drop out of it.
As a workaround, you can setup some External Tool Configurations (Run >
External Tools >...) in Eclipse for your typical use cases to run a
locally installed maven, so you do not need to leave the IDE (and, for
launching the jetty case, it will require you fewer clicks/keystrokes).
Thanks!
--
Abel Muiño
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07944 seconds
Home