[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272699#comment-272699
]
Adriano Bonat commented on JBEHAVE-543:
---------------------------------------
Hey Mauro, thanks for letting me know that I should also test with
"-Pexamples", it will be useful :)
About the issue, it is happening in your master too and it is a bug in Weld:
https://issues.jboss.org/browse/WELD-897
they're generating java class names with illegal characters for their proxies.
The Weld example never really worked and the build with profile 'examples' is
broken since Paul added it back to the examples' pom.xml:
https://github.com/jbehave/jbehave-core/commit/da2e5e0a56edf2f0b7cf3fe2fbf4889c9ba8047d
I got success after upgrading to Weld-se 1.1.1.Final and you can pull my
checkin:
https://github.com/tanob/jbehave-core/commit/30feb5b7815da73fcd78ef14c8f8fba40797f465
Would be better if you add the 'examples' build in the CI environment, so you
will be aware of any breakage on them.
Now talking about this ticket, I've made a great progress in the last couple of
days and hope to finish everything in the next days, so stay tuned! :)
> Before/After Story/Scenario methods could accept parameters that have meaning
> at that moment
> --------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-543
> URL: https://jira.codehaus.org/browse/JBEHAVE-543
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Paul Hammant
> Assignee: Mauro Talevi
> Fix For: 3.5
>
>
> For example -
> bq. public void myBeforeStory(@Named("someMetaTag") String someMetaTag) { .. }
> This would be a poor-mans version of JBEHAVE-541
--
This message is automatically generated by JIRA.
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
