AW: Seperate Classpath for test or Javadoc (or other plugins)

Hi Michal Thanks for the correct reply. Indeed we are talking about two or more graphs. From my point of view there should be a mechanism to manipulate the classpath of a specific plugin to solve such a problem. (or have somthing like projectbuilddependencies in the pom and to fork the VM for

Seperate Classpath for test or Javadoc (or other plugins)

Hi I use several jar's for launching my testcases (ex. Httpunit) and the javadoc plugin (i use another doclet). Is there a way to seperate those dependencies from the real application dependencies? (Sample: use some properties for the dependency?) Currently i put all jar's needed for javadoc

RE: Seperate Classpath for test or Javadoc (or other plugins)

Hi Rolf, I think this will be improved when transitive dependencies functionality is implemented. Currently the only solution is using xml entities, check List all dependencies or only main ones? thread. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net

Re: Seperate Classpath for test or Javadoc (or other plugins)

Carlos Sanchez wrote: Hi Rolf, I think this will be improved when transitive dependencies functionality is implemented. Currently the only solution is using xml entities, check List all dependencies or only main ones? thread. Carols: this has nothing to do with transitive dependencies.