I've made this change at r619373. The federation build.xml has also
been updated and the transition here is smooth. (Although you get
branches, tags, and trunk in common_resources when you update, the
svn_switch fixes this when you run ant.)
If you have other copies of common_resources checked out you should run
update and run svn switch to fix them. For example:
bash$ svn info |awk '/URL/ { print $2 }'
https://svn.apache.org/repos/asf/harmony/enhanced/common_resources
bash$ svn up
...
bash$ svn switch \
https://svn.apache.org/repos/asf/harmony/enhanced/common_resources/trunk
Alexey, I agree with Tim. The semantics of svn:externals aren't really
suitable for branching and tagging.
Regards,
Mark.
On 6 February 2008 at 10:02, Mark Hindess <[EMAIL PROTECTED]> wrote:
>
> I was hoping Alexey might comment on this given his involvement in the
> changes but I think it is a good idea to "fix" this now. Unless anyone
> complains I will take a look at doing it tomorrow.
>
> This will break builds and people will need to "svn switch" their
> commond_resources tree (or remove it and re-populate it if you have
> infinite bandwidth).
>
> Regards,
> Mark.
>
> ------- Forwarded Message
>
> From: Mark Hindess <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: Re: [announce] new DRLVM build system came into force
> Date: Tue, 05 Feb 2008 09:20:50 +0000
>
> Excellent!
>
> Before we get too comfortable with the changes we might want to think
> about whether:
>
> https://svn.apache.org/repos/asf/harmony/enhanced/common_resources
>
> should really be moved to:
>
> https://svn.apache.org/repos/asf/harmony/enhanced/common_resources/trunk
>
> We are going to want to be able to reproduce build so having the
> capability to use branches and tags might be useful. And it would
> be more consistent with the layout of the other svn-switched
> sub-directories of the federated build.
>
> I'll take a look at moving the dependencies in classlib to common_resources
> but before I force everyone working on classlib to checkout common_resources
> I'd like to get this resolved so we don't end up breaking it later.
>
> - -Mark.
>
> On 4 February 2008 at 16:51, "Alexey Varlamov" <[EMAIL PROTECTED]>
> wrote:
> > Folks,
> >
> > The new build system for DRLVM is now the offical one, our integrity
> > and snapshot CC systems were switched to it before this weekend.
> > Currently there is certain duplication of resources between the new
> > and old systems (property files, etc); I suggest we drop the old
> > system in a week or two.
> > Also, the old build directory encloses x-lists and MSVC solutions.
> > X-lists apparently should be moved closer to test sources, but what
> > about the solutions - just move them to working_vm/make? AFAIU they
> > need update to changed deploy dir names, any volunteers?
> > Meanwhile please be careful to update the right files, those in
> > <working_vm>/make tree.
> > I've updated GettingStarted page to reflect build changes, and will
> > update README.txt soon. Hopefully the transition to unified build
> > interface will be smooth for DRLVM developers.
> >
> > --
> > Alexey
> >
>
>
> ------- End of Forwarded Message
>
>
>
>
