This project is read-only.

Deploying Web App & Web Site Project Types

Dec 5, 2008 at 6:20 PM
When deploying a Web App project to a artifact repository initially you need to deploy the entire thing, images, pages and all.  But after that with each release you don't necessarily want to do that. You would in most cases only want to deploy those items that have changed.

For example if you changed 2 pages and add 3 images, you would only want to deploy to the repository those 2 pages, the new dll and those 3 images all in the correct folders of course. 

What does everybody think of this approach?
Dec 6, 2008 at 1:17 AM
As a deployment approach, it sounds fine... are you suggesting a change in NPanday?

I think the default artifact NPanday produces from a web app project needs to be the the zip file containing "everything".

If you want to post-process the main artifact and remove items that match the ones in a prior release, that doesn't sound too hard...  then depending on what you want you could either replace the main artifact or attach the stripped-down one with a classifier.

Another way would be to use the assembly plugin and define the items you want to include.

Dec 8, 2008 at 5:55 AM
Well, I was thinking that it doesn't always make sense to deploy the entire website to the repository.  This could get pretty big pretty quick.  Was just thinking that it would be more efficient to only release what has changed to the repository.