On 1/27/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
At the risk of complicating things, isn't bad form, if nothing else, to cut a release based on a transient repository location? One of the reasons to use Maven is to have a reproducible build, and a release is the kind of build which is more likely to need to be reproducible for some reason, and it seems fairly likely that the "struts-annotations-101-staging" repository will not be around for ever.
It's true that the staging repo will go away, but prior to that, the struts-annotations jar will be put into the central Maven repo. This does not affect the long term reproducibility of the struts 2.0.4 build. Nothing in the tagged/released struts poms will refer to the staging repo, it only goes in the release manager's settings.xml file temporarily. (Alternately, the RM could download and 'mvn install:install-file ...' the struts-annotations jar locally.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
