You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ca...@gru.com on 2004/02/13 18:49:27 UTC
RE: Can I set the classpath for a plugin?
What about using the project.xml from the plugin? You can add dependencies
via the <dependencies> subnode...
Is this not adequate?
-john
-----Original Message-----
From: David Jencks [mailto:david@coredevelopers.net]
Sent: Friday, February 13, 2004 12:52 PM
To: users@maven.apache.org
Subject: Can I set the classpath for a plugin?
I'm working on a maven plugin for xmlbeans. I need to be able to
specify for each use of the plugin which dependencies are in the
classloader that loads the java class used by the plugin (which is
included in the plugin) or what is in the thread context classloader (I
think).
Before I go off and spend hours investigating this I thought I'd ask if
this is possible and how to do it.
Many thanks,
david jencks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Can I set the classpath for a plugin?
Posted by David Jencks <da...@coredevelopers.net>.
AFAIK this is not adequate.
Each time I use the plugin I need different stuff on the classpath.
Some background is that the xmlbeans schema compiler, each time it is
called, makes sure everything referenced (recursively) from the schemas
you tell it about can be processed by code. Anything you have already
processed needs to be available in the schema compiler classloader or
it will generate another copy.
an example:
module A has schema A, with no references. schema compiler compiles it
fine.
module B has schema B which references A. Unless the results from
module A are available in the classloader for the schema compiler when
compiling B, the schema compiler will generate duplicates for what id
did for module A.
thanks
david jencks
On Friday, February 13, 2004, at 09:49 AM, CaseyJD@gru.com wrote:
> What about using the project.xml from the plugin? You can add
> dependencies
> via the <dependencies> subnode...
>
> Is this not adequate?
>
> -john
>
> -----Original Message-----
> From: David Jencks [mailto:david@coredevelopers.net]
> Sent: Friday, February 13, 2004 12:52 PM
> To: users@maven.apache.org
> Subject: Can I set the classpath for a plugin?
>
> I'm working on a maven plugin for xmlbeans. I need to be able to
> specify for each use of the plugin which dependencies are in the
> classloader that loads the java class used by the plugin (which is
> included in the plugin) or what is in the thread context classloader (I
> think).
>
> Before I go off and spend hours investigating this I thought I'd ask if
> this is possible and how to do it.
>
> Many thanks,
> david jencks
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org