On Thu, Aug 23, 2007 at 02:33:08PM +0100, Paul Cager wrote:
And can we just build them using
a custom build.xml written for ant?
That's the approach I've taken for some of Maven's build-depends - a
custom debian/build.xml. You could have a look at doxia or wagon for
example.
But consider the maven-resources plugin. The source jar has the
following:
org/apache/maven/plugin/resources/util/
org/apache/maven/plugin/resources/PropertyUtils.java
org/apache/maven/plugin/resources/ReflectionProperties.java
org/apache/maven/plugin/resources/ResourcesMojo.java
org/apache/maven/plugin/resources/TestResourcesMojo.java
org/apache/maven/plugin/resources/util/InterpolationFilterReader.java
I created a build.xml, and can copy your idea to make a deb. But is it
worth creating a single deb just for these, or do you think a
maven-plugins package with all the plugins assorted and a single
build.xml would be better? I ask this, since we have to repackage the
things anyway, for the source is provided as jars. But this would mean
that if some one plugin's version is bumped up, it would require a
rebuild of the whole thing. So, what is the right way?