[
http://jira.codehaus.org/browse/JBEHAVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98251
]
Mauro Talevi commented on JBEHAVE-49:
-------------------------------------
Stefan, a few comments from a cursory look.
I have purposefully avoided linking the behaviour scope to 'test'.
Also, I'm not sure I understand how this proposed patch differs from current
implementation. It too uses a separate classloader to instantiate the
behaviours.
I'll have a look into more detail during the week. Thanks.
> Maven 2 support
> ---------------
>
> Key: JBEHAVE-49
> URL: http://jira.codehaus.org/browse/JBEHAVE-49
> Project: JBehave
> Issue Type: New Feature
> Components: Build system
> Reporter: Mauro Talevi
> Attachments: jbehave-49-classloader.patch, maven-patch.txt
>
>
> Regardless of feelings about maven vs ant, there is a case for supporting
> both.
> IMO maven 2 provides a declarative approach that simplifies readability of
> build system,
> especially for multicomponent systems.
> Discussions on merits should be on the list.
> Here I'm attaching an initial spike patch that mavenises build for people to
> have a look at and get a feel.
> Read README.txt to start off with - need to install cotta jar in the local
> repo (this is just a temporary step to get build
> working - it can also be configured to be installed automatically or deployed
> to ibiblio).
> The behaviours still fail to run because of the
> jbehave.core.util.BehavioursLoader does not provide injection of classloader.
>
--
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