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 appears again.
It appears that the constructor of the DefaultMaven class is constructing the
InputHandler.
For now, I can live with this and will wait for the documentation on embedding
Maven.
Greetings,
Peter
Brett Porter wrote:
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 if
possible.
- If not, how should it be done? I've studied the MavenCli class and tried to
mimic its behaviour by extending the
testcase from PlexusTestCase in which an instance of Maven is created with
'lookup( Maven.ROLE )'. Is this the way to go
or is there a better way?
That's closer to the expected way it will be done. We're expecting to
formalise and document how to embed Maven during the approaching beta
cycle.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
