On Tue, 2003-04-01 at 04:29, Jason van Zyl wrote:
> On Mon, 2003-03-31 at 19:29, [EMAIL PROTECTED] wrote:
> > "Mark H. Wilkinson" <[EMAIL PROTECTED]> wrote on 01/04/2003 
> > 01:44:01 AM:
> 
> > >         At the moment the paths to the source trees are
> > >         encoded in the jelly script, so aren't easily available to any
> > >         plugin. A simple solution that you could start with would be to
> > >         put them in <properties> elements in the POM, but there probably
> > >         ought to be support for this in the POM itself (IMHO).
> 
> Sorry, I don't understand.

Mark McBride was saying that he has a jelly script to copy his multiple
source directories into one source tree for building (I think). I was
saying that it would be difficult for a plugin to use this information
because it's part of his jelly script, not part of the POM.

> There will never, ever, ever be support for more than one source tree
> per project.

Hmm; by that do you mean one source tree compiled by the java plugin?
The unit test source tree is effectively a second source tree, it's just
processed in a different way. As is the source tree that's generated by
the antlr plugin, from what you say.

I think there's a bit of a problem with the model here, because plugins
that would like to know about the various trees that contain Java source
need to have explicit code in them to handle each source tree. The
Eclipse plugin currently knows about the sourceDirectory and the
unitTestSourceDirectory. If another kind of plugin was introduced and it
had its own Java source tree, the Eclipse plugin (for example) would
need to be modified to extract the information from the POM and put it
in the .classpath file; as would any other plugin which needed to know
about source code locations...

I'm happy with one main source tree per project, but it might be useful
to have some way to extract all the source-tree-kind-of-things-that-are-
manipulated-by-plugins from the POM.

-Mark.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to