If we move this to the parent pom, we must take of mult modules build (scm, release). I'm not sure we need this sources tarball for each modules of those projects.
-- Olivier 2009/7/27 Arnaud HERITIER <aherit...@gmail.com>: > On Mon, Jul 27, 2009 at 7:28 PM, Jason van Zyl <jvan...@sonatype.com> wrote: > >> >> On 27-Jul-09, at 1:30 AM, Benjamin Bentmann wrote: >> >> Jason van Zyl wrote: >>> >>> Not sure if it's in flux but the format of what came out in the Jar >>>> Signer Plugin and what Vincent just released for the Javadoc Plugin seems >>>> to >>>> be different though the same version of the parent appears to have been >>>> used. >>>> >>> >>> The parent is not responsible for the ASF-compliant source distro, it's >>> produced by a per-project assembly descriptor. >>> >>> >> That's horrible. It's not in the parent plugin POM? We need to figure out a >> way to share that. This is why the naming of the source distribution is >> different between the recently release plugins. > > > +10 I thought we waited several weeks to have this new apache parent ?? > Is it a technical limitation ? > > Arnaud > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
