On Tue, Mar 22, 2011 at 7:12 AM, Benson Margulies <[email protected]> wrote: > I'm pushing Apache Batik jars to maven. > > Batik uses an ant build. By using various ant patterns, it subdivides > the source directory into 6 compiles and make 6 (different) jars. > > The ant build already sets up poms with dependencies, but whoever did > all this did not make provisions for source and javadoc jars. > > In pushing their existing 1.7 release, I don't feel comfortable trying > to do the level of surgery required to try to create accurate javadoc > and source jars that correspond to the various jars. > > So, I can just punt on javadoc and sources if I have to. I had hoped > that there was some trick whereby I could make them all point to a > single javadoc and a single source artifact, but I read this thread as > offering no joy of that sort.
Not in Maven directly. The best way would be to convince them to move to Maven and have it fixed for free :) In the meantime, you can hack your ant scripts to generate the source and javadoc. It sounds like you already have the 6 patterns since the jars are generated from these. The poms you use for these project's aren't real poms (since you aren't building your project's with them). The poms are like "stubs" so that maven projects can pull down Batik jars. So they don't need <build><plugin> sections to drive generating source/javadoc jars. They just need to make sure their dependency sections are correct. Then you need to get your pom, artifact.jar, source.jar, javadoc.jar uploaded into central and everything is done. Does this make sense? Barrie --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
