Maurice Marrink wrote:
Currently you would ask someone on this mailing list to give you
access to bamboo where you can setup a build for your project(s) after
that they are automatically available in the wicket stuff repo.
Johan and Martijn can give you access, probably Eelco too, don't know who else.
Maurice,
I already have access to bamboo. It's why I say deploying isn't easy.
because
* wicket stuff repo contains artifact build by bamboo only.
* how I work (and core wicket is similar)
* trunk host snapshot version
* when I release (using maven-release-plugin) I tag the code
* wicket stuff repo mixe snapshots and released version => impossible to
request rsync with central repository
bamboo is for continuous build, I understand to use it to deploy snapshots.
But my question was "how can we deploy *released* artifact today ?"
IMO, it's stupid to create a bamboo plan for release (one shot).
Using bamboo to release is overkill instead of :
mvn deploy
or
mvn release:prepare
mvn release:perform
similar question : where to deploy mvn generated site with bamboo ?
Thanks for your answer.
/davidB
PS: as you wrote using bamboo, require supplementary stuff for admin : provide
account and permission on bamboo (after providing access on sourceforge :
required for svn).
Maurice
On Jan 18, 2008 10:08 PM, David Bernard <[EMAIL PROTECTED]> wrote:
Eelco Hillenius wrote:
Another problem (I think) with sourceforge is that space is limited.
Wicket-stuff is registered as one project, but there are quite a few
projects under there.
but so few in the maven repository. :(
If someone whant to use one, he need use svn +
I host on the alchim.sf.net repository, more jar than the actual wicketstuff
repository (total (repositories + website) = 93M).
And the rsync with central will allow to use sourceforge to only store latest
version.
I'm not sur the actual solution is "simple" for contributor/developper (not
admin).
But, may be, I'm wrong (lake of info), how can we deploy released artifact
today ?
/davidB
Eelco
On Jan 18, 2008 11:47 AM, David Bernard <[EMAIL PROTECTED]> wrote:
The one on apache is not accessible/updatable by wicketstuff developpers, it
also mixe releases and snapshots.
the repo on sf.net could be slow
* if the releases are rsync on central repo.
* snapshots version are less used
* if it allows to release easier (and may be more often)
Currently deploy a release (or a snapshots) is very unclear.
As a wicketstuff developper, I vote for a simpler process to release on sf or
somewhere else.
/davidB
Igor Vaynberg wrote:
we did have a maven2 repo on sf.net for wicket before we moved to
apache but it was appallingly slow...
-igor
On Jan 18, 2008 4:38 AM, David Bernard <[EMAIL PROTECTED]> wrote:
Hi,
May be part of the space problem on bamboo server, could be solve by hosting
maven-repository on sourceforge.
There is some advantages :
* every committer on wicketstuff, already, have ssh access
* every committer could deploy manually snapshots and releases
* release version could be deploy with maven-release-plugin
* if there is 2 repositories repo-releases and repo-snapshots, then we could
request a rsync from repo-releases to maven central repository
I already setup this type of configuration of sf (cf:
http://alchim.sf.net/download) and similar for other server
http://maven-repo.gforge.inria.fr/releases ,
http://scala-tools.org/repo-releases .
WDYT ?
I could do a try with wicketstuff-parent, wicketstuff-misc
/davidB
