I know - my bad. And I fucked up twice.
The re-releases were due to the current poor module version
support... when upgrading 3.0.1 with the 3.0.2 jars, the samples
would be re-bootstrapped, thus overriding your changes. Of course it
should have been no big deal to just warn users not to update the
samples jar, in the upgrade notes. My bad again.
Actually, I wish there was an extra step in the release plugin, so
that you could test the final built artifacts before the get uploaded
to the repo...
g
On Mar 5, 2007, at 15:34 , Fabrizio Giustina wrote:
Hi Grégory,
We should really avoid deploying the same release more than once: I
was wondering to setup a repository sync in order to have magnolia
builds automatically deployed to the main maven repository, but we
can't do that until these rules are broken.
It's ok to retry and retag a release when only a release:prepare has
been done, but once a release hits the repository it should never be
replaced. It's better to just release it as 3.0.3, I guess nobody will
complain about the "version name"...
We did a lot of mess in the past about releases but I would like to
start handling them more carefully. Do anybody cares about a maven
repo sync? I think many users would be glad for that. If so we should
also cleanup the existing repo and be sure that in future only *clean
releases* will be deployed to the non-snapshot repo...
fabrizio
On 3/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Revision 8609 Author gjoseph Date 2007-03-05 13:21:20 +0100 (Mon,
05 Mar
2007)
Log Message will redo 3.0.2
Removed Paths
magnolia/tags/magnolia-3.0.2/
Diff
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
