Martin, Isn't it possible to use the same Wicket's SVN for that? That is create a repo under SVN and do store the pre-releases there? Or maybe use an external google code project only for that?
IMHO having this could help a bit people trying to test new releases. Regards, Ernesto On Wed, Dec 22, 2010 at 2:34 PM, Martin Grigorov <[email protected]> wrote: > Hi, > > Symlinks will not work. I just tried: > > [mgrigo...@minotaur:~/public_html/repo]$ ls -la > total 7 > drwxrwxr-x 2 mgrigorov wicket 3 Dec 22 13:21 . > drwxr-xr-x 3 mgrigorov mgrigorov 3 Dec 22 13:18 .. > lrwxr-xr-x 1 mgrigorov wicket 43 Dec 22 13:21 latest -> > /home/jrthomerson/public_html/wicket-1.4.15 > [mgrigo...@minotaur:~/public_html/repo]$ cd latest > [mgrigo...@minotaur:~/public_html/repo/latest]$ ls -la > total 12 > drwxr-xr-x 4 jrthomerson jrthomerson 4 Dec 20 08:00 . > drwxrwxr-x 9 jrthomerson jrthomerson 10 Dec 20 07:55 .. > drwxr-xr-x 2 jrthomerson jrthomerson 11 Dec 20 07:58 dist > drwxr-xr-x 3 jrthomerson jrthomerson 3 Dec 20 08:00 m2-repo > > http://people.apache.org/~mgrigorov/repo<http://people.apache.org/~mgrigorov/repo/latest> > << this doesn't list 'latest' > http://people.apache.org/~mgrigorov/repo/latest << this returns 403 > (Forbidden) > > > So we can just *copy* everything from > "/home/XXX/public_html/wicket-1.4.YY/*" in > "/home/mgrigorov/public_html/repo/latest_vote_14" and use that link. > Similar for 1.5. > > > On Wed, Dec 22, 2010 at 1:58 PM, Ernesto Reinaldo Barreiro < > [email protected]> wrote: > >> Dear all, >> >> Do you think it would be a good idea to have a fixed place where maven >> artifacts are deployed when a release vote is called. E.g. current >> 1.4.15 voting is pointing to: >> >> Maven repo: http://people.apache.org/~jrthomerson/wicket-1.4.15/m2-repo >> >> and probably next will be >> >> Maven repo: http://people.apache.org/~jrthomerson/wicket-1.4.16/m2-repo >> >> or maybe >> >> Maven repo: http://people.apache.org/~xxx/wicket-1.4.16/m2-repo >> >> If developer xxx is creating the release. >> >> Would it make sense to have to have a unique repo hosted somewhere so >> that in order to test a new version we only need to bump the version >> number in order to test a new pre-release? E.g. at work we are using >> artifactory and it would be nice to have a unique URL for every new >> pre-release. >> >> Regards, >> >> Ernesto >> >
