Hi! My use-easy is simple: to pass build information collected/generated by a buildinfo (our own - not the public one) to a second plugin (FreeMarker plugin, also our own) that generates Java Source code using templates.
The build information is Java System Properties, Maven Effective POM, Perforce properties (e.g. buildno) etc. Right now the first plugin outputs to the files which are set as inputs to the second plugin. However, it would be easier and more efficient/faster if we could pass object directly to the second plugin. I still consider the plugins to be atomic - passing on a file or a context object really doesn't matter. It's just a matter of how I configure my plugin where does it read input from and where does it place output, e.g. Plugin A: <output> <type>file</type> <value>myfile.txt</value> <output> Plugin B: <input> <type>file</type> <value>myfile.txt</value> <input> or Plugin A: <output> <type>context</type> <value>outputFromA</value> <output> Plugin B: <input> <type>context</type> <value>outputFromA</value> <input> Regards, Jimisola A Plugin, IMHO, is atomic. I don't think you can actually have 2 plugins inter-communicate (the way you need it), except for reading the configuration from pom.xml, which was on one of the threads on the user@ or dev@ list just a couple of days ago. What is your use-case - there might be another way of doing what you want to? Cheers, Rahul -- View this message in context: http://www.nabble.com/Inter-Plugin-communication-tf1937787.html#a5313806 Sent from the Apache Maven Developers List forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
