[SAFMT]

This is probably not a MyEclipse issue, but I’m hoping you folks might have an idea.

First of all, our development model is setup to allow our display developers to have commit access to WebRoot. and the Java developers to have access to the entire project. We use CVS to enforce permissions, and it works well.

The issue is that our developers create a bunch of content that has ‘source’ files similar to Java files, and these are currently stored in WebRoot (alongside the created files). Unfortunately, this means that our package warfiles include these source files in them. Normally, this isn’t a problem, except that it makes the deployed WAR files much larger than they need to be, which in and of itself isn’t a bad thing, except that it takes longer to build the deployment, as well as it takes significant period of time to re-deploy the site.

Is it possible to have the packager ‘ignore’ certain directories under WebRoot, which would allow us to leave the source files under source-code control (important), but not have these files deployed in the final WAR files since they are not used during deployment?

Thanks in advance!

[Scott Anderson]

Is it possible to have the packager ‘ignore’ certain directories under WebRoot, which would allow us to leave the source files under source-code control (important), but not have these files deployed in the final WAR files since they are not used during deployment?

Well, no. The webroot directory exists in our model because it signifies that everything under it is web content and therefore must be packaged in the WAR. At the present time, to do what you want you’d need to have the developers create these undeployable additional files in a directory outside the webroot since there isn’t a filtering mechanism available under the webroot.

Since the time and size seem to be the main issues, another alternative might be to use exploded deployment rather than packaged (for development only) if the server you’re targeting recognizes it. This will allow you to do a full deployment once and then each change you make will be automatically sync’d to the deployment on a file-by-file basis, thus eliminating the “big redeployment” most of the time.

[SAFMT]

Thanks Scott.

I figured as much. Unfortunately, exploded deployment would be a nightmare, since there are multiple developers, and while our application server supports it, it’s not 100% reliable.

Plus, packaged WAR files make it easier to guarantee that everything necessary is bundled up every time, since there are multiple people deploying to the site throughout the lifetime of the project.

I’ll talk with the developers and see if they would have a problem with us moving the development files outside of WebRoot.

Thanks!

[Author]

Posts