On Tue, 2003-04-01 at 04:33, Mark H. Wilkinson wrote: > > 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... >
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? 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. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
