Hi,

I'm sure I answered this question (or someone else asking it) on dev@
the other day... I also would really prefer you ask on the users list
so there's a permanent record (even if you need to privately ping me
to take a look there).

Sorry I checked the dev list archive before contacting you directly
and there wasn't a response to my original query.  I thought that as
this is more of a dev question than a user question the dev list would
be a more appropriate place to ask.

Anyway, there's no simple answer. Usually surefire tests are forked,
so the command line is not accessible. Even if they are not forked,
that would require storing the actual command line which isn't done.

So -Dtest=MyTest is looked up via system properties to configure
surefire correctly?

But standard mvn options -o, -X etc are not passed through to surefire
or stored at some point after mvn has been configured and execution
has started?

More specifically I need to access the -o param in a test.  Previously
I could lookup the QUOTED_ARGS env variable that is set in the mvn.sh
script, but since 2.0.6, it is no longer exported in the script, this
is also cumbersome as I need to maintain two sets of code for the
windows/linux versions as they use different env variable names.

I would have thought that the commandline that is built and used to
launch mvn could be stored and made accessible to plugins should they
need it, but I'm not familiar with the intricacies of mvn internals,
hence the original email on the dev@ list and then the follow up ping
to yourself.  If it isn't already available to the plugins, would it
be a feature that could be added to mvn?

Thanks for your time,
Kev

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to