As Stephen has said, if you can find a creative work around to drive Maven from Ant, I think that's the best way to go.
But since we've been moving more and more build process logic into Javac annotation processor from Maven, I think you can actually make it work.
The *.jpi files (which is the new name of *.hpi) are packaged in the same way as *.war files. They got some class files in WEB-INF/classes, static resources, and dependency jars in WEB-INF/lib. I think you can easily cook your Ant script to package this.
To compile your plugin source files, your classpath needs to include everything in /WEB-INF/lib of jenkins.war. Again, I don't think this is too hard.
The only part that you suffer is how you build META-INF/MANIFEST.MF of your .jpi file. The code to generate this is in Maven plugin, and so you'll have to manually write it and maintain it.
Look at some existing plugin files and hopefully you'll can tweak it to the format you need.
Good luck! On 03/20/2012 05:13 AM, Antares wrote:
My company we have a corporative dev tool based on ANT so every project has to be build with it. I would like to know if somebody have found an Ant task to packaging as 'hpi'.
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
