OK - the new svn repo is in place:
https://svn.jboss.org/repos/mod_cluster
Please commit all future work against this new repo.
I've also created a branch for 1.0.x, called branches/1.0.x
Work on 1.1 will continue in trunk.
Jean-Frederic, can you update the hudson jobs to use the new svn
location?
Paul
On Thu, 2009-07-30 at 08:58 +0200, jean-frederic clere wrote:
On 07/29/2009 09:52 PM, Paul Ferraro wrote:
> Today, Jean-Frederic and I discussed creating c an svn branch for 1.0.x
> work so that work on 1.1 can proceed in trunk. However, this brings up
> another issue...
> Currently, we share our subversion repository with the jboss native
> project. Our source code resides in an awkward subdirectory of trunk,
> making branching (not to mention the maven release process) equally
> awkward. Now would seem to be as good a time as any to move to our own
> repository. How would this impact the build of the native side?
There should be no problem with the build logic it is used to build
other stuff so it will work even if we move mod_cluster to another repo.
I would prefer to move the whole mod_cluster repo and then branch 1.1.x
to be able to port back stuff easily. (Note that commits in mod_cluster
causes hudson to build jbossnative actually which is not that good).
Cheers
Jean-Frederic
> If we
> keep its current location, should this branch only copy from
> trunk/mod_cluster? Thoughts?
>
> Paul
>
>
> _______________________________________________
> mod_cluster-dev mailing list
> mod_cluster-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/mod_cluster-dev
>