PureMVC Architects Lounge

Announcements and General Discussion => General Discussion => Topic started by: cyianite on October 25, 2008, 10:55:49

Title: Multiple project deployment
Post by: cyianite on October 25, 2008, 10:55:49
Hi Cliff,
  I'm a big fan of your framework and I using it for our Big project . I have this question , cause we will have multiple deployment for our project, its like we'd like to put our source project control into two separate folder but this two will use one source code or one framework. Its like project-A has something different from Look-And-Feel to project-B but using same source code and will be deployed separately. (hope I explained this right :) )

  I like to know what is the best approach do you think to do this?, and using this pureMVC how will I handle two different project in one source code for maintainability?, please help me on this.

Thank and more power,
Cyianite  ;D

Title: Re: Multiple project deployment
Post by: puremvc on October 25, 2008, 04:50:06
One really cool way to handle this in Subversion, if that's your repo, is to use the svn:externals property to pull source code from external repos along with the project you are checking out.

This way, projA might be the code and projB and projC are custom apps that use the code and add skins and or more functionality.

The pulled in code gets compiled as if part of the project.


Title: Re: Multiple project deployment
Post by: Tekool on October 26, 2008, 06:31:31
You also can use a common project and two other projects that use it directly as a library in your development environment. I don't know the language you use, but it works for Flex and Java, I suppose it can work for almost anything that PureMVC supports. I use this configuration since a long time with Actionscript 2/3 and SVN, it's effective.

I've never use the "svn:externals" of Cliff's solution, I will give a try asap.

Title: Re: Multiple project deployment
Post by: puremvc on October 26, 2008, 04:15:55
Sure, jus as any of the PureMVC utilities, you can just take the compiled library be it a swc, dll, jar, etc. And put it in your build path.

But its kind of nice to have the source code in the project so that the debugger can step you through it on screen.

Once your library of shared code is solid enough (unit tested) and development on it has slowed, then projects that use it might switch from pulling in the code to using a compiled lib.