On Wed, Aug 18, 2010 at 12:09:58PM -0400, Benson Margulies wrote: > On the one hand, a completely ant (or otherwise) project can choose to > publish its results to the maven infrastructure for the convenience of > those users who use Maven, with no change to producing plain old > releases for people who are happy with them. > > I'm only writing this, by the way, because I think it benefits people > to understand the issues here. I'm not trying to sell anyone anything. > If there is a bugzilla out there, however, begging for maven > publication of fop, I would be happy to submit a patch that added the > necessary bits to the existing ant build.xml to publish releases to > the ASF maven repo -- without changing anything else about how fop is > built and released.
Our ant build produces maven bundles, thanks to one of our earlier committers. Actual deployment however requires a maven installation on my computer. On my Debian GNU/Linux machine installation of the maven2 package is simple in principle, but it brings 29 packages as dependencies with it. That is so much new software for functionality that I do not use myself, I just do not want to have it. Maven is just not (yet) for me. I wait for a friendly ASF committer who is willing to do the deployment for us. That is simply the best solution for the FOP team and FOP's maven users. Simon -- Simon Pepping home page: http://www.leverkruid.eu
