On Fri, 2005-11-04 at 19:46 +0100, Milos Kleint wrote:
> regarding mevenide:
> i've done some basic work on maven2 mevenidefor netbeans. I'm using the
> embedder for that as well. it has some rough egdes but geneally works fine.
> check my recent post to the dev list with details.
>
> the current
regarding mevenide:
i've done some basic work on maven2 mevenidefor netbeans. I'm using the
embedder for that as well. it has some rough egdes but geneally works fine.
check my recent post to the dev list with details.
the current embedder is not release but I think Jason is very close to
releasin
Hi,
Whats the status on the maven embedder. I currently use intellij as my ide,
and through its external tools feature I'm able to run maven for the
selected module, but it would be nice to have a bit more control so I was
thinking of writing a very simple intellij plugin, that uses the embedder.
I'm including this as one of the use cases as we work through
http://jira.codehaus.org/browse/MNG-591
- Brett
On 7/24/05, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> Guys,
>
> I am also trying to create testcases for an m2 plugin. For this I need
> an initialized MavenProject instance inside my
Thank you very much, I am eagerly looking forward to these docs.
Adding the -B flag when executing MavenCli.main() solved the JLine problem.
The JLine problem occurs only when the -o flag is also used.
When using the PlexusTestCase in combination with 'lookup( Maven.ROLE )', the
JLine problem a
Guys,
I am also trying to create testcases for an m2 plugin. For this I need
an initialized MavenProject instance inside my test case (so that I
have access to getArtifacts and co). Best would be to be able to
initialize a Mojo with a particular POM.
Any idea how to do this?
Thanks,
Stéphane
On
On 7/24/05, Peter van de Hoef <[EMAIL PROTECTED]> wrote:
> - If it is, how can this JLine issue be worked around? Is it possible to
> disable the InputHandler?
I think the batch mode flag should turn that off. If not, I'd consider
that a bug. We should also consider fixing the problem with jline
Hi,
I'm developing a testcase in which I need to run Maven from within the testcase.
I don't want to run maven by executing 'm2' as a separate process via Runtime.exec() since I want my test to run
correctly in an environment where maven itself is embedded in another application (e.g. Eclipse).