It is simply Java code - so you would write a Java ant task to wrap the existing code.
Some things to note: - the best solution would be to read the plugin metadata and construct the ant task automatically (similarly to generating the documentation) - some plugins use private field injection, so will need setters added. - I'm not certain, but those with simple setters and no logging may even work as is. The eclipse plugin would not work as is due to requiring a project instance, and doesn't currently have setters - but it is definitely possible. Hope this helps. If you'd like to contribute to any of these tasks we'd be happy to help. If you'd like to file a JIRA issue for it to be addressed later, that can be worked on after the 2.0 release. Cheers, Brett On 9/29/05, Darren Hartford <[EMAIL PROTECTED]> wrote: > If I could reuse the Maven Eclipse plugin as an Ant task, I would > actually prefer that! Is there a reference somewhere on how to call > plugins through Ant? That would be awesome! > > -D > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, September 28, 2005 8:10 PM > > To: Maven Users List > > Subject: Re: [ot] m2 antlib and eclipse classpath task - > > someone else take a look pls? > > > > This would be a question for Ant. I'm not sure how you > > generally deal with iterating paths for generating content. > > > > Of course, another option is to use the Maven Eclipse plugin > > to generate the eclipse .classpath from the POM you have > > already created (which could be wrapped in an ant task if > > that was what you needed). > > > > - Brett > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
