Dean,
Can you provide some more details on how you're doing this? There's
some folks on this list that are new to SVN.
Thanks,
Matt
On Nov 30, 2007, at 1:16 AM, Dean Hallman wrote:
I'm just getting started with AppFuse, so this might be old news...
But I wanted to suggest a technique for structuring your AppFuse-
based projects (for those using subversion anyway).
IMO, ideally you may want to work in an appfuse:full-source (or
war:inplace) expanded view of your project, but that puts your code
and appfuse code together - which isn't ideal for version control
and upgrading. Furthermore, it is somewhat difficult to switch
between a collapsed appfuse project and an expanded one for serious
debugging. Svn:externals is a really good solution for a situation
like this. I'm using AppFuse with svn:externals to create a full
source project, with my code brought in via an svn:external
reference. This way, I can drop my code into multiple concurrent
versions of AppFuse without problem, since it is just a pointer out
to my code and subversion overlays the two for me automatically.
This clearly separates my code from appfuse code and when I check
in, the files know which subversion repository or path to commit to.
Anyway, I've found this a useful technique applied to AppFuse-based
projects, so I thought I'd pass it along...
Dean
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
