[ http://jira.codehaus.org/browse/MINVOKER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MINVOKER-6. ------------------------------------ Assignee: Benjamin Bentmann (was: John Casey) Resolution: Fixed Fix Version/s: 1.2 Added option {{addTestClassPath}} in [r651733|http://svn.apache.org/viewvc?view=rev&revision=651733] which allows to extend the BeanShell class path with the test class path of the project under test. > 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: Benjamin Bentmann > Fix For: 1.2 > > > 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