[jbehave-dev] Re: Classloader issue when running scenarios inside hudson

2009-10-30 Thread Ravi Varanasi
Mauro - One of the team members found a workaround for this problem. The problem is commons-logging vs slf4j class loader issues. I think spring brings in the slf4j dependency in our project. Adding "-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog" to the maven command

[jbehave-dev] Re: Classloader issue when running scenarios inside hudson

2009-10-30 Thread Mauro Talevi
Ravi Varanasi wrote: Mauro - Below are the answers - Hi Ravi, let's take in steps: 1. Can you run scenarios successfully using Maven in CLI on your local machine - but not embedded in Hudson or any other CI? Running the scenarios from command line through Maven works, but running inside

[jbehave-dev] [jira] Commented: (JBEHAVE-162) Need to be able to set order of steps for matching

2009-10-30 Thread Douglas Padian (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196668#action_196668 ] Douglas Padian commented on JBEHAVE-162: I think that might work -- please run your proposed

[jbehave-dev] Re: Classloader issue when running scenarios inside hudson

2009-10-30 Thread Ravi Varanasi
Mauro - Below are the answers - > Hi Ravi, > > let's take in steps: > > 1. Can you run scenarios successfully using Maven in CLI on your local > machine - but not embedded in Hudson or any other CI? Running the scenarios from command line through Maven works, but running inside hudson causes

[jbehave-dev] [jira] Commented: (JBEHAVE-162) Need to be able to set order of steps for matching

2009-10-30 Thread Hitesh (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196660#action_196660 ] Hitesh commented on JBEHAVE-162: Would changing the match to use non-greedy match not help? Current

[jbehave-dev] Re: Classloader issue when running scenarios inside hudson

2009-10-30 Thread Mauro Talevi
Ravi Varanasi wrote: Mauro - Though the exception is thrown only when the run-scenarios is run (bound to integration-test phase). If the scenarios are not run the test works fine. Below is the output from dependency tree [INFO] +- org.springframework:spring-core:jar:2.5.6:compile [INFO] | \- co

[jbehave-dev] [jira] Resolved: (JBEHAVE-196) Candidate steps should be aware of the method annotation type when matching textual steps

2009-10-30 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-196. -- Resolution: Fixed > Candidate steps should be aware of the method annotation type when matching > t

[jbehave-scm] [1370] trunk/core/jbehave-core/src/java/org/jbehave/scenario/steps: Best attempt in ensure backward compatibility when using deprecated Steps(String[] startingWords).

2009-10-30 Thread mauro
Title: [1370] trunk/core/jbehave-core/src/java/org/jbehave/scenario/steps: Best attempt in ensure backward compatibility when using deprecated Steps(String[] startingWords). Revision 1370 Author mauro Date 2009-10-30 04:56:50 -0500 (Fri, 30 Oct 2009) Log Message Best attempt in ensure bac

[jbehave-scm] [1369] trunk/core/jbehave-core/src/java/org/jbehave/scenario/i18n/I18nKeyWords.java: Use static imports.

2009-10-30 Thread mauro
Title: [1369] trunk/core/jbehave-core/src/java/org/jbehave/scenario/i18n/I18nKeyWords.java: Use static imports. Revision 1369 Author mauro Date 2009-10-30 04:31:37 -0500 (Fri, 30 Oct 2009) Log Message Use static imports. Modified Paths trunk/core/jbehave-core/src/java/org/jbehave/scenar