I get the wrong class version error. My IDEA is 6.0.4 build 6148, Java 1.5.0_10
--
Shane
http://www.shaneduan.com
-
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
CustomWorld for those people who want to define their own World accessors
-
Key: JBEHAVE-85
URL: http://jira.codehaus.org/browse/JBEHAVE-85
Project: JBehave
Issue Type:
[
http://jira.codehaus.org/browse/JBEHAVE-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh closed JBEHAVE-85.
--
Resolution: Fixed
Fix Version/s: (was: 1.2)
1.1
> CustomWorld for those
[
http://jira.codehaus.org/browse/JBEHAVE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh updated JBEHAVE-82:
---
Fix Version/s: (was: 1.1)
1.2
> Behaviour plugin produces multiple launches
[
http://jira.codehaus.org/browse/JBEHAVE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh updated JBEHAVE-57:
---
Affects Version/s: (was: 1.0)
1.1
Fix Version/s: (was: 1.1)
Title: [714] releases/1.1.0/: [dn] tagging 1.1.0 release
Revision 714
Author tastapod
Date 2007-03-28 12:01:35 -0500 (Wed, 28 Mar 2007)
Log Message
[dn] tagging 1.1.0 release
Added Paths
releases/1.1.0/
Diff
Copied: releases/1.1.0 (from rev 713, trunk) ( => )
To unsubsc
Hi team.
Can everyone kick the tyres on 1.1.0 please? That's the download links
on the website (I've already checked but I'm paranoid), the javadocs
(ditto), the eclipse and idea plugins, and any implied or otherwise
promises to address world hunger. If all is well I'll announce the
release t
Title: [713] trunk: [dn] updating for 1.1.0 release
Revision 713
Author tastapod
Date 2007-03-28 11:49:35 -0500 (Wed, 28 Mar 2007)
Log Message
[dn] updating for 1.1.0 release
Modified Paths
trunk/core/src/java/org/jbehave/core/story/domain/World.java
trunk/jbehave.ipr
trunk/plugins/ecli
Oops, sorry Mauro. Of course I can.
Mauro Talevi wrote:
Dan North wrote:
Hi folks.
I'm planning to roll a 1.1.0 release tomorrow. (I'm not going to
worry about release candidates - it only confuses the numbering. If
it's broke I'll push out a 1.1.1.)
Does anyone have anything in flight tha
Dan North wrote:
Hi folks.
I'm planning to roll a 1.1.0 release tomorrow. (I'm not going to worry
about release candidates - it only confuses the numbering. If it's broke
I'll push out a 1.1.1.)
Does anyone have anything in flight that they want to get into the release?
At the moment it's:
Yep, I agree.
The one word counterexample that made it for me was GivenScenario. How
do you do that with abstract superclasses? :)
Just thought I'd float the idea.
I think it's different in Joe's world because the point of Hamcrest is
for you to derive your own matchers, so you would expect
[
http://jira.codehaus.org/browse/JBEHAVE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh closed JBEHAVE-84.
--
Assignee: Elizabeth Keogh
Resolution: Fixed
Fix Version/s: 1.1
Done.
> UsingMatchers
UsingMatchers.nothing()
---
Key: JBEHAVE-84
URL: http://jira.codehaus.org/browse/JBEHAVE-84
Project: JBehave
Issue Type: New Feature
Reporter: Elizabeth Keogh
This should ensure that you can explicitly stub
[
http://jira.codehaus.org/browse/JBEHAVE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh closed JBEHAVE-83.
--
Assignee: Elizabeth Keogh
Resolution: Fixed
Fixed.
> Stack trace overflow when UsingMatchers.e
Stack trace overflow when UsingMatchers.either(...)
---
Key: JBEHAVE-83
URL: http://jira.codehaus.org/browse/JBEHAVE-83
Project: JBehave
Issue Type: Bug
Affects Versions: 1.0
Re
Hi Dan,
Dan North wrote:
Hi folks.
I've been following an interesting discussion about evolving APIs, and
there's something I'd like to do for jbehave 1.1.0. Technically it
should be jbehave 2.0.0 by my own definitions, in that it will break
existing client code, so I want to get it out ther
16 matches
Mail list logo
