Edgewall Software
Modify

Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#545 closed defect (invalid)

java tools: wildcards for junit don't work

Reported by: eXistence Owned by: hodgestar
Priority: major Milestone:
Component: Recipe commands Version: 0.6b2
Keywords: Cc:
Operating System: Linux

Description

referencing a specific file works like expected:

<java:junit file="testreport_TestProperty.xml"/>

referencing more the one file via wildcards doesnt. If i write this:

<java:junit file="testreport_*.xml"/>

nothing happens :(

Attachments (0)

Change History (5)

comment:1 Changed 15 years ago by hodgestar

Could you try running the slave with --verbose and looking for errors in the output? Add anything that looks relevant to the ticket. Thanks. :)

comment:2 Changed 15 years ago by hodgestar

  • Owner set to hodgestar
  • Status changed from new to assigned

comment:3 Changed 15 years ago by eXistence

thanks for the quick reply and the --verbose hint. I figured out its a problem with an outdated version of gtest that is installed on the slave. The output of that gtest version can't be converted to the junit format correctly, so the junit command complains about misformed xml input.

btw: the wiki page Bitten Slave Options is very helpful to debug those things, but i think a link to it is missing in the user guide/documentation.... or did i miss it?

long story made short: Its not an problem of bitten/junit, sorry for bothering. Ticket can be closed.

comment:4 Changed 15 years ago by hodgestar

  • Resolution set to invalid
  • Status changed from assigned to closed

No problem. :)

In general the documentation could use a little tidying up and re-organization.

comment:5 Changed 15 years ago by osimons

  • Milestone 0.6.1 deleted

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain hodgestar.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.