[
http://jira.codehaus.org/browse/JBEHAVE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222425#action_222425
]
Mauro Talevi commented on JBEHAVE-292:
--------------------------------------
Your updated project works fine for me (Mac JDK 1.6). Yes, I would strongly
advice to always to a clean when building, as you want to ensure that the build
is consistently compiled from source and not picking up artifacts from other
sources. Please try 'ant clean build'.
> Failed To Instantiate Scenario - ClassNotFoundException
> -------------------------------------------------------
>
> Key: JBEHAVE-292
> URL: http://jira.codehaus.org/browse/JBEHAVE-292
> Project: JBehave
> Issue Type: Task
> Components: Ant extension
> Affects Versions: 2.5.4
> Environment: Windows 7, JDK 1.6.18, JBehave 2.5.4, Selenium Server
> and Selenium-Java client.
> Reporter: Tom Little
> Attachments: LoginProject.zip, LoginProject.zip
>
>
> Hi,
> I'm having an issue with a very basic project using Jbehave and Selenium and
> hopefully someone can help me out.
> I have managed to create a .scenario, LoginScenario.java and LoginSteps.java
> basic test with Selenium built in to test a login of a website. This is all
> setup in Eclipse with the correct .jars on the classpath and buildpath, it
> runs and works correctly. There is also a base.properties file that the test
> uses to determine the URL to test.
> I've been trying to migrate the project into a command line build using an
> Ant script. I have almost carbon copied the build.xml from the Trader example
> from the Jbehave website except rather than reading in the dependencies from
> the pom.xml it copies local JARs into the classpath. Hopefully I have all the
> Jars I need. I've also left out the reporting stuff as I just want the tests
> to run firstly.
> It fails to instantiate the LoginScenario.java file and further down in the
> error list is a ClassNotFoundError which makes me think the classpath isn't
> including the compiled classes even though the output says the compilation
> has been sucessful and prints out a very long classpath with the Jars in and
> the path C:\LoginProject\target\classes which is the destdir of the compile
> target.
> I'm sure its just me missing something in the build.xml, I'm sure its not an
> issue with the Java classes themselves as they work fine in Eclipse when you
> run LoginScenario.java
> Ive attached the project and under /lib there is a list of the JARS I would
> have in List of JARS.txt, sorry I know this is a bit of a rubbish way of
> doing things I'm just not particularly familiar with Maven and how to use its
> functionality.
> Many Thanks,
> Tom.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email