On 8/23/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
On 8/23/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
>
> On 8/20/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
<snip/>
> >
> > So my proposal is to involve everyone in the beta testing but do not
> > distribute the "final" version to vote on so we can prevent mass
> > confusion. If non committers want to participate they can build from
> > the *tagged* svn version (not the trunk) and they do so at their own
> > risk.
> >
> <snip/>
>
> Makes sense, going a step ahead, if a committer could generously post
> (rather than deploy) the bits in their personal webspace (rather than
> a maven snapshot repository, which presumably is where folks can
> unknowingly obtain the "premature" artifacts from) -- that would lower
> the barrier for participation, which is a good thing IMO.
Now that we're building with Maven2, there are two "kinds" of things being
deployed:
* Release artifacts (bundled-up versions of the sources and compiled
code, essentially like what the nightly builds produce)
* Maven artifacts (jars and poms that need to be published into a
Maven repository to be accessible).
For the former, I did indeed do what Rahul suggests (
http://people.apache.org/~craigmcc/shale-proposed-release-1.0.3 but this is
going away now that it's been completed), and that was part of the "please
test" message to the dev list.
<snap/>
Yup.
For the latter, it wouldn't really make sense to set up yet another Maven2
repository in the release manager's personal web space ... the
http://people.apache.org/repo/m2-snapshot-repository exists for this
purpose. Indeed, the nightly build process has been posting
1.0.3-SNAPSHOTbuilds of these poms and jars all along (and, this is
where the initial
1.0.3 test builds were posted). So, if you've been using 1.0.3-SNAPSHOT and
wanted to try out 1.0.3, you'd need only switch the version number in your
dependencies and you'd get the right stuff automatically ... no need to
configure yet another repository entry for the temporarily posted bits.
<snip/>
I tried to be careful in phrasing that, but didn't have much success
;-) Ofcourse, setting a m2 repository in personal webspace will be no
fun (and a waste of time), but just posting the artifacts there (not
in any particular repository layout) might be possible.
For simplicity, lets say we have a simple project which produces just
one artifact, foo.jar (yes, I oversimplified!). I can do a "mvn
compile" and scp foo.jar (with sums and sigs) to ~rahul. If folks
think its OK (they will have to deploy manually to local repo), we
deploy to the remote repo(s) of choice. I claim that the extra effort
required to manually deploy the artifacts in the local repo (by folks
who are testing it) actually works in our favor, since there is little
chance to accidently acquire the artifact (as against the apache
snapshot repos, which are fairly "well-known") and thereby, forget to
replace it with the "final" v1.0.3.
-Rahul
Craig
-Rahul
>
>
> > Sean
> >
