[
http://jira.codehaus.org/browse/MINVOKER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115440
]
Olivier Lamy commented on MINVOKER-6:
-------------------------------------
Just to be sure of your needed is it the mojo under testing classpath or the it
classpath ?
If you want to provide a patch, you have to :
- checkout the project : svn co
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-invoker-plugin
- made your changes on the sources (a unit test will be appreciate)
- svn diff > MINVOKER-6.patch
- attach the file MINVOKER-6.patch to this issue
Thanks
> Add current's project test classpath to the Bean Shell interpreter classpath
> ----------------------------------------------------------------------------
>
> Key: MINVOKER-6
> URL: http://jira.codehaus.org/browse/MINVOKER-6
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Samuel Le Berrigaud
> Assignee: John Casey
>
> It would be interesting to add the test classpath of the current maven
> project to the Bean Shell's interpreter classpath.
> This would allow developing some utilities classes (project specific
> assertions for example) and use them effectively in the post (or pre) Bean
> Shell scripts..
> I tried it and it is fairly easy to do using the
> bsh.BshClassManager#addClassPath(java.net.URL path) method. Just remember to
> add a trailing "/" at the end of folder URLs for the class loader to pick
> them.
> I could possibly look into providing a patch, so far I worked against the 1.0
> tag. Don't know how I would effectively test that though...
--
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
