[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60113 ] Jesse Kuhnert commented on MSUREFIRE-69: Hi Brett, The use of that method is decieving in it's current form. The default no args constructor creates a default listener for

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60115 ] Brett Porter commented on MSUREFIRE-69: --- I was just saying that new TestNG ( false ) is not a particularly help piece of code to read when used. new TestNG()

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60116 ] Jesse Kuhnert commented on MSUREFIRE-69: No I think you're right, I just think it's something I'm not completely in control of. TestNG tries very hard to provide defaults

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60121 ] Brett Porter commented on MSUREFIRE-69: --- it should only require: cd surefire-testng vi pom.xml mvn install mvn -X might help. I don't know how you go about getting testng

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60152 ] Jesse Kuhnert commented on MSUREFIRE-69: Got it now. Didn't realize TestNG was instantiated in two different places. The patch supplied only works against the latest

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60166 ] Brett Porter commented on MSUREFIRE-69: --- don't worry about uploads. I'll create snapshots from the cvs repository. I haven't tried building testNG with m2, but I don't think

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60167 ] Jesse Kuhnert commented on MSUREFIRE-69: I think it will ~probably~ be possible to build it with m2? There have to be other projects with seperate source trees for differing

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60176 ] Jesse Kuhnert commented on MSUREFIRE-69: Awesome, thanks Brett! I don't use a sun jvm so don't have the javadoc libs available via normal means. (ibm's jre runs much much

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60059 ] Jesse Kuhnert commented on MSUREFIRE-69: I had originally removed this when developing the first round of patches but it seems to have re-surfaced again. Will do it again

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60060 ] Brett Porter commented on MSUREFIRE-69: --- this was by setting the output directory - but that was to target/surefire-reports which isn't wanted. ideally, the listeners would

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60064 ] Jesse Kuhnert commented on MSUREFIRE-69: I meant fixed in testng itself, it probably got re-enabled somehow. Will report back when testng get's fixed and if any patches need

[jira] Commented: (MSUREFIRE-69) stop output to test-output directory

[ http://jira.codehaus.org/browse/MSUREFIRE-69?page=comments#action_60088 ] Brett Porter commented on MSUREFIRE-69: --- Jesse, This doesn't seem like the best way to fix this from the TestNG perspective. Shouldn't it be more explicit? I assume this is