[ http://jira.codehaus.org/browse/MNG-697?page=comments#action_43891 ]
Kenney Westerhof commented on MNG-697: -------------------------------------- I'm not sure wheter this is a good idea - you can't directly call those classes anyway, because then the plugin would need a dependency on that code compile-time. You also cannot be sure if the plugin is never re-used (depending on the instantiation-strategy in plugin.xml). Wouldn't it be better to just ask for a ClassLoader/ClassRealm all setup with the correct classpath? > allow plugins to declare dependence on the project-classpath(s) > --------------------------------------------------------------- > > Key: MNG-697 > URL: http://jira.codehaus.org/browse/MNG-697 > Project: Maven 2 > Type: New Feature > Components: maven-plugin-descriptor, maven-core > Versions: 2.0-alpha-3 > Reporter: John Casey > Assignee: John Casey > Priority: Critical > Fix For: 2.0-beta-1 > > > Currently the only way to provide access to the classpath which consists of > the project artifacts within some scope from a plugin is to manually create > your own classloader inside the plugin using project.getCompileClasspath() or > somesuch. In many plugins (thinking of integration-tests where the project is > NOT an appserver module), it would be most useful to have the plugin > container started with the appropriate project-classpath already added to the > container. This might even be nice for testing plexus projects, and would > allow the plugin to simply instantiate (somehow) and use compiled classes in > order to run tests. > Jesse even tells me this would be useful from a process-classes phase, in > order to gather info about the classes that were compiled. > I propose the following modifications: > 1. Add addProjectClasspath="scope" (where scope = {compile,test...}) > configuration for the maven-plugin-plugin, alongside prefix or whatever else > we use to define the plugin-level metadata. > 2. For plugins declaring addProjectClasspath, add the appropriate project > classpath to the plugin container before calling the mojo. -- 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, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
