On Tue, 2003-04-01 at 15:22, Jason van Zyl wrote:
>
> So if we use, say, the Antlr plugin that generates sources you're
> talking about some non-maven compilation process knowing about the
> generated sources?
Yeah, that's basically it.
> The addPath tag allows any addition path of sources
> to be added to the maven.compile.src.set which is what is currently used
> to compile the project sources. Take a look at the Antlr plugin for how
> this works. If we need a way of external tasks to know where sources are
> we could probably add something to the POM that makes this information
> available when the addPath tag is executed.
I think that might be useful. Would the information from the addPath tag
be available even if the plugin hadn't actually generated it's source
code during that instance of maven? For example, if someone did
maven eclipse:generate-project
the antlr (or whatever) plugin wouldn't (probably) be executed, hence
the addPath data wouldn't be available.
That said, this isn't actually the problem I was trying to fix when I
started this thread :-) _That_ problem is that if you break a system
into a number of maven projects, one source tree in each, it's useful to
be able to say that a dependency actually relates to the current version
of another maven project rather than a jar file in some repository. Any
thoughts on that problem?
-Mark.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
