The new assembly plugin makes it trivially easy to have the release
profile build the source distro, which is really amazingly nice.
However you can easily have a separate profile to run an earlier
assembly plugin to construct just the required source distro and run
it with -N so it only runs once.
Now that the policy has been clarified there are no more excuses to
not following it.
thanks
david jencks
On Jun 3, 2009, at 3:10 PM, Arnaud HERITIER wrote:
I think there's no value to block all releases, waiting for this fix.I
agree, support this change, but it won't help our users to have them
waiting
all our releases for several weeks.
We are doing it like that (yes badly) for a long time now. Thus I
don't
think that one or two releases will change something.
Arnaud
On Wed, Jun 3, 2009 at 11:48 PM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
Barrie Treloar wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-
staging-005/
-1
As far as I understand the recent discussions about proper releases
[0] and
the current docs [1], we are required to provide "a source package,
which
must be sufficient for a user to build and test the release". This
requirement is not met by the "*-sources.jar" (no POM, no tests).
One needs to grap an assembly descriptor to create a proper source
bundle
(John and Brian are working on improvements to our tooling to make
this
easy).
Others may please correct me if I misunderstood the Apache release
policy.
Benjamin
[0]
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200904.mbox/browser
[1] http://www.apache.org/dev/release.html#what-must-every-release-contain
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
